mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilbert Song (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-6061) Docker registry puller shows decode error "No response decoded".
Date Thu, 20 Oct 2016 23:05:58 GMT

     [ https://issues.apache.org/jira/browse/MESOS-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gilbert Song updated MESOS-6061:
--------------------------------
    Labels: docker  (was: docker gpu)

> Docker registry puller shows decode error "No response decoded".
> ----------------------------------------------------------------
>
>                 Key: MESOS-6061
>                 URL: https://issues.apache.org/jira/browse/MESOS-6061
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization, docker
>    Affects Versions: 1.0.0
>            Reporter: Sunzhe
>              Labels: docker
>
> The {{mesos-agent}} flags:
> {code}
>  GLOG_v=1 ./bin/mesos-agent.sh \
>               --master=zk://${MESOS_MASTER_IP}:2181/mesos  \
>               --ip=10.100.3.3  \
>               --work_dir=${MESOS_WORK_DIR} \
>               --isolation=cgroups/devices,gpu/nvidia,disk/du,docker/runtime,filesystem/linux
\
>               --enforce_container_disk_quota \
>               --containerizers=mesos \
>               --image_providers=docker \
>               --executor_environment_variables="{}"
> {code}
> And the {{mesos-execute}} flags:
> {code}
>  ./src/mesos-execute \
>            --master=${MESOS_MASTER_IP}:5050 \
>            --name=${INSTANCE_NAME} \
>            --docker_image=nvidia/cuda \
>            --framework_capabilities=GPU_RESOURCES \
>            --resources="cpus:1;mem:128;gpus:1"  \
>            --command="nvidia-smi"
> {code}
> But when {{./src/mesos-execute}}, the errors like below:
> {code}
> I0822 18:45:55.423899  8821 scheduler.cpp:172] Version: 1.0.1
> I0822 18:45:55.426172  8821 scheduler.cpp:461] New master detected at master@10.103.0.125:5050
> Subscribed with ID '34126b61-9d41-48dd-9c85-b61e4f9ad4c9-0001'
> Submitted task 'test' to agent 'b6c1587d-ab88-4734-9cb3-2cb916a73bf8-S1'
> Received status update TASK_FAILED for task 'test'
>   message: 'Failed to launch container: Failed to decode HTTP responses: No response
decoded
> HTTP/1.1 200 Connection established
> HTTP/1.1 401 Unauthorized
> Content-Type: application/json; charset=utf-8
> Docker-Distribution-Api-Version: registry/2.0
> Www-Authenticate: Bearer realm="https://auth.docker.io/token",service="registry.docker.io",scope="repository:nvidia/cuda:pull"
> Date: Mon, 22 Aug 2016 10:46:25 GMT
> Content-Length: 143
> Strict-Transport-Security: max-age=31536000
> {"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":[{"Type":"repository","Name":"nvidia/cuda","Action":"pull"}]}]}
> ; Container destroyed while provisioning images'
>   source: SOURCE_AGENT
>   reason: REASON_CONTAINER_LAUNCH_FAILED
> {code}
> The Docker works well, I can use {{docker pull}} IMAGE. And  if I used the agent flag
{{--docker_registry}} is a local path(i.e:{{/tmp/docker/images}}) in which Docker image archives(result
of {{docker save}}) are stored, the mesos-execute works well.



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

Mime
View raw message