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

Hudson commented on YARN-8783:
------------------------------

FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #16072 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/16072/])
YARN-8783. Improve the documentation for the docker.trusted.registries 
(sumasai: rev a106d2dc9d9af996bcb8e3c1b80c03b22dbc4251)
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/DockerContainers.md


> Improve the documentation for the docker.trusted.registries configuration
> -------------------------------------------------------------------------
>
>                 Key: YARN-8783
>                 URL: https://issues.apache.org/jira/browse/YARN-8783
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>    Affects Versions: 3.1.1
>            Reporter: Simon Prewo
>            Assignee: Eric Yang
>            Priority: Major
>              Labels: Docker, container-executor, docker
>             Fix For: 3.3.0
>
>         Attachments: YARN-8783.001.patch, YARN-8783.002.patch
>
>
> I am deploying the default yarn distributed shell example:
> {code:java}
> yarn jar hadoop-yarn-applications-distributedshell.jar -shell_env 
> YARN_CONTAINER_RUNTIME_TYPE=docker -shell_env 
> YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=centos -shell_command "sleep 90" -jar 
> hadoop-yarn-applications-distributedshell.jar -num_containers 1{code}
> Having a *single trusted registry configured like this works*:
> {code:java}
> docker.trusted.registries=centos{code}
> But havingĀ *a list of trusted registries configured fails* ("Shell error 
> output: image: centos is not trusted."):
> {code:java}
> docker.trusted.registries=centos,ubuntu{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to