Manifest does not work lately

rustdesk · March 28, 2024, 10:18am

My manifest job in CI does not work lately.

I also tried docker command line manually, the same problem?

Does it mean dockerhub has stop to support manifest for free user.

rustdesk · April 2, 2024, 6:09am

Got the fix. It is propbaly docker-buildx upgraded implictly.

github.com/Noelware/docker-manifest-action

Manifest creation fails

opened 09:05AM - 25 Jan 23 UTC

closed 08:01PM - 27 Jan 23 UTC

r4sas

Hello. Thank you for your workaround with docker containers merging with manife…st. Lately it start fail when trying to create manifest. Example output can be found here: https://github.com/PurpleI2P/i2pd/actions/runs/4001302421/jobs/6867928655 ``` /usr/bin/docker manifest create --amend purplei2p/i2pd:latest purplei2p/i2pd:latest-amd64 purplei2p/i2pd:latest-i386 purplei2p/i2pd:latest-arm64 purplei2p/i2pd:latest-armv7 docker.io/purplei2p/i2pd:latest-amd64 is a manifest list ``` How can we fix this?

github.com/docker/build-push-action

Docker push creates multiple images on GCR, some with creation timestamp equal to 0 epoch

opened 07:09PM - 23 Jan 23 UTC

closed 06:07PM - 30 Jan 23 UTC

pantelis-karamolegkos

### Troubleshooting Before submitting a bug report please read the [Troublesh…ooting doc](https://github.com/docker/build-push-action/blob/master/TROUBLESHOOTING.md). ### Behaviour #### Steps to reproduce this issue 1. Build an image and push to local registry ``` - name: build and push to local registry uses: docker/build-push-action@v3.3.0 with: context: ${{ inputs.context }} file: ${{ inputs.context }}/${{ inputs.dockerfile }} no-cache: ${{ inputs.no_cache }} build-args: ${{ inputs.build_args }} push: true tags: ${{ env.LOCAL_IMAGE }} cache-to: type=inline provenance: false ``` 2. Use `buildx` to copy the image to a GCR registry ``` - name: copy tagged image to sre gcr if: inputs.image_build == true shell: bash run: | docker buildx imagetools create \ --tag "${{ steps.set-images.outputs.base }}:${{ inputs.image_tag }}" \ ${{ env.LOCAL_IMAGE }} ``` #### Expected behaviour > Tell us what should happen One image should be created #### Actual behaviour Instead, I am seeing this weird behaviour > Tell us what happens instead ![Screenshot 2023-01-23 at 9 05 51 PM](https://user-images.githubusercontent.com/50835081/214127447-b01418b1-d4f7-4762-9f2f-47ab1102d169.png) ### Configuration My workflow uses the local registry service ``` services: registry: image: registry:2 ports: - 5000:5000 ``` FWIW * Repository URL (if public): * Build URL (if public): ```yml # paste your YAML workflow file here and remove sensitive data ``` ### Logs > Download the [log file of your build](https://docs.github.com/en/actions/managing-workflow-runs/using-workflow-run-logs#downloading-logs) and [attach it](https://docs.github.com/en/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests) to this issue.

Topic		Replies	Views
Manifest not found Docker Desktop macos	6	24720	June 3, 2020
First time Docker Cloud user - Manifest not found? Docker Hub ci_cd	0	2093	March 1, 2018
Docker:dind manifest broken Docker Hub docker	1	30	December 14, 2024
Can't find docker manifest since update Docker Desktop dockerhub , docker , build	3	1554	May 10, 2023
Can't pull from DockerHub Docker Hub	4	10748	October 9, 2021

Manifest does not work lately

Related topics