[UPGRADE] Limit the size allocated to the Nextcloud container #1
Closed
opened 4 years ago by StephanSainleger
·
3 comments
Loading…
Reference in new issue
There is no content yet.
Delete Branch '%!s(MISSING)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
The Nextcloud container currently has no limitation of memory. That means it can grow up too the server capacity. In that extreme case, the other containers won't have enough free memory to run.
This situation leads to a global black out of all the containers.
IDEA#1: to have a parameter in the compose.yml file in order to give a limitation to the Nextcloud container. This parameter can be:
IDEA#2: generalize this parameter to all the containers (Odoo, Rocketchat,...)
Nice idea. Please note that you can already do those things (well most of them).
Indeed,
docker-compose
value in yaml allow you to pass on docker-compose options... and these exist already:https://docs.docker.com/compose/compose-file/compose-file-v2/#cpu-and-other-resources
and for units and all:
https://docs.docker.com/engine/reference/run/#runtime-constraints-on-resources
Just keep in mind the
docker-compose.yml
generated is currently version 2.Depending if we want to add some level of abstraction to these notions, we can think about adding a specific options right in
0k-compose
.For now here an example of how you can achieve this in your
compose.yml
:If you have a general feeling of how resources should always be attributed, or at least decided charm by charm. I could automatically then generate these limit by following your rule.
Thank you for shearing amazing post this is post very useful for me.
Adarsh Park Heights price
Adarsh Property
Adarsh Park Heights in Bangalore
Sumadharu Folium
SUMADHURA FOLIUM
Prestige Park Grove Whitefield Price
Prestige Park Grove Whitefield
Adarsh Tropica Bangalore
Adarsh Tropica Bangalore Sarjapur
Prestige Lavender Fields
Brigade Calista Bangalore
Adarsh Park Land