3 ms·

That's not what I remember. Wikipedia backs up that recollection as well [0], marking systemd's initial release in 2010. Docker's initial release is listed as

by oso2k 6y ago

That's not what I remember. Wikipedia backs up that recollection as well [0], marking systemd's initial release in 2010. Docker's initial release is listed as 2013 [1]. Maybe that was true of the dotCloud internal releases, and certainly, not all of the EL and other Linux distros had not adopted systemd during 2010 - 2013. Certainly after 2014 or 2015, systemd had spread to the major Linux distros so Docker could have chosen to take a systemd-based approach at that point. [0] https://en.wikipedia.org/wiki/Systemd https://en.wikipedia.org/wiki/Systemd [1] https://en.wikipedia.org/wiki/Docker_(software) https://en.wikipedia.org/wiki/Docker_(software)

westurner 6y ago
Are there other systemd + containers solutions? "Chapter 4. Running containers as Systemd services with Podmam" https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html/managing_containers/running_containers_as_systemd_services_with_podman https://access.redhat.com/documentation/en-us/red_hat_enterp... AFAIU, when running containers with systemd: - logs go to journald by default - there's no docker-compose for just the [name-prefixed] containers in the docker-compose.yml, - you can use systemd unit template parametrization - it's not as easy to collect metrics on every container on the system without a read-only docker socket: how many containers are running, how much RAM quota are they assigned and utilizing? What are the filesystem and port mappings? - you can run containers as non-root - you can run containers in systemd timer units - you use runC to handle seccomp ... You can do cgroups and namespaces with just systemd; but keeping chroots/images upgraded is outside the scope of systemd: where is the ideal boundary between systemd and containers? See this comment regarding per-container MAC MCS labels: https://news.ycombinator.com/item?id=23430959 https://news.ycombinator.com/item?id=23430959 There's much additional complexity that justifies k8s / OpenShift: when would I want to manage containers with just systemd units?

by oso2k 6y ago

westurner 6y ago

Are there other systemd + containers solutions? "Chapter 4. Running containers as Systemd services with Podmam" https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html/managing_containers/running_containers_as_systemd_services_with_podman https://access.redhat.com/documentation/en-us/red_hat_enterp... AFAIU, when running containers with systemd: - logs go to journald by default - there's no docker-compose for just the [name-prefixed] containers in the docker-compose.yml, - you can use systemd unit template parametrization - it's not as easy to collect metrics on every container on the system without a read-only docker socket: how many containers are running, how much RAM quota are they assigned and utilizing? What are the filesystem and port mappings? - you can run containers as non-root - you can run containers in systemd timer units - you use runC to handle seccomp ... You can do cgroups and namespaces with just systemd; but keeping chroots/images upgraded is outside the scope of systemd: where is the ideal boundary between systemd and containers? See this comment regarding per-container MAC MCS labels: https://news.ycombinator.com/item?id=23430959 https://news.ycombinator.com/item?id=23430959 There's much additional complexity that justifies k8s / OpenShift: when would I want to manage containers with just systemd units?