-
Notifications
You must be signed in to change notification settings - Fork 2
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
Does modctl support pushing to a registry that does not yet support the Image Spec v1.1? #50
Comments
The model specification is dependent on the OCI image specification v1.1. This potentially introduces incompatibility with older registries, although this has not been verified. But based on the provided logs, the issue appears to be a connection error rather than a compatibility problem. Could you retry the operation or provide the Jfrog logs? |
Sorry, I missed your reply earlier! Thanks so much for looking into my issue. ❤️ From the error messages, it does seem most likely to be a network issue. Regarding JFrog logs, I have no access to them, as JFrog is maintained by another team within our company. However, our company will soon be upgrading JFrog to a version that supports image spec v1.1. I’ll test again after the upgrade and let you know the result. Thanks again! |
@chlins It does not seem that even https://github.com/distribution/distribution/releases/tag/v3.0.0-rc.2 supports. I am trying to push image to local registry and have same issue.
What is the target registry that |
The distribution should work with the |
|
|
I was testing modctl within our company environment, but encountered a failure during the config push step:
Background: We are using a JFrog version that currently does not support OCI Image Spec v1.1. Could this be causing the issue?
The text was updated successfully, but these errors were encountered: