Some confusion about abnormal “/proc/mounts"

[wenhaochen]

Hi all ！

I doubt I got an issue similar with https://github.com/cloudfoundry/warden/issues/76. I pushed an app , but failed.And I found the abnormal "/proc/mounts" as follows which resulted in creating container failed.

# cat /proc/mounts
....
cgroup /sys/fs/cgroup/freezer cgroup rw,relatime,freezer 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,relatime,blkio 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,relatime,perf_event 0 0
cgroup /sys/fs/cgroup/hugetlb cgroup rw,relatime,hugetlb 0 0
/dev/loop0 /tmp ext4 rw,relatime,data=ordered 0 0
none /tmp/warden/cgroup tmpfs rw,relatime 0 0
none /tmp/warden/cgroup tmpfs rw,relatime 0 0
none /tmp/warden/cgroup tmpfs rw,relatime 0 0
none /tmp/warden/cgroup tmpfs rw,relatime 0 0
none /tmp/warden/cgroup/cpu cgroup rw,relatime,cpu 0 0
none /tmp/warden/cgroup/cpuacct cgroup rw,relatime,cpuacct 0 0
none /tmp/warden/cgroup/devices cgroup rw,relatime,devices 0 0
none /tmp/warden/cgroup/memory cgroup rw,relatime,memory 0 0

Howerve ,I still have no idea why the mount record none /tmp/warden/cgroup tmpfs rw,relatime 0 0happened four times，since https://github.com/cloudfoundry/warden/blob/master/warden/root/linux/setup.sh has checked the ”/proc/mounts“ .

Thanks

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/80712612.

[glyn]

This sounds more like a question than a bug report. If so, please close the bug and ask the question on vcap-dev as you are more likely to get an answer there and the answer may be of interest to others who are not tracking this issue.