You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Joseph Wu (JIRA)" <ji...@apache.org> on 2016/08/10 17:32:21 UTC

[jira] [Commented] (MESOS-6019) How Mesos deal with docker services stop?

    [ https://issues.apache.org/jira/browse/MESOS-6019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15415635#comment-15415635 ] 

Joseph Wu commented on MESOS-6019:
----------------------------------

Docker is no longer supported on CentOS 6 (Docker dropped support, not Mesos).  If you still want to run docker containers on CentOS 6, I would recommend using the Mesos/unified containerizer: http://mesos.apache.org/documentation/latest/mesos-containerizer/

> How Mesos deal with docker services stop?
> -----------------------------------------
>
>                 Key: MESOS-6019
>                 URL: https://issues.apache.org/jira/browse/MESOS-6019
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization, docker, slave, volumes
>    Affects Versions: 0.26.0
>            Reporter: Enrique
>              Labels: mesosphere
>
> I'm using docker 1.7.1 and apache mesos 0.26.0 on CentOS6 with aufs. The firsts hours all work fine, but after some executions of docker cleanup procedure the docker service made crashed with error:
> ...
> time="2016-08-09T16:33:55.980463082-04:00" level=error msg="HTTP Error" err="No such image: vcregistry-hub.datys.cu:80/elasticsearch:2.3" statusCode=404 
> time="2016-08-09T16:33:56.229827046-04:00" level=info msg="POST /v1.19/images/create?fromImage=vcregistry-hub.datys.cu%3A80%2Felasticsearch%3A2.3" 
> time="2016-08-09T16:33:59.202167429-04:00" level=error msg="Error from V2 registry: Image 816f494ae83ef4c20d4b69db115158087f4ac4fc7ac9e8685750dae7c9a0426a already exists" 
> panic: runtime error: invalid memory address or nil pointer dereference
> [signal 0xb code=0x1 addr=0x20 pc=0x62db3a]
> goroutine 590 [running]:
> bufio.(*Writer).flush(0xc2084528c0, 0x0, 0x0)
>     /usr/lib/golang/src/bufio/bufio.go:530 +0xda
> bufio.(*Writer).Flush(0xc2084528c0, 0x0, 0x0)
>     /usr/lib/golang/src/bufio/bufio.go:519 +0x3a
> net/http.(*response).Flush(0xc2081912c0)
>     /usr/lib/golang/src/net/http/server.go:1047 +0x4c
> github.com/docker/docker/pkg/ioutils.(*WriteFlusher).Write(0xc208444480, 0xc20837bb80, 0xbd, 0x142, 0xbd, 0x0, 0x0)
> ...
> docker cleanup procedure
> stop docker and mesos-slave service
> rm -rf /var/lib/docker
> start docker and mesos-slave service
> The docker issue on github: https://github.com/docker/docker/issues/25551
> How Mesos recover from docker stop service?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)