Open jscotka opened 3 years ago
+1 this would be awesome to have
Sounds interesting! I've quickly experimented with the example above and it worked nice.
dnf install --releasever 34 --nogpg --installroot=/tmp/spawn --repofrompath=f34,https://dl.fedoraproject.org/pub/fedora/linux/releases/34/Everything/x86_64/os/ systemd
What are the advantages of nspawn
when compared to using podman
?
Sounds interesting! I've quickly experimented with the example above and it worked nice.
dnf install --releasever 34 --nogpg --installroot=/tmp/spawn --repofrompath=f34,https://dl.fedoraproject.org/pub/fedora/linux/releases/34/Everything/x86_64/os/ systemd
What are the advantages of
nspawn
when compared to usingpodman
?
nspawn is closer to system and also running systemd by default is the main advantage, so from that perspective nspawn it is more than just container.
as we've discussed on IRC,
systemd-nspawn
could be very nice solution for testing, it is something between virtualization and containerization with docker/podman. Implementation could be easy and could be beneficial, because it could provide still new sources because it can use system or remore repos.Steps are
then via
machinectl shell machine_name command
run the commands on target machine e.g. run test there.and have some option
like tmt run -a provision -h nspawn
without any other param it will use local repos, in case of multiple-r/--repo
param used, use this repo, with some aliases I can imagine e.g.-r centos-8
will be traslated to url to centos-8