[
https://issues.apache.org/jira/browse/YARN-9244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775721#comment-16775721
]
Hudson commented on YARN-9244:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #16034 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/16034/])
YARN-9244. Document docker registry deployment with direct S3 driver.
(eyang: rev 05bce33d6e8b46c416a37b8d12fd84eb53474d6d)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/DockerContainers.md
> Document docker registry deployment with direct S3 driver
> ---------------------------------------------------------
>
> Key: YARN-9244
> URL: https://issues.apache.org/jira/browse/YARN-9244
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Eric Yang
> Assignee: Suma Shivaprasad
> Priority: Major
> Fix For: 3.3.0
>
> Attachments: YARN-9244.1.patch, YARN-9244.2.patch
>
>
> On Amazon, it would be possible to deploy docker registry in YARN using
> Docker's own S3 driver. The same micro-benchmark can also be applied to show
> the docker registry performance difference. The sample YARN service
> configuration looks like this:
> {code}
> {
> "name": "docker-registry",
> "version": "1.0",
> "kerberos_principal" : {
> "principal_name" : "hbase/[email protected]",
> "keytab" : "file:///etc/security/keytabs/hbase.service.keytab"
> },
> "components" :
> [
> {
> "name": "registry",
> "number_of_containers": 1,
> "artifact": {
> "id": "registry:latest",
> "type": "DOCKER"
> },
> "resource": {
> "cpus": 1,
> "memory": "256"
> },
> "run_privileged_container": true,
> "configuration": {
> "env": {
> "YARN_CONTAINER_RUNTIME_DOCKER_RUN_OVERRIDE_DISABLE":"true",
>
> "YARN_CONTAINER_RUNTIME_DOCKER_MOUNTS":"/path/to/config.yml:/etc/docker/registry/config.yml"
> },
> "properties": {
> "docker.network": "host"
> }
> }
> }
> ]
> }
> {code}
> Where /path/to/config.yml maps to a Docker S3 storage option config.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
