Arch Linux

replabrobin

Member

Registered: 2010-05-06

Posts: 235

[SOLVED] systemd-nspawn container df strangeness

I'm running arch x64 fully up to date with systemd-213-9. I built a container following the wiki article and after

systemd-nspawn -bD ~/MyContainer

I logged in and started playing around I noticed that df reports some failures eg

root@MyContainer ~]# df
df: '/run/user/1000': No such file or directory
df: '/run/user/1000/gvfs': No such file or directory
df: '/proc/kmsg (deleted)': No such file or directory
df: '/proc/sys/kernel/random/boot_id (deleted)': No such file or directory
Filesystem     1K-blocks     Used Available Use% Mounted on
/dev/sda1      147418744 85779872  54127364  62% /
dev              1413900        4   1413896   1% /dev
tmpfs            1413900        0   1413900   0% /dev/shm
tmpfs            1413900        0   1413900   0% /sys/fs/cgroup
run              1413900       44   1413856   1% /run
tmpfs            1413900        0   1413900   0% /tmp
tmpfs            1413900        4   1413896   1% /dev
tmpfs            1413900        0   1413900   0% /dev/shm
tmpfs            1413900       44   1413856   1% /run
tmpfs            1413900        0   1413900   0% /sys/fs/cgroup
tmpfs            1413900        0   1413900   0% /tmp
tmpfs             282784        0    282784   0% /run/user/0
[root@MyContainer ~]# 

1000 is my normal non-root login id, but that should not appear in the container. The container environment doesn't appear to contain any reference to user robin. Can I fix these missing filesystems/errors?

Edit: Apparently df doesn't work properly; we must now use redhat's findmnt command.

Last edited by replabrobin (2014-06-16 20:55:51)