"Tim Woodall" writes:
> Don't know about systemd-nspawn but I do something like this using
> unshare, binfmt-support and qemu-user-static.
>
> I don't have to do anything at all other than create the file system
> with the emulated architecture and then chroot into it with those
> packages instal
On Wed, 21 Aug 2024, Steve Keller wrote:
Can I run a container for a different CPU architecture using
systemd-nspawn? I can easily install on my amd64 host a Debian
container of the same architecture and run that:
Don't know about systemd-nspawn but I do something like this using
unshare, bi
"Markus Schönhaber" writes:
> No. systemd-nspawn does indeed simply run a container. You can think of
> that as a chroot on steroids. This means, everything inside the
> container is run using the host kernel. Or to put it the other way
> round: what the host kernel can't execute won't run.
Actua
21.08.24, 16:56 +0200, Steve Keller:
> Can I run a container for a different CPU architecture using
> systemd-nspawn?
No. systemd-nspawn does indeed simply run a container. You can think of
that as a chroot on steroids. This means, everything inside the
container is run using the host kernel. Or
4 matches
Mail list logo
