Daniel J Walsh <dwa...@redhat.com> writes:
> We have to have a version by Tuesday for RHEL.
>
> On 03/16/2017 01:03 PM, Mrunal Patel wrote:
>
> If we can wait a bit, we should have a new 1.0.0.rc3 for runc soon.
I've tried to find a workaround for this issue on Atomic Host but it
seems that runC works only with rootfsPropagation = "rprivate",
otherwise it leaks mounts.
For a quick reproducer, it is enough to add "rootfsPropagation":"private" to
the default
configuration file generated by runC:
bash-4.3# rpm-ostree status
State: idle
Deployments:
● fedora-atomic:fedora-atomic/25/x86_64/docker-host
Version: 25.80 (2017-03-13 23:35:50)
Commit:
24d4499420ffb2cc49681020bbe5aa6780d780d2b811eab1f5ffea6446b5a4c5
OSName: fedora-atomic
# cd /var/lib/containers/atomic/docker.0/ (can really be any container)
# rm config.json
# runc spec config.json
# sed -i -e 's|\("linux": {\)|\1\n\t\t"rootfsPropagation": "private",|g'
config.json
# wc -l /proc/self/mountinfo
34 /proc/self/mountinfo
# /usr/bin/runc run test ; wc -l /proc/self/mountinfo
container_linux.go:247: starting container process caused
"process_linux.go:359: container init caused \"rootfs_linux.go:89: jailing
process inside rootfs caused \\\"pivot_root invalid argument\\\"\""
# wc -l /proc/self/mountinfo
71 /proc/self/mountinfo
Regards,
Giuseppe
