Replies: 5 comments
-
Sorry for the delayed response. Very interesting scenario! I've never actually used user namespace isolation for docker environments so this never even occurred to me. I suspect this is only going to be an issue for tasks that need to perform actions on containers not in the same user space as Chadburn's container. Did you configure Chadburn to run in a different user space than your other containers? Your use-case is not typical but highly encouraged! As a fan of better security practices, I'll definitely be looking into this in the near future. Sadly though, this may be just outside my skill level but I'll be here for the ride in case anyone else jumps in to help with this. Until then, I'll try and carve out some time soon to look into this. |
Beta Was this translation helpful? Give feedback.
-
So here is a thing, as already shown the |
Beta Was this translation helpful? Give feedback.
-
Thanks for the tips: I'll try adding |
Beta Was this translation helpful? Give feedback.
-
I'd love to know if that worked for you. I'm about to begin a major re-work of Chadburn and releasing it under version 2.x. Knowing this now would save me some time in initial testing. |
Beta Was this translation helpful? Give feedback.
-
I believe that you should be running the containers that require to talk to the docker socket in the host user namespace. |
Beta Was this translation helpful? Give feedback.
-
i get the following errors wheen running Chadburn (via Docker Compose) on a Docker host where user namespace isolation is enabled (
"userns-remap": "default"
in/etc/docker/daemon.json
file):I tried adding permissions to
/var/run/docker.sock
withsetfacl
without success (still getting the same errors),getfacl -R /var/run/docker.sock
returns:Is Chadburn compatible with user namespace isolation?
PS: Also tested with Ofelia : same result (mcuadros/ofelia#176)
Beta Was this translation helpful? Give feedback.
All reactions