Docker mysterious behavior in F22

[Dusty Mabe]

I think we really need to get a new Docker rpm in to F22 atomic before
we ship. One thing that I found this weekend is that /run/ is mounted
on top of /tmpfs inside running containers. This means that directories 
that are needed don't exist and cause some applications to fail on
startup. A great example of this is the fact that httpd won't start
because /run/httpd/ doesn't exist. 

> From what I can tell this functionality was added in Docker in [1] and
then reverted in [2], but for some reason the
docker-1.5.0-25.git5ebfacd.fc22.x86_64
we are using in Fedora 22 doesn't seem have the reverted commit even
though the reverted commit did make it in the 1.5.0 tag. You can tell we 
are trying to use 5ebfacd from [3], but I can't find that commit when
I clone the repo. The only way I can find anything regarding that commit 
is to download the source [4] specified by the spec file [5]. If I do
download the source and untar it the version is '1.5.0-dev':

[dustymabe@media wget]$ cat docker-5ebfacda4747fb0b2473841dff9b9b771b3bcb53/VERSION 
1.5.0-dev

I am also having random issues stopping/removing containers. Usually
I'll get a message like this: 

Cannot stop container jolly_mclean: active container for .... does not exist


[1] - https://github.com/docker/docker/commit/905795ece624675abe2ec2622b0bbafdb...
[2] - https://github.com/docker/docker/commit/8e967fe8028d8362fe3dfb293a8e07a95...
[3] - https://github.com/lsm5/docker.git
[4] -
https://github.com/lsm5/docker/archive/5ebfacda4747fb0b2473841dff9b9b771b...
[5] -
http://pkgs.fedoraproject.org/cgit/docker.git/tree/docker.spec?h=f22&...

[Matthew Miller]

On Sun, May 17, 2015 at 06:38:59PM -0400, Dusty Mabe wrote:
>  I think we really need to get a new Docker rpm in to F22 atomic
> before
>  we ship. One thing that I found this weekend is that /run/ is mounted 
Uh oh. Is there a bugzilla bug? Please propose it as a freezeexception.
(Can't be a blocker since atomic is nonblocking.)


-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Dusty Mabe]

On Sun, May 17, 2015 at 06:40:31PM -0400, Matthew Miller wrote:
>  On Sun, May 17, 2015 at 06:38:59PM -0400, Dusty Mabe wrote:
>  > I think we really need to get a new Docker rpm in to F22 atomic before
>  > we ship. One thing that I found this weekend is that /run/ is mounted
>  
>  Uh oh. Is there a bugzilla bug? Please propose it as a freezeexception.
>  (Can't be a blocker since atomic is nonblocking.) 
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?

[1] -
https://admin.fedoraproject.org/updates/FEDORA-2015-7836/docker-1.6.0-3.g...

[Matthew Miller]

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.

-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Dusty Mabe]

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 :(

[Daniel J Walsh]

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(a)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.