I was intrigued by this post on socket activated containers with systemd. The basic premise is:
systemdopens a socket on the host and listens for connections.- When a client connections,
systemdspawns a new container. - The host
systemdpasses the connected socket to the containersystemd. - Services in the container receive these sockets from the container
systemd.
This is a very neat idea, since it delegates all the socket listening to the host and only spins up container and service resources when necessary.