Re: [atomic-devel] Status of containerizing docker and https://github.com/projectatomic/atomic-system-containers

[Daniel J Walsh <dwalsh redhat com>]

We have updated the runc package for RHEL

https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=12783794



On 03/16/2017 09:16 AM, Daniel J Walsh wrote:
>
> On 03/16/2017 08:06 AM, Giuseppe Scrivano wrote:
>> Colin Walters <walters verbum org> writes:
>>
>>> # atomic host 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
>>> # atomic install --system gscrivano/docker-fedora
>>> # systemctl start docker-fedora
>>> ...
>>> Mar 15 16:02:02 localhost.localdomain runc[4867]: 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\\\"\""
>>> ```
>> it seems like a bug in runC.  The same version of runC works on Rawhide
>> though, I think the difference is that /var is a bind mount on Atomic
>> Host.  The issue is fixed in runC upstream, looking at the git log, by
>> this:
>>
>> commit 6c147f86496c02f1c28315d1e86ea8be08049ceb
>> Author: Vivek Goyal <vgoyal redhat com>
>> Date:   Tue Oct 25 11:15:11 2016 -0400
>>
>>     Make parent mount private before bind mounting rootfs
>>     
>>     This reverts part of the commit eb0a144b5e383
>>
>> Could we get an updated runC package?  There is also another fix
>> that would be nice to have for the Flannel system container:
>>
>> https://github.com/projectatomic/atomic-system-containers/pull/24
>>
>> Regards,
>> Giuseppe
> What OS Needs updating?
>