-
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
porter archive --> Error preparing artifacts: unsupported MediaType: "application/vnd.docker.distribution.manifest.v1+prettyjws" #1224
Comments
|
Thanks for the issue @digger18 . Alas, last we checked, Quay isn't a CNAB-compatible registry. This unfortunately means that these errors are currently expected. An issue around improving Porter's UX in this area is currently being tracked in #822. |
I am not trying to push to quay.io, just pull images from it. |
May I suggest taking a look at this PR for go-containerregistry: google/go-containerregistry#408 which should fix this issue, I assume that Porter uses go-containerregistry under the hood? |
Ah, I see. Thank you for the PR link. Porter is currently on the following commit of go-containerregistry from Oct 15, '19: google/go-containerregistry@71da34e ... which appears to be more recent than the commit in google/go-containerregistry#408, so I'm assuming we have that particular change as well. I'm also intrigued by the error from |
Another strange error while publishing to a local docker registry v2:
|
I've created a repro bundle in https://github.com/vdice/porter-bundles/blob/master/wip/publish-repro/porter.yaml. Indeed, I see the same (and other) errors from some of the images attempted to be copied. For testing, I've been publishing against a local Docker registry (via The errors seen in the registry logs either seem to be:
I'm surprised that these errors are encountered on well-known/supported images. I'm not sure if there's a setting we can flip in either go-containerregistry or cnab-to-oci to forgo these errors -- if even advisable. (Oh, by the way, I built/used a local Porter binary with the go-containerregistry dep bumped to their latest v0.1.2 release; Porter is already on the latest cnab-to-oci release). Any experience in this area @radu-matei ? |
Any update on this? |
Unfortunately, no updates here. These are errors coming straight from the referenced libraries (go-containerregistry and cnab-to-oci), both of which were tested with their latest variants. We would need to spend some time with both to debug the issues and/or inquire with the upstream dependencies. |
Should I create the issue there? |
@digger18 I had some spare cycles this morning to revisit. When reviewing my repro bundle (based on the bundle provided in this issue), the two main errors produced by the stock docker registry (v2) are/were:
My hunch was that the first class of errors was due to problematic image tags, so I looked up each affected image and bumped to a more recent tag. These images now succeeded in pushing/copying when publishing the bundle. The second class only occurred for one image in the repro bundle: (One additional note on multi-arch tags: publishing didn't have an issue with tags with Linux-only multi-arch images, such as the configmap-reload v0.4.0 tag.) For an updated porter.yaml of this repro bundle, see: https://github.com/vdice/porter-bundles/blob/ref/publish-repro/wip/publish-repro/porter.yaml Can you try publishing this updated bundle (or your variant with similar bumped/changed tags) and see if you have better luck publishing? Thank you! |
@vdice Assuming that your thoughts on multi-os/arch are correct, is this a bug with porter that needs fixing? Perhaps something that we need to document? |
I revisited the same publish-repro bundle. While I still encounter similar errors when publishing to a local registry (using the same Since it works for one but not the other, I'm not thinking it is a bug with Porter. As for documenting, it still seems like we'd need to pin down the real issue first, unfortunately. |
I am making a new issue label, |
Describe the bug
Unable to bundle several images from quay.io, probably related to google/go-containerregistry#377
Getting error
Error preparing artifacts: unsupported MediaType: "application/vnd.docker.distribution.manifest.v1+prettyjws"
duringporter archive
.Porter Command and Output
My porter.yaml
Version
porter v0.27.2 (aee93e9)
The text was updated successfully, but these errors were encountered: