Ubuntu 20.04 (20240609) does not start container systemd as PID 1

[aminvakil]

Ubuntu 20.04 (20240609) does not start container systemd as PID 1

From this release (probably because of docker bump from 24.0.9 to 26.1.3), I cannot run containers which have systemd as PID 1.

https://github.com/aminvakil/nvchecker/blob/a66f1b92eedabc20dca590400aff91cd70b3131d/.github/workflows/aur.yml#L25

docker run --detach --privileged -v /sys/fs/cgroup:/sys/fs/cgroup:ro -v "${PWD}":/nvchecker quay.io/aminvakil/archlinux:latest

So something like this which gets created in https://github.com/aminvakil/docker-archlinux/blob/master/Dockerfile:

FROM archlinux:base-20240101.0.204074

ENV container docker

LABEL maintainer="Amin Vakil <info@aminvakil.com>"

RUN pacman -Syu --noconfirm && \
    rm -rf /var/cache/pacman/pkg/*

ENTRYPOINT ["/usr/lib/systemd/systemd"]

does not work.

This is not just archlinux related, there are multiple other images getting created in https://github.com/aminvakil/docker-os-systemd/tree/main/images which gets used in other repositories like https://github.com/aminvakil/ansible-role-docker-installation/, but they do not work as well and container exits with error code 255.

I've tested and ubuntu 22 and ubuntu 24 has this problem as well, they are both using docker 26 as well.

I've also tested this on an Archlinux and ubuntu 24 instance locally and both worked.

[aminvakil]

It got fixed with running docker run like this:

docker run --detach --privileged --cgroup-parent=docker.slice --cgroupns private --tmpfs /tmp --tmpfs /run --tmpfs /run/lock -v "${PWD}":/nvchecker quay.io/aminvakil/archlinux:latest