Re: rsync copyed systemd-nspawn container won't start

From	Alexandre Rossi <niol@zincube.net>
Newsgroups	linux.debian.user
Subject	Re: rsync copyed systemd-nspawn container won't start
Date	2022-01-12 09:20 +0100
Message-ID	<DEGRH-622-1@gated-at.bofh.it> (permalink)
References	<DEqMW-3Xo-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Hi,

[...]
> Jan 11 15:22:55 dhanna systemd-nspawn[21268]: Failed to create
> /init.scope control group: Operation not permitted
[...]
> Then I try it with
> 
> debootstrap --variant=minbase --include
> systemd,vim,libterm-readline-gnu-perl,iproute2,dialog,dbus stretch
> /var/lib/machines/foo
> 
> it work as expected.
> 
> Any ideas?

This may be related to systemd<236 in the container.

I would try one of the workarounds mentionned in https://github.com/systemd/systemd/issues/9563 :
- passing systemd.legacy_systemd_cgroup_controller=yes to systemd via
  Parameters=
- try with systemd-nspawn ... --private-users=0 --private-users-chown

Alex

Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

rsync copyed systemd-nspawn container won't start basti <mailinglist@unix-solution.de> - 2022-01-11 16:00 +0100
  Re: rsync copyed systemd-nspawn container won't start Alexandre Rossi <niol@zincube.net> - 2022-01-12 09:20 +0100

csiph-web