I thought of using docker in my runit artix and looking at the docker-runit package I see that it uses/creates a cgroup with name
/sys/fs/cgroup/systemd
I suppose that this is because the default docker setup uses a cgroup named systemd.
I'm not particularly anti-systemd, but in artix how do we know if systemd has left an actual requirement about or if it's just a token/name memory.
I don't know if this fits your needs, but podman seems to be the better choice:
- it is compatible with Docker containers
- it runs in the user security context https://betterstack.com/community/guides/scaling-docker/podman-vs-docker/ (https://betterstack.com/community/guides/scaling-docker/podman-vs-docker/)
- does not alter the firewall rules as docker does (https://geoff.tuxpup.com/posts/psa_docker_edits_firewall_rules/)
- it has several GUI management interfaces ( Pods (https://github.com/marhkb/pods), Podman Desktop (https://github.com/containers/podman-desktop), Container Desktop (https://github.com/iongion/container-desktop) )
Give it a try, you will not regret it.
That page seems to imply that podman relies a lot on systemd which I would not care for.
While there is an artix pkg it's likely that a lot of the online info will rely on systemd specifics.
I'll certainly take a look anyhow.
There is a nuance: podman does not rely on systemd, it can work with systemd.
Gosh, you cannot grasp the damage systemd has done until you try to swim against the current !
On my Artix (with dinit) I'm happily using podman, importing container images from wherever I need; I have a small repo (https://codeberg.org/SoftExpert/dinit-services) with some services and a description on how I configured it - including the configuration for using podman.
I hope it helps you even a tiny bit ...