I am deploying some non-critical serviecs using docker-compose, on a single host.
Despite docker does support setting resource upper bounds (cpu/memory limits) they are ignored in pratice.
I am aware that this is a documented behavior (https://docs.docker.com/compose/compose-file/#deploy is always open when I'm dealing with docker-compose).
However, I can't understand why it has been chosen not to enable these feature when running against a single docker daemon (instead of a swarm).
With this feature request I would like to ask for such options (the whole deployment.resources.limits subtree) to be enabled for non-swarm deployments too.
Describe the solution you'd like
Just pass the appropriate options to the underlying docker daemon.
Describe alternatives you've considered
Alternatives are the following:
- running the containers in a vm -> nullifies the point of running containers
- launch my containers using shell scripts that call the docker binary with appropriate options (I would really like not to).
I am deploying some non-critical serviecs using docker-compose, on a single host.
Despite docker does support setting resource upper bounds (cpu/memory limits) they are ignored in pratice.
I am aware that this is a documented behavior (https://docs.docker.com/compose/compose-file/#deploy is always open when I'm dealing with docker-compose).
However, I can't understand why it has been chosen not to enable these feature when running against a single docker daemon (instead of a swarm).
With this feature request I would like to ask for such options (the whole deployment.resources.limits subtree) to be enabled for non-swarm deployments too.
Describe the solution you'd like
Just pass the appropriate options to the underlying docker daemon.
Describe alternatives you've considered
Alternatives are the following: