-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
writing /etc/resolv.conf caused: open /etc/resolv.conf: permission denied: unknown without "userns-remap":"sysbox"; kernel version is fine #799
Comments
Hi @dimikot, Thanks for giving Sysbox a shot! Can you share your docker-compose YAML so I can recreate locally please? With Kernel 5.15 you shouldn't need to run Docker in userns-remap mode, as Sysbox will leverage the kernel's ID-mapped-mounts feature to ensure files show up with proper ownership inside the rootless Sysbox container. However we still recommend shiftfs until kernel 5.19 which adds overlayfs on ID-mapped-mounts support. Thanks! |
@ctalledo Thanks! Try using the following compose.yml, I think it's self-sufficient: services:
ci-storage:
image: ghcr.io/dimikot/ci-storage:main
ports:
- 26022:22
environment:
- TZ
volumes:
- ci-storage-mnt:/mnt
volumes:
ci-storage-mnt:
external: false See my linux kernel version in the above I actually don't want shiftfs in sake of just performance, since its installation is not so trivial (compiling from source code etc.); I want the setup to be as vanilla as possible. |
Hi @dimikot, Apologies for the late reply. I am not able to repro on an AWS Ubuntu Focal host with kernel 5.15:
Not quite sure why if fails in your case ... |
I also used Sysbox v0.6.4:
|
Despite it's said in https://github.com/nestybox/sysbox/blob/master/docs/user-guide/install-package.md#docker-userns-remap that "Starting with Sysbox v0.5.0, configuring Docker in userns-remap mode is no longer required, even if the host has no support for shiftfs. However, without shiftfs, you will need a host with kernel >= 5.12 so that Sysbox can use the kernel's ID-mapped mounts feature." - it doesn't work unfortunately.
Full error message:
When I add
"userns-remap": "sysbox"
, it starts working.The container image is based on "ubuntu:22.04".
I wanted some minimally changed configuration to work, since it's said that sysbox version and kernel version are new enough for it all to work without userns-remap.
The text was updated successfully, but these errors were encountered: