>>> Colin Guthrie <gmane@xxxxxxxxxxxxxx> schrieb am 13.06.2022 um 14:58 in Nachricht <t87c9t$lon$1@xxxxxxxxxxxxx>: > Ulrich Windl wrote on 13/06/2022 09:09: >> Hi! >> >> Two questions: >> 1) Why can't I use "systemctl start network" in a chroot environment (e.g. > mounting the system from a rescue medium to fix a defective kernel)? When I > try I get: "Running in chroot, ignoring command 'start'" >> 2) How can I start the network using systemd? > > You may wish to consider "booting" the container rather than just chrooting. No container involved; an unbootable system instead, and I'd like to have networking available for repair. So obviously I cannot boot. Without systemd it wouldn't be a problem. Regards, Ulrich > > Combined with IPVLAN or similar (which systemd-nspawn makes easy) you > can bring up a namespaced network interface inside the container > completely isolated from the host. > > I do this for various setups and it works pretty well. > > Col