df returns no results in some situations
I am running Alpine 3.4 in a container and df returns no lines of output other than the header, but returns a zero return code:
moby:~# docker run alpine df
Filesystem 1K-blocks Used Available Use% Mounted on
busybox or Debian are fine. The only odd thing about this container is it has a very long first line for /proc/mounts:
docker run alpine cat /proc/mounts
overlay / overlay
rw,relatime,lowerdir=/var/lib/docker/overlay/679fa932029d07180dc9f22198f5462375bcd5e23e83a58105f72cc8a7bbde30/root,upperdir=/var/lib/docker/overlay/700ad8e3d622803dd63f20613d9cc3404cacd3d42badedbc0426e61cbd79001b/upper,workdir=/var/lib/docker/overlay/700ad8e3d622803dd63f20613d9cc3404cacd3d42badedbc0426e61cbd79001b/work
0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,mode=755 0 0
devpts /dev/pts devpts
rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666 0 0
sysfs /sys sysfs ro,nosuid,nodev,noexec,relatime 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,relatime,mode=755 0
0
openrc /sys/fs/cgroup/openrc cgroup
ro,nosuid,nodev,noexec,relatime,release_agent=/lib/rc/sh/cgroup-release-agent.sh,name=openrc
0 0
cpuset /sys/fs/cgroup/cpuset cgroup
ro,nosuid,nodev,noexec,relatime,cpuset 0 0
cpu /sys/fs/cgroup/cpu cgroup ro,nosuid,nodev,noexec,relatime,cpu 0 0
cpuacct /sys/fs/cgroup/cpuacct cgroup
ro,nosuid,nodev,noexec,relatime,cpuacct 0 0
blkio /sys/fs/cgroup/blkio cgroup ro,nosuid,nodev,noexec,relatime,blkio
0 0
memory /sys/fs/cgroup/memory cgroup
ro,nosuid,nodev,noexec,relatime,memory 0 0
devices /sys/fs/cgroup/devices cgroup
ro,nosuid,nodev,noexec,relatime,devices 0 0
freezer /sys/fs/cgroup/freezer cgroup
ro,nosuid,nodev,noexec,relatime,freezer 0 0
net_cls /sys/fs/cgroup/net_cls cgroup
ro,nosuid,nodev,noexec,relatime,net_cls 0 0
perf_event /sys/fs/cgroup/perf_event cgroup
ro,nosuid,nodev,noexec,relatime,perf_event 0 0
net_prio /sys/fs/cgroup/net_prio cgroup
ro,nosuid,nodev,noexec,relatime,net_prio 0 0
hugetlb /sys/fs/cgroup/hugetlb cgroup
ro,nosuid,nodev,noexec,relatime,hugetlb 0 0
pids /sys/fs/cgroup/pids cgroup ro,nosuid,nodev,noexec,relatime,pids 0
0
mqueue /dev/mqueue mqueue rw,nosuid,nodev,noexec,relatime 0 0
/dev/vda2 /etc/resolv.conf ext4 rw,relatime,data=ordered 0 0
/dev/vda2 /etc/hostname ext4 rw,relatime,data=ordered 0 0
/dev/vda2 /etc/hosts ext4 rw,relatime,data=ordered 0 0
shm /dev/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=65536k 0 0
proc /proc/bus proc ro,nosuid,nodev,noexec,relatime 0 0
proc /proc/fs proc ro,nosuid,nodev,noexec,relatime 0 0
proc /proc/irq proc ro,nosuid,nodev,noexec,relatime 0 0
proc /proc/sys proc ro,nosuid,nodev,noexec,relatime 0 0
proc /proc/sysrq-trigger proc ro,nosuid,nodev,noexec,relatime 0 0
tmpfs /proc/kcore tmpfs rw,nosuid,mode=755 0 0
Perhaps the long line causes a parse issue?
(from redmine: issue id 5703, created on 2016-06-10, closed on 2016-09-23)
- Changesets:
- Revision 6a2b1e8b by Natanael Copa on 2016-09-14T10:40:09Z:
main/musl: fix for getmntent
ref #5703
- Revision ae8d3cf9 by Natanael Copa on 2016-09-22T14:39:52Z:
main/musl: fix for getmntent
fixes #5703