Bug#915397: systemd-container: fails to start a container going through machines.target or machinectl

[Michael Biebl]

Am 03.12.18 um 14:53 schrieb ed.gomez at free.fr:

> Reproduction steps
> ==================
> 
>     # as root, i don't have a big /, so i'll be using /home. Do as you see fit
>     $ mkdir -p /home/chroots
>     $ cd /home/chroots
>     $ debootstrap stable stable
>     [... does its work successfully ... ]
>     $ ln -sf /home/chroots/stable /var/lib/machines/stable
>     $ systemctl enable machines.target
>     $ systemctl enable systemd-nspawn at stable
>     
>     # then this last command is executed w/ patched or unpatched
>     # systemd-container package
>     $ machinectl start stable
>     # or 
>     $ systemctl start systemd-nspawn at stable

This works just fine here (Debian sid host system, Debian stretch inside
the container), executed exactly the commands you provided.

I assume the main difference is that you are not using a Debian provided
kernel and I do?



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20181203/c47243fb/attachment.sig>