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

App Request: Lazytainer #365

Open
6 tasks done
Ryah opened this issue May 30, 2024 · 1 comment
Open
6 tasks done

App Request: Lazytainer #365

Ryah opened this issue May 30, 2024 · 1 comment
Labels
AppRequest Request for new application

Comments

@Ryah
Copy link

Ryah commented May 30, 2024

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?

  • I will you help with making docs if this gets picked up.
  • I will you help with testing.

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.

@Ryah Ryah added the AppRequest Request for new application label May 30, 2024
@maximuskowalski maximuskowalski changed the title App Request: Name of app App Request: Lazytainer May 30, 2024
@owine
Copy link
Collaborator

owine commented May 30, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AppRequest Request for new application
Projects
None yet
Development

No branches or pull requests

2 participants