search

vmware / vic

vSphere Integrated Containers Engine is a container runtime for vSphere.
http://vmware.github.io/vic
Other
639 stars 173 forks source link

docker: Error: No such image: xxx-.eng.vmware.com/project1/vmware-platypus:2.0 when same image pulled with different version (tag) from different client machine #3238

Open mobla opened 7 years ago

mobla commented 7 years ago

VIC: vic-machine-windows.exe version v0.7.0-6964-7b2d9ac Harbor: 0.4.5-respin Client Machine - Windows and Linux (Photon)

Steps:

  1. Client machine1: (developer 1 tags an image as 1.0 and pushes to Harbor) docker tag vmware-platypus root@photon-lJUA39j42 [ ~/vic/vic ]# docker tag vmware/platypus:latest xxx.eng.vmware.com/project1/vmware-platypus:1.0 root@photon-lJUA39j42 [ ~/vic/vic ]# docker push xxx.eng.vmware.com/project1/vmware-platypus:1.0

  2. Client machine2: (developer 2 tags an image as 2.0 and pushes to Harbor) root@photon-lJUA39j42 [ ~/vic/vic ]# docker tag vmware/platypus:latest xxx.eng.vmware.com/project1/vmware-platypus:2.0 root@photon-lJUA39j42 [ ~/vic/vic ]# docker push xxx.eng.vmware.com/project1/vmware-platypus:2.0

  3. Both the developers are trying to run the image which is tagged with different version from same VCH and same Harbor at the same time.

  4. Succeeds for developer1 and fails for developer2

Success

$ docker -H w1-vim-cat-dhcp-231.eng.vmware.com:2376 --tlsverify --tlscacert="./VCH4ESX/ca.pem" --tlscert="./VCH4ESX/cert.pem" --tlskey="./VCH4ESX/key .pem" run -it --name wc-platypus1-1.0 xxx.eng.vmware.com/project1/vmware-platypus:1.0 Unable to find image 'xxx.eng.vmware.com/project1/vmware-platypus:1.0' locally Pulling from project1/vmware-platypus 6c123565ed5e: Pull complete a3ed95caeb02: Pull complete 3b2d6d0b88ad: Pull complete b94dc18057f9: Pull complete df08828a4137: Pull complete cb4173a26ed7: Pull complete cbe955929431: Pull complete Digest: sha256:a0cb878b9483af9c871b7b89c5fb30dacc786c8b718908e6360639e89450bfa0 Status: Downloaded newer image for project1/vmware-platypus:1.0 specifying your environment .. PRODUCT not set, defaulting to vRA VERSION not set, defaulting to 7 API_HOST not set, defaulting to localhost. starting your swaggerness

Failure

root@photon-lJUA39j42 [ ~/vic/vic ]# docker -H xxx.eng.vmware.com:2376 --tlsverify --tlscacert="./VCH4ESX/ca.pem" --tlscert="./VCH4ESX/cert.pem" --tlskey="./VCH4ESX/key.pem" run -it --name lc1-platypus1-2.0 xxx.eng.vmware.com/project1/vmware-platypus:2.0 Unable to find image 'xxx.eng.vmware.com/project1/vmware-platypus:2.0' locally Pulling from project1/vmware-platypus a3ed95caeb02: Pull complete 6c123565ed5e: Pull complete 3b2d6d0b88ad: Pull complete b94dc18057f9: Pull complete df08828a4137: Pull complete cb4173a26ed7: Pull complete cbe955929431: Pull complete Digest: sha256:e5f09486ece671875cb5dfaa33e52908a8b2911837ad0fa51162544b8092f955 Status: Downloaded newer image for project1/vmware-platypus:2.0 docker: Error: No such image: xxx.eng.vmware.com/project1/vmware-platypus:2.0.

Note: Looks like a race condition and subsequent run of image with version 2.0 for developer 2 works fine..

mdubya66 commented 7 years ago

@jzt please triage this one

mdubya66 commented 7 years ago

@mobla did you grab the logs?

mobla commented 7 years ago

with the latest build#6964, able to pull the container logs from https VCH [no BAD cert issue] which is cool..

Uploaded..

container-logs.tar.gz

https://w1-vim-cat-dhcp-231.eng.vmware.com:2378/

image

image

hickeng commented 7 years ago

@cgtexmex You cleaned up a lot of tagging issues for 0.8 - do you know if this was addressed?

I'm moving into backlog for verification.

cgtexmex commented 7 years ago

I believe this is less of a potential tagging issue and more a potential imagec issue -- I've not attempted to recreate yet...but pulling in @jzt as he's most familiar with the current state of imagec.