Docker mysterious behavior in F22

Daniel J Walsh dwalsh at redhat.com
Mon May 18 12:37:08 UTC 2015



On 05/17/2015 08:23 PM, Dusty Mabe wrote:
> On Sun, May 17, 2015 at 07:43:38PM -0400, Matthew Miller wrote:
>> On Sun, May 17, 2015 at 07:18:05PM -0400, Dusty Mabe wrote:
>>> So. Some new information. Looks like there is a new docker in testing [1] 
>>> that does not have this problem. We need to add karma to this. Please test 
>>> and upvote/downvote!
>>> Matt should I still open a bug for this issue so it can be proposed as
>>> a freezeexception?
>> Yes -- otherwise it won't get included in the composes and will be
>> shipped as a zero-day update.
> https://bugzilla.redhat.com/show_bug.cgi?id=1222352
>
> It would suck if we shipped F22 atomic with a Docker that can't run
> apache :( 
> _______________________________________________
> cloud mailing list
> cloud at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/cloud
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
We have been shipping a /run on tmpfs docker for some time.  If the
docker image has /run/httpd
the docker command is supposed to copy the contents in the images /run
onto the tmpfs.  If this is
not happening it is a bug.  Of course httpd should be able to handle the
fact that /run/httpd does not exists
and create it. 


More information about the cloud mailing list