docs icon indicating copy to clipboard operation
docs copied to clipboard

Setting tags not shown in the matrix example

Open andy5995 opened this issue 1 year ago • 5 comments

Is this a docs issue?

  • [X] My issue is about the documentation content or website

Type of issue

I can't find what I'm looking for

Description

In the example for the workflow using the matrix, setting the tags isn't shown.

Location

https://docs.docker.com/build/ci/github-actions/multi-platform/

Suggestion

Do the tags only need to be set in the meta section?

I'm trying this:

      -
        name: Docker meta
        id: meta
        uses: docker/metadata-action@v5
        with:
          images: ${{ env.REGISTRY_IMAGE }}
          tags: type=raw,value=dependencies-latest
-
        name: Build and push by digest
        id: build
        uses: docker/build-push-action@v5
        with:
          context: .
          file: ./dependencies.dockerfile
          platforms: ${{ matrix.platform }}
          labels: ${{ steps.meta.outputs.labels }}
          outputs: type=image,name=${{ env.REGISTRY_IMAGE }},push-by-digest=true,name-canonical=true,push=true
          tags: ${{ steps.meta.outputs.tags }}

The build finishes but the push fails:

#15 exporting config sha256:702f28b89befc2ea0d12a904c3a353ccf80cb4be0d9770769b5839c9b997e53b done
#15 exporting attestation manifest sha256:65234ecf26b23171773d75ec90596e1d200641ca2e5d54a9a6ec327a2e7be124 done
#15 exporting manifest list sha256:e8b40fa8f621c7cd0a07cdafaaa3572809007aca2bcd2afc42a46cbeecf61800 done
#15 ERROR: failed to push ***/linuxdeploy:dependencies-latest: can't push tagged ref docker.io/***/linuxdeploy:dependencies-latest by digest
------
 > exporting to image:
------
ERROR: failed to solve: failed to push ***/linuxdeploy:dependencies-latest: can't push tagged ref docker.io/***/linuxdeploy:dependencies-latest by digest
Error: buildx failed with: ERROR: failed to solve: failed to push ***/linuxdeploy:dependencies-latest: can't push tagged ref docker.io/***/linuxdeploy:dependencies-latest by digest

andy5995 avatar Feb 08 '24 02:02 andy5995

There hasn't been any activity on this issue for a long time. If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment. If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

docker-robot[bot] avatar May 08 '24 01:05 docker-robot[bot]

/remove-lifecycle stale

andy5995 avatar May 13 '24 23:05 andy5995

Here's a real-world workflow with the implementation. Note the "tags" section is only in the merge job.

andy5995 avatar May 14 '24 02:05 andy5995

Hi! I'm struggling with the same thing. If we add tags, we get an error:

Error: buildx failed with: ERROR: invalid tag "xxx/yyy:zzz": invalid reference format
buildx failed with: ERROR: failed to solve: failed to push xxx/yyy:zzz: can't push tagged ref docker.io/xxx/yyy:zzz by digest

If we remove the tags to push-by-digest it fails with:

Error: buildx failed with: ERROR: tag is needed when pushing to registry

uZer avatar Jul 20 '24 12:07 uZer

There hasn't been any activity on this issue for a long time. If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment. If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

docker-robot[bot] avatar Oct 18 '24 01:10 docker-robot[bot]

I think this is still an issue, following the example at https://docs.docker.com/build/ci/github-actions/multi-platform/#distribute-build-across-multiple-runners I still get the error reported at the top of the ticket

giordano avatar Nov 04 '24 13:11 giordano

/remove-lifecycle stale

andy5995 avatar Nov 04 '24 19:11 andy5995

Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked

docker-robot[bot] avatar Dec 04 '24 03:12 docker-robot[bot]