Arch Linux

N.T.

Member

Registered: 2021-03-01

Posts: 27

[Solved] systemd-nspawn: no space left on device

Hi! I'm trying to boot a minimal Arch Linux container from Debian.

[user@debian ~] $ sudo apt -V --no-install-recommends --no-install-suggests install systemd-container
[user@debian ~] $ sudo mc -e /var/lib/machines/arch/etc/pacman.d/mirrorlist
[root@debian ~] # echo 'pts/0' >> /var/lib/machines/arch/etc/securetty

$ sudo systemd-nspawn -D /var/lib/machines/arch
[root@arch ~]# pacman-key --init && pacman-key --populate archlinux
[root@arch ~]# pacman -Syu --needed base
[root@arch ~]# passwd
[root@arch ~]# logout

[user@debian ~] $ sudo sysctl -w kernel.unprivileged_userns_clone=1

[user@debian ~] $ sudo systemd-nspawn -b -U -D /var/lib/machines/arch
Spawning container arch on /var/lib/machines/arch.
Press ^] three times within 1s to kill container.
Selected user namespace base XXXXXXXXXX and range 65536.
Failed to fork inner child: No space left on device 

I changed the location of the container to ~/.arch.

[user@debian ~] $ sudo systemd-nspawn -b -U -D ~/.arch
Spawning container arch on /home/user/.arch.
Press ^] three times within 1s to kill container.
Selected user namespace base XXXXXXXXXX and range 65536.
Failed to fork inner child: No space left on device 

There is a lot of free space on the disk. What is the reason then?

Edit: Debian testing, Linux 5.10.13, systemd 247.

Last edited by N.T. (2021-03-07 11:49:08)

N.T.

Member

Registered: 2021-03-01

Posts: 27

Re: [Solved] systemd-nspawn: no space left on device

The culprit was Kernel Self Protection . Solution:

# sysctl -w user.max_user_namespaces=1