-
Notifications
You must be signed in to change notification settings - Fork 39
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
Using Mouthful with User Namespaces #102
Comments
I got this working myself, so you can close this issue now. |
Correction. Although the comments loads in the webpage with namespaces enabled, I am not able to post comments. Each time I attempt to post a comment I get a
Inside the mouthful container I notice the
If I run mouthful with namespaces disabled (using
The problem with this is the process on the host is also set as root.
Thats the reason why running a container without namespaces is such a security risk. I'ts too easy for someone to gain root access to the host. So, my question is is there a way around this issue?? How can I use mouthful with namespaces enabled?? |
I was not aware that a thing called user namespaces existed, will look into it and investigate. |
OK, thanks. Scrap the part where I said " How would I make Mouthful use the Nginx user if I created a namespace for Nginx." though. I didn't understand Docker namespaces properly and that question is not relevant. |
Is it possible to use Mouthful with Dockers user namespaces?
I'd like to do this for security reasons.
I'm using Mouthful on a Centos 7 OS with a Nginx server.
How would namespacing work with mouthful? How would I make Mouthful use the Nginx user if I created a namespace for Nginx.
Docker namespace resources:
https://success.docker.com/article/introduction-to-user-namespaces-in-docker-engine
https://coderwall.com/p/s_ydlq/using-user-namespaces-on-docker
https://raesene.github.io/blog/2016/02/04/Docker-User-Namespaces/
https://www.linux.com/blog/learn/2017/8/hardening-docker-hosts-user-namespaces
https://www.jujens.eu/posts/en/2017/Jul/02/docker-userns-remap/
The text was updated successfully, but these errors were encountered: