-
Notifications
You must be signed in to change notification settings - Fork 392
ansible-container build: Conductor container fails when using user namespaces #967
Comments
Can you provide more details about ansible-container usage-scenario? In it's present state it is rather logically to use it to build images and push to some registry, while handle their deployment with some other workflow. |
I am trying to prevent any kind of privilege escalation on my host. I want my containers to run on an unprivileged user but there are processes within the container that need to run as root. Also I want to be able to write to files while developing. Here is more of my container.yml if that helps
|
My understanding, that current concept requires privileged mode, may be @j00bar can join the thread for the short explanation |
ISSUE TYPE
container.yml
OS / ENVIRONMENT
SUMMARY
ansible-container build
fails when using user namespaces. The conductor container is being run privileged but we cannot adduserns_mode: "host"
to the conductor."privileged mode is incompatible with user namespaces. You must run the container in the host namespace when running privileged mode".
STEPS TO REPRODUCE
Enable userns remap on the daemon: https://docs.docker.com/engine/security/userns-remap/#enable-userns-remap-on-the-daemon
Run:
EXPECTED RESULTS
ansible-container build
executes succesfullyACTUAL RESULTS
The text was updated successfully, but these errors were encountered: