[jira] [Updated] (YARN-3159) DOCKER_IMAGE_PATTERN should support multilayered path of docker images
[
https://issues.apache.org/jira/browse/YARN-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leitao Guo updated YARN-3159:
-
Description:
Currently, DOCKER_IMAGE_PATTERN in DockerContainerExecutor can only match
docker images with the path like "sequenceiq/hadoop-docker:2.6.0", which has
only 1 "/" in the path.
{code:java}
public static final String DOCKER_IMAGE_PATTERN =
"^(([\\w\\.-]+)(:\\d+)*\\/)?[\\w\\.:-]+$";
{code}
In our cluster, the image name have multi layers, such as
"docker-registry:8080/cloud/hadoop-docker:2.6.0", which is workable when using
"docker pull IMAGE_NAME", but can not pass the check of image name in
saneDockerImage().
was:
Currently, DOCKER_IMAGE_PATTERN in DockerContainerExecutor can only match
docker images with the path like "sequenceiq/hadoop-docker:2.6.0", which has
only 1 "/" in the path.
{code}
public static final String DOCKER_IMAGE_PATTERN =
"^(([\\w\\.-]+)(:\\d+)*\\/)?[\\w\\.:-]+$";
{code}
In our cluster, the image name have multi layers, such as
"docker-registry.qiyi.virtual:8080/cloud/hadoop-docker:2.6.0", which is
workable when using "docker pull IMAGE_NAME", but can not pass the check of
image name in saneDockerImage().
> DOCKER_IMAGE_PATTERN should support multilayered path of docker images
> --
>
> Key: YARN-3159
> URL: https://issues.apache.org/jira/browse/YARN-3159
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
>Affects Versions: 2.6.0
>Reporter: Leitao Guo
>Assignee: Leitao Guo
>Priority: Major
> Labels: BB2015-05-TBR
> Attachments: YARN-3159.patch
>
>
> Currently, DOCKER_IMAGE_PATTERN in DockerContainerExecutor can only match
> docker images with the path like "sequenceiq/hadoop-docker:2.6.0", which has
> only 1 "/" in the path.
> {code:java}
> public static final String DOCKER_IMAGE_PATTERN =
> "^(([\\w\\.-]+)(:\\d+)*\\/)?[\\w\\.:-]+$";
> {code}
> In our cluster, the image name have multi layers, such as
> "docker-registry:8080/cloud/hadoop-docker:2.6.0", which is workable when
> using "docker pull IMAGE_NAME", but can not pass the check of image name in
> saneDockerImage().
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-3159) DOCKER_IMAGE_PATTERN should support multilayered path of docker images
[
https://issues.apache.org/jira/browse/YARN-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated YARN-3159:
---
Labels: BB2015-05-TBR (was: )
> DOCKER_IMAGE_PATTERN should support multilayered path of docker images
> --
>
> Key: YARN-3159
> URL: https://issues.apache.org/jira/browse/YARN-3159
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
>Affects Versions: 2.6.0
>Reporter: Leitao Guo
>Assignee: Leitao Guo
> Labels: BB2015-05-TBR
> Attachments: YARN-3159.patch
>
>
> Currently, DOCKER_IMAGE_PATTERN in DockerContainerExecutor can only match
> docker images with the path like "sequenceiq/hadoop-docker:2.6.0", which has
> only 1 "/" in the path.
> {code}
> public static final String DOCKER_IMAGE_PATTERN =
> "^(([\\w\\.-]+)(:\\d+)*\\/)?[\\w\\.:-]+$";
> {code}
> In our cluster, the image name have multi layers, such as
> "docker-registry.qiyi.virtual:8080/cloud/hadoop-docker:2.6.0", which is
> workable when using "docker pull IMAGE_NAME", but can not pass the check of
> image name in saneDockerImage().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-3159) DOCKER_IMAGE_PATTERN should support multilayered path of docker images
[
https://issues.apache.org/jira/browse/YARN-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Junping Du updated YARN-3159:
-
Assignee: Leitao Guo
> DOCKER_IMAGE_PATTERN should support multilayered path of docker images
> --
>
> Key: YARN-3159
> URL: https://issues.apache.org/jira/browse/YARN-3159
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
>Affects Versions: 2.6.0
>Reporter: Leitao Guo
>Assignee: Leitao Guo
> Attachments: YARN-3159.patch
>
>
> Currently, DOCKER_IMAGE_PATTERN in DockerContainerExecutor can only match
> docker images with the path like "sequenceiq/hadoop-docker:2.6.0", which has
> only 1 "/" in the path.
> {code}
> public static final String DOCKER_IMAGE_PATTERN =
> "^(([\\w\\.-]+)(:\\d+)*\\/)?[\\w\\.:-]+$";
> {code}
> In our cluster, the image name have multi layers, such as
> "docker-registry.qiyi.virtual:8080/cloud/hadoop-docker:2.6.0", which is
> workable when using "docker pull IMAGE_NAME", but can not pass the check of
> image name in saneDockerImage().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-3159) DOCKER_IMAGE_PATTERN should support multilayered path of docker images
[
https://issues.apache.org/jira/browse/YARN-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leitao Guo updated YARN-3159:
-
Attachment: YARN-3159.patch
> DOCKER_IMAGE_PATTERN should support multilayered path of docker images
> --
>
> Key: YARN-3159
> URL: https://issues.apache.org/jira/browse/YARN-3159
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
>Affects Versions: 2.6.0
>Reporter: Leitao Guo
> Attachments: YARN-3159.patch
>
>
> Currently, DOCKER_IMAGE_PATTERN in DockerContainerExecutor can only match
> docker images with the path like "sequenceiq/hadoop-docker:2.6.0", which has
> only 1 "/" in the path.
> {code}
> public static final String DOCKER_IMAGE_PATTERN =
> "^(([\\w\\.-]+)(:\\d+)*\\/)?[\\w\\.:-]+$";
> {code}
> In our cluster, the image name have multi layers, such as
> "docker-registry.qiyi.virtual:8080/cloud/hadoop-docker:2.6.0", which is
> workable when using "docker pull IMAGE_NAME", but can not pass the check of
> image name in saneDockerImage().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
