#asahi · 2024-10-18 08:49
manniefestoI'll post here for future ref#asahi · 2024-10-18 08:48
manniefestoOk, I've just tried my issue on a Debian box with the same problems :/#asahi · 2024-10-18 07:07
manniefestos/be/by#asahi · 2024-10-18 07:07
manniefestoI think it's pretty much standard practice in podman these days, --systemd=true is set be default#asahi · 2024-10-18 07:07
manniefestoThis post from 2019 explains some of the reasoning behind using systemd in a container: https://developers.redhat.com/blog/2019/04/24/how-to-run-systemd-in-a-container#enter_podman#asahi · 2024-10-18 07:05
manniefestoI'm also seeing some errors regarding systemd when I do an apt upgrate for example#asahi · 2024-10-18 07:05
manniefestoHi, as far as I can tell it's trying to start a Postgresql service inside the container#asahi · 2024-10-18 06:53
manniefestoThanks anyway :)#asahi · 2024-10-18 06:52
manniefestoI was hoping that it may have been discussed previously :)#asahi · 2024-10-18 06:52
manniefestoIt's possible that it's not, but the same config has worked on other distro's, so I think it may be related to default config possibly.#asahi · 2024-10-18 06:51
manniefestoThe full error message being "System has not been booted with systemd as init system (PID 1). Can't operate."#asahi · 2024-10-18 06:50
manniefestoI have tried podman, moby-engine and containerd with the same result, so I currently conclude that it must be systemd configuration on my asahi fedora install.#asahi · 2024-10-18 06:49
manniefestoEG: when running a container in 'privileged' mode I still can not access systemd from the container itself.#asahi · 2024-10-18 06:48
manniefestoI'm having some trouble with systemd and containers#asahi · 2024-10-18 06:48
manniefestoAha, thanks, apologies :)#asahi · 2024-10-18 06:45
manniefestoHi, is this the best place to ask for some support?