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

2025-02-18 Thread Yassine Chaouche
Hello all, I have been advised to use systemd-nspawn and machinectl in place of chroot to run services from a cloned, working remote host. The cloning was done using rsync of the root filesystem (/) into a location in the new host, then linking that location from /var/lib/machines/ When I star

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

2025-02-18 Thread Yassine Chaouche
Le 2/18/25 à 14:07, Kevin P. Fleming a écrit : On Tue, Feb 18, 2025, at 07:32, Yassine Chaouche wrote: I tried systemctl on the host root@messagerie-recup[10.10.10.20] ~ # systemctl status -M clone-messagerie Failed to read server status: Transport endpoint is not connected root

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

2025-02-19 Thread Yassine Chaouche
Le 2/18/25 à 11:53, Yassine Chaouche a écrit : Hello all, I have been advised to use systemd-nspawn and machinectl in place of chroot to run services from a cloned, working remote host. Another interresting behavior is when I start it with the UID shifting feature -U $ systemd-nspawn