Using go client to access a Harbor registry #45360
dougchristie-DukeEnergy
started this conversation in
General
Replies: 1 comment 5 replies
-
The push and pull actions provide a streaming response; the 200 status code is returned when the request is received, but a streaming response containing the push/pull progress (and any errors occurring during push or pull) will follow. So when you receive the 200 status code, the push/pull is likely still in progress; also see the docker/cli code as an example https://github.com/docker/cli/blob/26a73575f1e3a0d1dc6ee6592db5926dcb907feb/cli/command/image/trust.go#L285 |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am have been seeing odd behavior when using the the go client to access a harbor registry. On smy windows machine There appears to be a race condition. If I slow things thing they appear to work.All calls to RegistryLogin, ImageTag and ImagePush all return no errors, but the image doesn't show up in the harbor registry. When I try this on an AWS workspace running ubuntu. Everything returns 200 when digging into the API call but nothing shows up in the registry. When I tried to pull an image from harbor I get now error and see a 200 digging into the api, but no image appears in the local registry when I run "docker image ls". Any idea why this happens.
Beta Was this translation helpful? Give feedback.
All reactions