It seems that systemd-nspawn, together with machinectl can use qcow2 images directly.

This means I could use the images genereted by kiwi to start containers (for development and for running the tests).

The nspawn containers are closer to VMs.

I was already able to run a full Suse Manager inside an nspawn container starting from an qcow2 image used for the tests.


Looking for hackers with the skills:

Nothing? Add some keywords!

This project is part of:

Hack Week 15


  • over 7 years ago: j_renner liked this project.
  • over 7 years ago: dmaiocchi liked this project.
  • over 7 years ago: mdinca started this project.
  • over 7 years ago: mdinca originated this project.

  • Comments

    • dmacvicar
      over 7 years ago by dmacvicar | Reply

      Network setup is interesting, docker manages a docker bridge and ip addresses for you.

      You can connect nspawn to the libvirt bridge (that has dhcp):

      sudo systemd-nspawn -b -x --network-bridge=virbr0 -M manager-3.0

      However, just like you have to delete /etc/securetty, you need to move ifcfg-eth0 to ifcfg-host0 if you want to use the default host0 name, or, use --network-veth-extra but then you need to do the bridge operations yoursef.

    Similar Projects

    This project is one of its kind!