We have a private harbor registry that's insecure. We use docker client on a centos7 VM to push /pull images. We lost the docker client centos7 VM so have installed a new one. The issue I see is I log into the registry but when I do "docker image list" or "docker images" it doesn't show the images previously loaded. I'm not sure why?
[udmuser1@vtc-spk-auto10 ~]$ docker image list REPOSITORY TAG IMAGE ID CREATED SIZE
If I do a docker load -i image on the new linux VM then docker push I do see the image when doing "docker image list" on the registry.
[udmuser1@vtc-spk-auto10 ~]$ docker image list REPOSITORY TAG IMAGE ID CREATED SIZE harbor01.ims.net/library/f5-fluentd v1.4.2 b96d9e18a71c 9 months ago 495 MB
I'm unclear why I don't see the images that were loaded by the previous linux VM.
Thanks for any input on this.
John
CodePudding user response：
The container Registry is a place where you push/pull images to and from.
Your local Docker Client has of only the image that
- It pulled from a registry
- Build itself
The images you have are not synchronized with your registry, you need to explicitly push and pull those images.
CodePudding user response：
Your local Docker client would show you images that are part of its docker daemon in other words the images present on your client. You would need to setup synchronization if you want similar images on both the ends.