ContainerNursery

Puts Docker Containers to sleep and wakes them back up when they're needed.

  • Infrastructure
  • Network Services
  • Productivity
  • Tools & Utilities
Puts Docker Containers to sleep and wakes them back up when they're needed. Written in Node.js, this application acts as a HTTP reverse proxy and stops Docker containers which haven't been accessed recently and starts them again when a new request comes in. ContainerNursery also makes sure there are no more active WebSocket connections before stopping the container. To improve the user experience a loading page is presented, which automatically reloads when the containers webserver is ready.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

22/100 Low

Maintained
0last commit 1067 days ago
Popular
48256 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
201 serious finding, 19 minor

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 23 days ago

GitHub stars
256
Open issues
17
Last commit
2023-12-20
License
MIT
Activity
stale

Checked 7 days ago - source: GitHub (ItsEcholot/ContainerNursery)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Default port & Docker socket ContainerNursery listens on port 80 by default for HTTP and connects to the Docker daemon via the /var/run/docker.sock socket; expose the container's port 80 and mount the host Docker socket when deploying. source

Fetched 47 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How does ContainerNursery handle a request to a stopped container?

It acts as an HTTP reverse proxy and starts the container when a new request comes in. A loading page is shown, then automatically reloads when the container's web server is ready.

Will ContainerNursery stop a container while a WebSocket is still active?

It checks that there are no active WebSocket connections before stopping the container.

Does ContainerNursery only pause containers or fully stop them?

It stops the container entirely rather than using a simple docker pause. This frees RAM and avoids unnecessary CPU wake-ups.

What makes a container go to sleep?

ContainerNursery stops Docker containers that have not been accessed recently.

Answers sourced from github.com, korben.info

Community

Collected 53 days ago - public community threads