You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
e94834ac9522: Error pulling image (latest) from docker.io/registry, ApplyLayer exit status 1 stdout: stderr: unexpected EOF
FATA[0038] Error pulling image (latest) from docker.io/registry, ApplyLayer exit status 1 stdout: stderr: unexpected EOF
[centos@megacore01 ~]$ sudo docker create -p 5000:5000 -v /var/lib/local-registry:/srv/registry -e STANDALONE=false -e MIRROR_SOURCE=https://registry-1.docker.io -e MIRROR_SOURCE_INDEX=https://index.docker.io -e STORAGE_PATH=/srv/registry --name=local-registry registry
Unable to find image 'registry:latest' locally
latest: Pulling from docker.io/registry
i just think the notes need to be updated for the following instructions: https://docs.docker.com/registry/deploying/. this will deploy the docker registry 2.0 server, from what i understand. when i create that container, it seems the issue clears up. thus, i ended up using registry 2.0. (i hope that's correct?)
[centos@megacore01 ~]$ sudo docker create -p 5000:5000 \
> -v /var/lib/local-registry:/srv/registry \
> -e STANDALONE=false \
> -e MIRROR_SOURCE=https://registry-1.docker.io \
> -e MIRROR_SOURCE_INDEX=https://index.docker.io \
> -e STORAGE_PATH=/srv/registry \
> --name=local-registry registry:2
Unable to find image 'registry:2' locally
2: Pulling from docker.io/registry
d3a1f33e8a5a: Pull complete
c22013c84729: Pull complete
d74508fb6632: Pull complete
91e54dfb1179: Pull complete
5c3e6bcaa8b0: Pull complete
a5b8dc690ce7: Pull complete
e4aee72fc6c3: Pull complete
76b7062ceb9a: Pull complete
6228a99f9630: Pull complete
e024fb496e6b: Pull complete
1e847b14150e: Already exists
docker.io/registry:2: The image you are pulling has been verified. Important: image verification is a tech preview feature and should not be relied on to provide security.
Digest: sha256:0631faa22077d0494e9ac3d7e90bac3eeb6fd9f579cbf7b87dab1cda85c86f73
Status: Downloaded newer image for docker.io/registry:2
eebd0f819ac4352913e94a654d31a9bc2ea6575e2f7a17632a419430b2697274
[centos@megacore01 ~]$
Service seems to be running fine...
[centos@megacore01 ~]$ sudo systemctl status local-registry
local-registry.service - Local Docker Mirror registry cache
Loaded: loaded (/etc/systemd/system/local-registry.service; enabled)
Active: active (running) since Mon 2015-08-31 18:59:24 UTC; 18s ago
Main PID: 2751 (docker)
CGroup: /system.slice/local-registry.service
└─2751 /usr/bin/docker start -a local-registry
Aug 31 18:59:24 megacore01.jinkit.com.novalocal systemd[1]: Started Local Docker Mirror registry cache.
Aug 31 18:59:26 megacore01.jinkit.com.novalocal docker[2751]: time="2015-08-31T18:59:26Z" level=warning msg="No HTTP secret provided - generated random secret. This may cause problems with upl...
Aug 31 18:59:26 megacore01.jinkit.com.novalocal docker[2751]: time="2015-08-31T18:59:26Z" level=info msg="redis not configured" instance.id=ad99935f-6dcd-48b7-8a93-f962deba2318 version=v2.1.1
Aug 31 18:59:26 megacore01.jinkit.com.novalocal docker[2751]: time="2015-08-31T18:59:26Z" level=info msg="using inmemory blob descriptor cache" instance.id=ad99935f-6dcd-48b7-8a93-f...sion=v2.1.1
Aug 31 18:59:26 megacore01.jinkit.com.novalocal docker[2751]: time="2015-08-31T18:59:26Z" level=info msg="listening on [::]:5000" instance.id=ad99935f-6dcd-48b7-8a93-f962deba2318 version=v2.1.1
Aug 31 18:59:26 megacore01.jinkit.com.novalocal docker[2751]: time="2015-08-31T18:59:26Z" level=info msg="Starting upload purge in 16m0s" instance.id=ad99935f-6dcd-48b7-8a93-f962deb...sion=v2.1.1
Hint: Some lines were ellipsized, use -l to show in full.
The text was updated successfully, but these errors were encountered:
following the 'getting started instructions' at http://www.projectatomic.io/docs/gettingstarted/, i noticed an error when pulling the docker registry image.
i just think the notes need to be updated for the following instructions: https://docs.docker.com/registry/deploying/. this will deploy the docker registry 2.0 server, from what i understand. when i create that container, it seems the issue clears up. thus, i ended up using registry 2.0. (i hope that's correct?)
Service seems to be running fine...
The text was updated successfully, but these errors were encountered: