[systemd-devel] Starting a container with machinectl vs nspawn

Kevin P. Fleming lists.systemd-devel at kevin.km6g.us
Tue Feb 18 13:07:29 UTC 2025


On Tue, Feb 18, 2025, at 07:32, Yassine Chaouche wrote:
> I tried systemctl on the host
>
>
>    root at messagerie-recup[10.10.10.20] ~ # systemctl status -M clone-messagerie
>    Failed to read server status: Transport endpoint is not connected
>    root at messagerie-recup[10.10.10.20] ~ #

It is very likely that the machine-management tools in systemd 252 are unable to communicate with systemd 215 inside the container. You will probably need to treat that container as if it did not have systemd running inside it.


More information about the systemd-devel mailing list