-
Notifications
You must be signed in to change notification settings - Fork 212
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
Error on publish to Harbor 2.0 (OCI-compliant) registry #1229
Comments
To double-check, does |
Just tested, it does not work either. |
@digger18 thank you for testing. As the errors are the same, I'm tempted to file this under the https://github.com/cnabio/cnab-to-oci repo as a result. Perhaps some maintainers of that repo might have some ideas. |
Oh wait, I did notice the invocation image name is: |
Thanks for reporting this, @digger18. (I don't have access to a Harbor instance right now, but I will try to reproduce it as well.) |
It works with the minimal bundle:
It led me to the understanding that I require
My slightly revised porter.yaml:
|
When adding
... but fails on other error for a specific image(s) which I believe is related to another issue I opened few days ago (#1224) My bundle.json file:
|
I changed |
@digger18 are you able to get the logs from the Harbor registry when the publish error(s) occur? Any leads there? |
Just wanted to add we're seeing this issue as well publishing inside an Openshift 3.11 environment to an insecure docker registry. |
@jeffersonbenson here's my output I just ran into this one today using version 0.28.1. I reverted back to 0.27.0 and the problem went away. Extracting bundle from archive /home/ocpadmin/my/my.tgz... |
Thanks for the extra information, all. If anyone is/was able to capture logs from the registry being published to, it'd be much appreciated. In the meantime, I'll keep attempting to reproduce the issue... looking into spinning up a Harbor registry now. |
I can confirm that downgrading to Porter v0.27.2 solves this issue:
However, I had to comment-out one image
|
I still hadn't successfully installed Harbor via the Helm chart approach (Any tips? I tried to start w/o TLS, but maybe it'd be best to invest in the time to set it up). All the components appear to deploy successfully and are running, but when I attempt to login I see:
However, I did experiment w/ the demo instance. I was able to successfully publish a few bundles and am as of yet unable to reproduce an error. However, latency is quite poor with the demo instance, as it appears to be shared with the rest of the public for testing purposes -- and, most importantly, I don't see a way to capture registry server logs if/when errors are encountered. Anyone with a Harbor instance of their own able to capture registry server logs when error(s) are encountered? |
@digger18 and @jeffersonbenson are you still having this problem? Harbor is darned important and OS well, you betcha |
@squillace We seem to have resolved the issue for now. I believe the issue was in how we had our registry configured. Thanks! |
any tips for others that might help before you go poof? If we haven't gotten there yet, a short tl;dr: might be great if you have a moment... ...it's usually a typo... |
I guess tl;dr since this is an API call to Docker, ensure that your service fabric isn't having any known networking issues, and possible push to another known good registry (even temporarily) just to make sure it's not an issue with your bundle itself. |
The latest version of harbor works as a charm https://github.com/goharbor/harbor/releases/tag/v2.1.0 . Just follow the installation steps and you should be good to go. |
Sounds like this is resolved. Let me know if it's still a problem and we can investigate. |
Describe the bug
Harbor 2.0 should be fully OCI-compliant (https://goharbor.io/blog/harbor-2.0/) registry, but Porter fails to publish CNAB bundles to it.
In the Harbor UI, there are specific instructions on how to push CNAB packages using
cnab-to-oci
which makes even a stronger case why Porter should be able to publish to it.The push command is:
cnab-to-oci push CNAB_PATH --target 172.31.33.xxx/library/REPOSITORY[:TAG] --auto-update-bundle
Expected behavior
CNAB bundle is successfully pushed to Harbor and available for deployment.
Porter Command and Output
Version
porter v0.27.2 (aee93e9)
The text was updated successfully, but these errors were encountered: