IssueRaiser

Add the ability to map containers to a user host-side

_Before getting into the details, I want to point out that I suspect a feature like what I'm about to suggest could solve many permission related snags when using Docker._ _**So as to prevent this suggestion from getting mired in philosophical objections, this ticket is not advocating permanently storing credentials inside a container. I don't do that and I don't suggest anyone else do it either!**_ --- #### tldr; The current method of UID spoofing _inside of a container_ via `--user` has limitations that end up mandating entire ecosystems of one-offs and very problematic workarounds to massage container state into the right frame of mind. This is worsened by the fact that the need to perform these workarounds is influenced by what platform you are calling Docker from. The feature I'd like to request is to have a flag added to `docker run` (and equivalents) that tells Docker to map all filesystem operations that a container performs to a specific user host-side. This is very different to `--user` which simply sets the user of the process that runs inside the container. If you're interested in an extended explanation, read on! --- #### Rationale We've all heard about people having issues with temporarily binding SSH credentials and similar `$UID` & `$USER` related difficulties. Something that I've noticed when using Docker on OSX and Windows however is that I'm actually freed from the challenges of ensuring my ephemeral development containers (my primary use case) ar

Posted by atrauzzi on Apr 29, 2016, 12:55 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments

github (Other)

Add the ability to map containers to a user host-side

atrauzziApr 29, 2016, 12:55 PM

_Before getting into the details, I want to point out that I suspect a feature like what I'm about to suggest could solve many permission related snags when using Docker._ _**So as to prevent this suggestion from getting mired in philosophical objections, this ticket is not advocating permanently storing credentials inside a container. I don't do that and I don't suggest anyone else do it either!**_ --- #### tldr; The current method of UID spoofing _inside of a container_ via `--user` has limitations that end up mandating entire ecosystems of one-offs and very problematic workarounds to massage container state into the right frame of mind. This is worsened by the fact that the need to perform these workarounds is influenced by what platform you are calling Docker from. The feature I'd like to request is to have a flag added to `docker run` (and equivalents) that tells Docker to map all filesystem operations that a container performs to a specific user host-side. This is very different to `--user` which simply sets the user of the process that runs inside the container. If you're interested in an extended explanation, read on! --- #### Rationale We've all heard about people having issues with temporarily binding SSH credentials and similar `$UID` & `$USER` related difficulties. Something that I've noticed when using Docker on OSX and Windows however is that I'm actually freed from the challenges of ensuring my ephemeral development containers (my primary use case) ar

Comments (0)

No comments yet. Start the discussion.

Comment on this issue