Skip to content
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

skopeo copy on docker.redpanda.com/redpandadata/connect:4.39 gives server side error 500 #24146

Open
oscni opened this issue Nov 15, 2024 · 0 comments
Labels
kind/bug Something isn't working

Comments

@oscni
Copy link

oscni commented Nov 15, 2024

Version & Environment

image redpandadata/connect:4.39

What went wrong?

skopeo copy on docker.redpanda.com/redpandadata/connect:4.39 gives server side error 500

What should have happened instead?

the image should have been copied

How to reproduce the issue?

This works as expected
skopeo copy docker://docker.redpanda.com/redpandadata/console:v2.7.2 docker://<PRIVATE_REGISTRY_PATH>

This gives an error
skopeo copy docker://docker.redpanda.com/redpandadata/connect:4.39 docker://<PRIVATE_REGISTRY_PATH>
FATA[0000] initializing source docker://docker.redpanda.com/redpandadata/connect:4.39: reading manifest 4.39 in docker.redpanda.com/redpandadata/connect: manifest unknown

Additional information

Don't know if this is a server side error or an error with skopeo but it would be valueable if you could look into it since redpandadata/console:v2.7.2 works but redpandadata/connect:4.39 does not work. This is the first time I've seen some error like this with skopeo, it has worked flawlessly on all other image copies we've ever done.

Thanks for creating redpanda! ✨

@oscni oscni added the kind/bug Something isn't working label Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant