You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Docker containers can take up a lot of resources, especially on less powered devices. This allows specific docker containers to start or stop depending on traffic.
A good example is for Minecraft servers. Modded servers can take up a lot of RAM and CPU that's just wasted if no one is online. Lazytainer allows the server to turn off after a configurable amount of time, and then start the server when someone tries to connect to it.
This is different than docker pause as pause doesn't free up used memory, so if the container is already using a lot of RAM, it's now locked. This is a full auto stop and start.
We’d accept a PR for this, but I don’t see a ton of value in the Saltbox ecosystem to be honest. First and foremost, Saltbox doesn’t support ARM at all which excludes the majority of low powered devices that would seem to benefit from something like this. Second, Saltbox leverages the reverse proxy wherever possible which does not appear comparable here so the benefit is limited to roles that separately bind their own ports (I.e. game servers, as you identified) which is a small minority. Third, there is nothing specific needed to actually use this with Saltbox as you can deploy a compose file alongside and use the inventory system to apply labels and network mode as needed. That is probably the best path for a user that wants to use this.
Lazytainer
What does it do? Why? Please describe.
Docker containers can take up a lot of resources, especially on less powered devices. This allows specific docker containers to start or stop depending on traffic.
A good example is for Minecraft servers. Modded servers can take up a lot of RAM and CPU that's just wasted if no one is online. Lazytainer allows the server to turn off after a configurable amount of time, and then start the server when someone tries to connect to it.
This is different than docker pause as pause doesn't free up used memory, so if the container is already using a lot of RAM, it's now locked. This is a full auto stop and start.
Links to further information
What are you willing to do to help?
Anything else you would like to add.
I feel like this would be very useful for people running saltbox on Raspberry Pi's or other low powered servers/shared VPS.
The text was updated successfully, but these errors were encountered: