You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Shuai Lin (JIRA)" <ji...@apache.org> on 2016/03/06 20:41:40 UTC
[jira] [Commented] (MESOS-4878) Task stuck in TASK_STAGING when
docker fetcher failed to fetch the image
[ https://issues.apache.org/jira/browse/MESOS-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182289#comment-15182289 ]
Shuai Lin commented on MESOS-4878:
----------------------------------
Seems it's because the containerizer is waiting for the preparation of the isolators, but the prepare is not started at all because the provision failed.
> Task stuck in TASK_STAGING when docker fetcher failed to fetch the image
> ------------------------------------------------------------------------
>
> Key: MESOS-4878
> URL: https://issues.apache.org/jira/browse/MESOS-4878
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.27.0, 0.27.1
> Reporter: Shuai Lin
> Assignee: Shuai Lin
>
> When a task is launched with the mesos containerizer and a docker image, if the docker fetcher failed to pull the image, no more task updates are sent to the scheduler.
> {code}
> I0306 17:28:57.627169 17647 registry_puller.cpp:194] Pulling image 'alpine:latest' from 'docker-manifest://registry-1.docker.io:443alpine?latest#https' to '/tmp/mesos-test/store/docker/staging/V2dqJv'
> E0306 17:29:00.749889 17651 slave.cpp:3773] Container '6b98026b-a58d-434c-9432-b517012edc35' for executor 'just-a-test' of framework a4ff93ba-2141-48e2-92a9-7354e4028282-0000 failed to start: Collect failed: Unexpected HTTP response '401 Unauthorized' when trying to get the manifest
> I0306 17:29:00.751579 17646 containerizer.cpp:1392] Destroying container '6b98026b-a58d-434c-9432-b517012edc35'
> I0306 17:29:00.752188 17646 containerizer.cpp:1395] Waiting for the isolators to complete preparing before destroying the container
> I0306 17:29:57.618649 17649 slave.cpp:4322] Terminating executor ''just-a-test' of framework a4ff93ba-2141-48e2-92a9-73
> {code}
> Scheduler logs:
> {code}
> sudo ./build/src/mesos-execute --docker_image=alpine:latest --containerizer=mesos --name=just-a-test --command="sleep 1000" --master=33.33.33.33:5050
> WARNING: Logging before InitGoogleLogging() is written to STDERR
> W0306 17:28:57.491081 17740 sched.cpp:1642]
> **************************************************
> Scheduler driver bound to loopback interface! Cannot communicate with remote master(s). You might want to set 'LIBPROCESS_IP' environment variable to use a routable IP address.
> **************************************************
> I0306 17:28:57.498028 17740 sched.cpp:222] Version: 0.29.0
> I0306 17:28:57.533071 17761 sched.cpp:326] New master detected at master@33.33.33.33:5050
> I0306 17:28:57.536761 17761 sched.cpp:336] No credentials provided. Attempting to register without authentication
> I0306 17:28:57.557729 17759 sched.cpp:703] Framework registered with a4ff93ba-2141-48e2-92a9-7354e4028282-0000
> Framework registered with a4ff93ba-2141-48e2-92a9-7354e4028282-0000
> task just-a-test submitted to slave a4ff93ba-2141-48e2-92a9-7354e4028282-S0
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)