Page 1 of 1

run_woof using systemd-nspawn instead of chroot

Posted: Fri Nov 04, 2022 11:22 pm
by Chrysolite Azalea

Hello everyone! I've forked the run_woof project and replaced chroot with systemd-nspawn. The advantages of it:

  • Various virtual filesystems are now handled by systemd-nspawn and don't have to be handled by run_woof
  • systemd-nspawn containers can be managed by machinectl utility
  • PID namespace isolation (system processes are not seen from the Puppy Linux container)

The main disadvantage is that it cannot be used on systems that lack systemd-nspawn, that includes a lot of Puppy Linux systems. This is why I decided not to make a pull request -- because chroot is more universal. However, it can be used to run woof-CE on mainstream distributions.