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

Proposal: daemon defaults for runtime constraints #19023

Closed
geovanisouza92 opened this issue Dec 31, 2015 · 4 comments
Closed

Proposal: daemon defaults for runtime constraints #19023

geovanisouza92 opened this issue Dec 31, 2015 · 4 comments
Labels
kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny

Comments

@geovanisouza92
Copy link

Today, the resource constraints values is defined on each docker run command. Thinking about cloud-scale Docker deployment, could be nice to define this defaults on Docker daemon. I think that /etc/default/docker / DOCKER_OPTS could be a nice place to configure it. This way, each container would start with right resources.

@thaJeztah
Copy link
Member

Yes, I thought about this, but not sure if this is something that should be set on the daemon, or something that belongs in orchestration software; both can make sense, depending how you look at it.

Note that there's this proposal, that would allow applying "profiles" to containers; #18647

@thaJeztah thaJeztah added the kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny label Dec 31, 2015
@geovanisouza92
Copy link
Author

@thaJeztah You're about about the place. Swarm introduced an additional layer about "the right place" questions...

The proposal for profiles is really interesting.

@HackToday
Copy link
Contributor

seems orchestration layer is more meaning instead of add other options in docker daemon

@LK4D4
Copy link
Contributor

LK4D4 commented Sep 14, 2016

Seems like we'll have daemon-wide seccomp profiles soon. Implementing daemon wide constraints is indeed a task of orchestration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny
Projects
None yet
Development

No branches or pull requests

4 participants