Closed robbyoconnor closed 7 years ago
The container runs as root to fix the UID/GID mismatch problems that occur with Linux bind mounts. Do you have a better way to fix this?
i...guess...I'll hack at it and see what kind of a middle ground I can arrive at
I don't think you're going to do much better, welcome to suggestions though.
Let's explore why we care about running or not running as root:
aosp
user. All steps in the build process are hence executed unprivileged, so any rogue build scripts in Android should be no more privileged this the aosp
user.docker run --rm -it -v /:/ubuntu-root ubuntu
and do whatever they want.What are you trying to protect against?
Digging in more, it's possible that the root privilege could be workaround since it appears progress has been made on https://github.com/docker/docker/issues/7198 -- perhaps you can investigate that?
I'd like to know if the fix mitigates the need for the entry-point work around and how widely the merged feature is distributed (i.e. what docker release was it first included in, how many people are running that release or later?)
Let's just act like this never happened :smile:
Let's just act like this never happened :smile:
I'd love to not run as root, but I think we're blocked by Docker features for the time being. :)
Thanks for investigating though!
Root in containers means root in the host. This is bad.