Edit history

Hmm.

A lot of these are going to be just request-driven. That is, they aren’t really doing anything while idling. Thus, they don’t really need to be actually running.

If the idle memory usage is an actual concern — and honestly, the OS is probably just gonna page things out if the software is truly idle and it needs the memory for something else and it has paging space…I kind of assume that someone has built some sort of system that works like inetd, which avoided leaving non-containerized servers running. You register a port, and then inetd listens on it. When someone connects, it starts up the daemon in question (say, Apache or whatever). Just need to start a container on demand here. Maybe close it down after a long-enough period of inactivity.

EDIT:

old.reddit.com/…/startrun_a_container_when_incomi…

Start/run a container when incoming traffic detected

Sounds like you’re looking for inetd.

A more modern version of this is systemd socket activation.

Podman supports socket activation since version 3.4.0 (released Sep 2021).

Hmm.

A lot of these are going to be just request-driven. That is, they aren’t really doing anything while idling.

If the idle memory usage is an actual concern — and honestly, the OS is probably just gonna page things out if the software is truly idle and it needs the memory for something else and it has paging space…I kind of assume that someone has built some sort of system that works like inetd, which avoided leaving non-containerized servers running. You register a port, and then inetd listens on it. When someone connects, it starts up the daemon in question (say, Apache or whatever). Just need to start a container on demand here. Maybe close it down after a long-enough period of inactivity.

EDIT:

old.reddit.com/…/startrun_a_container_when_incomi…

Start/run a container when incoming traffic detected

Sounds like you’re looking for inetd.

A more modern version of this is systemd socket activation.

Podman supports socket activation since version 3.4.0 (released Sep 2021).

Hmm.

A lot of these are going to be just request-driven. That is, they aren’t really doing anything while idling.

If the idle memory usage is an actual concern — and honestly, the OS is probably just gonna page things out if the software is truly idle and it needs the memory for something else and it has paging space…I kind of assume that someone has built some sort of system that works like inetd, which avoided leaving non-containerized servers running. You register a port, and then inetd listens on it. When someone connects, it starts up the daemon in question (say, Apache or whatever). Just need to start a container on demand here. Maybe close it down after a long-enough period of inactivity.

Hmm.

A lot of these are going to be just request-driven. That is, they aren’t really doing anything while idling.

If the idle memory usage is an actual concern — and honestly, the OS is probably just gonna page things out if the software is truly idle and it needs the memory for something else and it has paging space…I kind of assume that someone has built some sort of system that works like inetd, which avoided leaving non-containerized servers running. You register a port, and then inetd listens on it. When someone connects, it starts up the daemon in question (say, Apache or whatever). Just need to start a container on demand here.

Hmm.

A lot of these are going to be just request-driven.

If the idle memory usage is an actual concern…I kind of assume that someone has built some sort of system that works like inetd — you register a port, and then inetd listens on it. When someone connects, it starts up the daemon. Just need to start the container on demand.