With docker_manifests enabled, how not to push docker image

[Loyalsoldier]

With the following docker and docker_manifests config, docker images username/myrepo:latest-386, username/myrepo:latest-amd64 and username/myrepo:latest-arm64 will also be pushed to DockerHub.

I wonder how to only push image username/myrepo:latest?

dockers:
  - build_flag_templates:
      - --platform=linux/386
      - --pull
    use_buildx: true
    dockerfile: ./Dockerfile
    image_templates:
      - "username/myrepo:latest-386"

  - build_flag_templates:
      - --platform=linux/amd64
      - --pull
    use_buildx: true
    dockerfile: ./Dockerfile
    image_templates:
      - "username/myrepo:latest-amd64"

  - build_flag_templates:
      - --platform=linux/arm64
      - --pull
    use_buildx: true
    dockerfile: ./Dockerfile
    image_templates:
      - "username/myrepo:latest-arm64"

docker_manifests:
  - name_template: "username/myrepo:latest"
    image_templates:
      - "username/myrepo:latest-386"
      - "username/myrepo:latest-amd64"
      - "username/myrepo:latest-arm64"

[caarlos0]

afaik its not possible because the manifest tool needs the images to be pushed... you can try to create a manifest locally with unpushed images and it will fail as well...

[Loyalsoldier]

BTW, I don't know why this Docker multi-platform build failed(without docker_manifests):

dockers:
  - use: buildx
    dockerfile: ./Dockerfile
    build_flag_templates:
      - --pull
      - --output=registry
      - --platform=linux/386,linux/amd64,linux/arm64
    image_templates:
      - "username/myrepo:latest"
      - "username/myrepo:{{ .Tag }}"
      - "username/myrepo:v{{ .Major }}"
      - "username/myrepo:v{{ .Major }}.{{ .Minor }}"
    ids:
      - mybuild

Any suggestion? Thanks!

[Loyalsoldier]

AFAIK, run the following command will build and push multi-platform images to DockerHub without redundant images username/myrepo:latest-386, username/myrepo:latest-amd64 and username/myrepo:latest-arm64:

docker buildx build --platform linux/386,linux/amd64,linux/arm64 \
                    --output=registry \
                    --tag "username/myrepo:latest" \
                    --file Dockerfile .

It seems Goreleaser doesn't support this.

[caarlos0]

that's assuming all images are built from the same dockerfile, which is something goreleaser can't assume...

goreleaser first builds the images, pushes them, and then uses docker manifest create to create the manifest and then push it.

[Loyalsoldier]

Why not extend it? I think the following configs are intuitive:

dockers:
  - use: buildx
    dockerfile: ./Dockerfile
    build_flag_templates:
      - --pull
      - --output=registry
      - --platform=linux/386,linux/amd64,linux/arm64
    image_templates:
      - "username/myrepo:latest"
      - "username/myrepo:{{ .Tag }}"
      - "username/myrepo:v{{ .Major }}"
      - "username/myrepo:v{{ .Major }}.{{ .Minor }}"
    ids:
      - mybuild

or

dockers:
  - use: buildx
    dockerfile: ./Dockerfile
    buildx_flag:
      - --pull
      - --output=registry
      - --platform=linux/386,linux/amd64,linux/arm64
      - --tag=latest
      - --tag={{ .Tag }}
      - --tag=v{{ .Major }}
      - --tag=v{{ .Major }}.{{ .Minor }}
    ids:
      - mybuild
    owner: username
    repo: myrepo

[caarlos0]

mainly because the way goreleaser works... build and publishing are separated steps, and buildx dost not seem to not support that yet...

e.g., I can't

 docker buildx build --platform linux/386,linux/amd64,linux/arm64 \
                      --load \
                      --tag "caarlos0/foobar" \
                      --file Dockerfile .

and later just docker push caarlos0/foobar.

[trallnag]

This article showcases how to use GoReleaser without using it to push images.