New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot pull images pushed from oci reference on Fly.io #1881
Comments
Thanks for reaching out. The above is really not enough to go on. At the very least, please collect the precise and full command line, and a log of |
Sure thing!
|
Thanks! That looks normal enough so far, but the |
|
I tried it on the one I created from the docker archive (working) and got
|
That looks just fine. If some the consumer doesn’t find the image, I think that needs to be debugged in / within that consumer. One thing of note to possibly examine in more detail is that the |
The only difference I noticed was that I'll try Edit: And thanks for your help! I wouldn't have discovered the manifest difference. |
Okay, I got a reply from them. They were able to confirm that their issue is with oci manifests, and they asked me to work around it by using docker manifests (v2s2, which I assume I can convert to with the format parameter). |
Sorry in case this is a vendor specific issue.
I have an image in oci directory format that I'm pushing to Fly.io's private repo. The copy works with no errors, however launching an instance fails with an error like
Could not find image "registry.fly.io/myimage:mytag"
.Copying from the oci directory to anything else (docker-daemon, docker, docker-archive) and then from that (docker-daemon, docker, docker-archive) to fly works fine.
So if I understand it correctly, either Skopeo is doing something different when it copies from an oci directory vs docker-daemon/docker, or else the image is broken and docker-daemon/docker is fixing up the pushed image when it receives it.Since copying to docker archive first works, Skopeo must be doing something different when it copies from an oci dir vs when it copies from a docker archive.I did look through the code and I couldn't see any big branches that would make it different in the main copy code. Do you have any idea what could be going on?
I cloned
skopeo
today to try it, but also had issues with 1.10.0 (and I was using those to try to reproduce this issue in go code callingCopy
directly).The text was updated successfully, but these errors were encountered: