Replies: 6 comments 2 replies
-
I think regarding the images being listed as untagged, one possible reason could be that the tags output from the docker/metadata-action step is not correctly capturing or passing the tags for the new images. Make sure that the tags output in the meta step captures all the relevant tags for both images (linux/amd64 and linux/arm64). You can check the output of the meta step by adding a debug log statement like run: echo "${{ steps.meta.outputs.tags }}". Verify if it includes the expected tags for both images. As for the missing manifest data, it could be related to the provenance: false parameter you have set in the docker/build-push-action step. The provenance option controls whether to generate and include image provenance information in the manifest. Try setting provenance: true to include the manifest data when pushing the Docker images. This may resolve the issue with missing manifest data.
|
Beta Was this translation helpful? Give feedback.
-
Hi @ArdeshirV, thank you for the tip, it may also be that generally the pinned images are always untagged as well? Or rather not? I tried your tip with the |
Beta Was this translation helpful? Give feedback.
-
@gowizzard you actually need to disable the |
Beta Was this translation helpful? Give feedback.
-
@daltonv right, that's why I set it up that way in my first example, just wanted to show what happens since @ArdeshirV said I should enable this. |
Beta Was this translation helpful? Give feedback.
-
Here is the official doc for merging multi-platform images into one with GitHub action: https://docs.docker.com/build/ci/github-actions/multi-platform/ I think the untagged images have no business with multi-platform. |
Beta Was this translation helpful? Give feedback.
-
Observed same behavior. There are always untagged images created when publishing new package version. Removing untagged breaks package download:
When those untagged versions exist I have no problem pulling image from ghcr. I guess those need to stay. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Hello everyone, I have a question. I've been working with GitHub packages for the last few days. I have created an action which creates an image for
linux/arm64
for a project withbuildx
. This also tags all images correctly and allows to display the manifest data. Now I have modified the action to create two images forlinux/amd64
andlinux/arm64
.The images can also be accessed via the packages and the two images are also displayed under OS, but unfortunately the images are also found under untagged images, although they seem to be assigned. Unfortunately, the manifest data is also missing from the image where the two OS versions are displayed. Does anyone know what this could be?
Here is my action:
Many greetings
Jonas
Beta Was this translation helpful? Give feedback.
All reactions