Skip to content
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

Support CapAdd And CapDrop in Docker driver #3695

Closed
samart opened this issue Dec 28, 2017 · 9 comments
Closed

Support CapAdd And CapDrop in Docker driver #3695

samart opened this issue Dec 28, 2017 · 9 comments

Comments

@samart
Copy link

samart commented Dec 28, 2017

In order to run docker containers more securely, i would like to drop container privileges - and hence pass some extra args for the nomad - docker engine api container create call.

"CapAdd": [
".."
],
"CapDrop": [
"..."
],

http://www.projectatomic.io/blog/2016/01/how-to-run-a-more-secure-non-root-user-container/
https://opensource.com/business/15/3/docker-security-tuning

@schmichael
Copy link
Member

References for implementers:

@filipochnik
Copy link
Contributor

I can try implementing this if no one is working on it yet.

@schmichael
Copy link
Member

@filipochnik No one on the HashiCorp team has gotten around to it yet, so please do!

@filipochnik
Copy link
Contributor

@schmichael I think I have it working. One thing that came to my mind in the process is that it might be useful to have an option to specify whitelist and blacklist for capabilities in the client config (probably here https://www.nomadproject.io/docs/drivers/docker.html#client-configuration). What do you think? It looks a bit tricky to implement given the special semantics of the ALL capability.

@alxark
Copy link

alxark commented Jan 17, 2018

@filipochnik could you please check for tmpfs and readonlyrootfs options for docker driver? I think you can implement them really fast after digging to nomad docker driver.

@filipochnik
Copy link
Contributor

@alxark I'll try to, once I'm done with this :)

@alxark
Copy link

alxark commented Jan 17, 2018

@filipochnik will be just great =)

@dadgar
Copy link
Contributor

dadgar commented Jan 23, 2018

Closed by #3754

@github-actions
Copy link

github-actions bot commented Dec 4, 2022

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants