Skip to content

build(deps): bump docker/build-push-action from 6.10.0 to 6.11.0 (#724) #2102

build(deps): bump docker/build-push-action from 6.10.0 to 6.11.0 (#724)

build(deps): bump docker/build-push-action from 6.10.0 to 6.11.0 (#724) #2102

Triggered via push January 14, 2025 09:00
Status Failure
Total duration 4m 50s
Artifacts 36

buildx.yml

on: push
Matrix: buildx
Fit to window
Zoom out
Zoom in

Annotations

33 errors and 88 warnings
buildx (3.2/20, 3.2-20 3.2-iron 3.2, linux/amd64,linux/arm64,linux/arm/v7)
Process completed with exit code 1.
buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)
Process completed with exit code 1.
buildx (3.4/18/alpine, 3.4-alpine-18 3.4-alpine-hydrogen, linux/amd64,linux/arm64,linux/ppc64le,l...
buildx failed with: ERROR: failed to solve: ruby:3.4-rc-alpine: failed to resolve source metadata for docker.io/library/ruby:3.4-rc-alpine: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/ruby/manifests/sha256:9b4bceb71d1a1fea2c9df2260a2c53a8bd1c3142cd0df37911232d114afc0484: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (3.2/18, 3.2-18 3.2-hydrogen, linux/amd64,linux/arm64,linux/arm/v7)
Process completed with exit code 1.
buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)
buildx failed with: ERROR: failed to solve: ruby:3.3-slim: failed to resolve source metadata for docker.io/library/ruby:3.3-slim: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/ruby/manifests/sha256:8f0c74a7c0a845bdeab335953988c15275a119ae08fb1e6ffbcb46d72d5ffd49: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (3.1/18, 3.1-18 3.1-hydrogen, linux/amd64,linux/arm64,linux/arm/v7)
Process completed with exit code 1.
buildx (3.4/18, 3.4-18 3.4-hydrogen, linux/amd64,linux/arm64,linux/arm/v7)
Process completed with exit code 1.
buildx (3.4/18, 3.4-18 3.4-hydrogen, linux/amd64,linux/arm64,linux/arm/v7)
buildx failed with: ERROR: failed to solve: ruby:3.4-rc: failed to resolve source metadata for docker.io/library/ruby:3.4-rc: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/ruby/manifests/sha256:3544ba11dd19f1cbf358fda8677037e2678d88d7a8e6b5ca11d3462db278fcd2: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (3.4/18/slim, 3.4-slim-18 3.4-slim-hydrogen, linux/amd64,linux/arm64,linux/arm/v7)
buildx failed with: ERROR: failed to solve: ruby:3.4-rc-slim: failed to resolve source metadata for docker.io/library/ruby:3.4-rc-slim: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/ruby/manifests/sha256:3ca454ec9d6265b79f5551e929e76b59d812a0d42751eebff5fde9be5619b46c: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (3.4/20/alpine, 3.4-alpine-20 3.4-alpine-iron 3.4-alpine, linux/amd64,linux/arm64,linux/pp...
buildx failed with: ERROR: failed to solve: ruby:3.4-rc-alpine: failed to resolve source metadata for docker.io/library/ruby:3.4-rc-alpine: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/ruby/manifests/sha256:9b4bceb71d1a1fea2c9df2260a2c53a8bd1c3142cd0df37911232d114afc0484: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)
buildx failed with: ERROR: failed to solve: ruby:3.4-rc: failed to resolve source metadata for docker.io/library/ruby:3.4-rc: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/ruby/manifests/sha256:3544ba11dd19f1cbf358fda8677037e2678d88d7a8e6b5ca11d3462db278fcd2: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)
Process completed with exit code 1.
buildx (3.4/22/alpine, 3.4-alpine-22 3.4-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...
buildx failed with: ERROR: failed to solve: ruby:3.4-rc-alpine: failed to resolve source metadata for docker.io/library/ruby:3.4-rc-alpine: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/ruby/manifests/sha256:9b4bceb71d1a1fea2c9df2260a2c53a8bd1c3142cd0df37911232d114afc0484: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (3.4/22/slim, 3.4-slim-22 3.4-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)
buildx failed with: ERROR: failed to solve: ruby:3.4-rc-slim: failed to resolve source metadata for docker.io/library/ruby:3.4-rc-slim: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/ruby/manifests/sha256:3ca454ec9d6265b79f5551e929e76b59d812a0d42751eebff5fde9be5619b46c: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (3.4/20, 3.4-20 3.4-iron 3.4, linux/amd64,linux/arm64,linux/arm/v7)
Process completed with exit code 1.
buildx (3.4/20, 3.4-20 3.4-iron 3.4, linux/amd64,linux/arm64,linux/arm/v7)
buildx failed with: ERROR: failed to solve: ruby:3.4-rc: failed to resolve source metadata for docker.io/library/ruby:3.4-rc: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/ruby/manifests/sha256:3544ba11dd19f1cbf358fda8677037e2678d88d7a8e6b5ca11d3462db278fcd2: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (3.4/20/slim, 3.4-slim-20 3.4-slim-iron 3.4-slim, linux/amd64,linux/arm64,linux/arm/v7)
buildx failed with: ERROR: failed to solve: ruby:3.4-rc-slim: failed to resolve source metadata for docker.io/library/ruby:3.4-rc-slim: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/ruby/manifests/sha256:3ca454ec9d6265b79f5551e929e76b59d812a0d42751eebff5fde9be5619b46c: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)
Process completed with exit code 1.
Legacy key/value format with whitespace separator should not be used: 3.2/18/alpine/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.2/18/alpine/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.1/18/alpine/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.1/18/alpine/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.2/22/alpine/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.2/22/alpine/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.1/22/alpine/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.1/22/alpine/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.1/20/alpine/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.1/20/alpine/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.2/20/alpine/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.2/20/alpine/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.3/18/alpine/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.3/18/alpine/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
buildx (3.1/20, 3.1-20 3.1-iron 3.1, linux/amd64,linux/arm64,linux/arm/v7)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: 3.1/20/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.1/20/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.2/20/slim/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.2/20/slim/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: 3.1/22/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.1/22/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: 3.1/22/slim/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.1/22/slim/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: 3.2/22/slim/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.2/22/slim/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.1/20/slim/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.1/20/slim/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
buildx (3.2/20, 3.2-20 3.2-iron 3.2, linux/amd64,linux/arm64,linux/arm/v7)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: 3.2/20/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.2/20/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.3/20/alpine/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.3/20/alpine/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: 3.2/22/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.2/22/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
buildx (3.2/18, 3.2-18 3.2-hydrogen, linux/amd64,linux/arm64,linux/arm/v7)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: 3.2/18/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.2/18/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (3.1/18, 3.1-18 3.1-hydrogen, linux/amd64,linux/arm64,linux/arm/v7)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: 3.1/18/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.1/18/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
buildx (3.4/18, 3.4-18 3.4-hydrogen, linux/amd64,linux/arm64,linux/arm/v7)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: 3.2/18/slim/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.2/18/slim/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.3/22/alpine/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.3/22/alpine/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: 3.1/18/slim/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.1/18/slim/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
buildx (3.4/22/slim, 3.4-slim-22 3.4-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (3.4/20, 3.4-20 3.4-iron 3.4, linux/amd64,linux/arm64,linux/arm/v7)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: 3.3/20/slim/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.3/20/slim/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
buildx (3.3/20, 3.3-20 3.3-iron 3.3 3 latest, linux/amd64,linux/arm64,linux/arm/v7)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: 3.3/20/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.3/20/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: 3.3/22/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.3/22/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
buildx (3.3/18, 3.3-18 3.3-hydrogen, linux/amd64,linux/arm64,linux/arm/v7)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: 3.3/18/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.3/18/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.3/18/slim/Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: 3.3/18/slim/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Artifacts

Produced during runtime
Name Size Digest
timbru31~docker-ruby-node~5ECU4C.dockerbuild Expired
209 KB
sha256:45226e39d6f4c410d0fcd350a2ac69f546ec393818309f41f9e2bd80e1165b9d
timbru31~docker-ruby-node~5MS9E6.dockerbuild Expired
117 KB
sha256:9a0aedc68ef63c011ad0f300bc33fffda9a72ac45ae6022ac04986324b9ee9f4
timbru31~docker-ruby-node~5PDKED.dockerbuild Expired
121 KB
sha256:1f816a0fc667f22bd526ab748cac3fb9fa429307a19111abc720521ed371c9a2
timbru31~docker-ruby-node~63IX28.dockerbuild Expired
203 KB
sha256:7c98f5a6bbf5cd3ac99814b21c013cd71fbe8f707835df4205845f13494c9c7a
timbru31~docker-ruby-node~766289.dockerbuild Expired
14.1 KB
sha256:f55a3bf0e4c67733d5b1fdb753ef5d93c69db60530659dc7815ab001e216e38b
timbru31~docker-ruby-node~9G3KSD.dockerbuild Expired
13.8 KB
sha256:afa2f13e96c7eea2918691ffedf7eb5282a54d56e749953cedc558db22747662
timbru31~docker-ruby-node~9IXJNG.dockerbuild Expired
14.5 KB
sha256:4882ee7f28fbed4a73c2d599d48e951bd93aaa3fe8f411052c68220557a4b72b
timbru31~docker-ruby-node~A2IVG2.dockerbuild Expired
140 KB
sha256:15e1b8185086804c04ba51a7d6ea37031a647ac1020b8293cf0bde93b745f101
timbru31~docker-ruby-node~AX9HEX.dockerbuild Expired
117 KB
sha256:b6834ae4dc0acd3827c43a6d9ae005241afa3bfc8207fa03bc06e46307996e4b
timbru31~docker-ruby-node~EDHD3N.dockerbuild Expired
172 KB
sha256:b8708b4b7aedb94d81a00007e87dea19fa7a7819f1b404f1ff5ea9e624cd0627
timbru31~docker-ruby-node~H2XZA1.dockerbuild Expired
135 KB
sha256:65ed206a07de47bdaf383424c8bc4c3fcdb35d7846a5e07fe6b6b2552a357136
timbru31~docker-ruby-node~HM8K0H.dockerbuild Expired
118 KB
sha256:111cb157b6ab4d453ab0bd935d1c796a4ee8a1d0cc59792ba2da310ed0c47ad5
timbru31~docker-ruby-node~IATYNR.dockerbuild Expired
175 KB
sha256:f193a550c99f2db345ee53e0733eecd39597439f91226b7f6ff409faeda3c88d
timbru31~docker-ruby-node~IQL54J.dockerbuild Expired
135 KB
sha256:cc57574a02589671b66ca721bf071005ada8e7cb654ea2c64483b43ab34a2dda
timbru31~docker-ruby-node~JDZZD2.dockerbuild Expired
114 KB
sha256:b2d3e5c2df7662a14eedfa7999782a879be5626aa2ce7468cd6d2047ceaa0ebe
timbru31~docker-ruby-node~N58XBC.dockerbuild Expired
118 KB
sha256:bf67e5eea5605015c8ef5d3be5b17e395d40df2092b08a309ec1aca9bae18e12
timbru31~docker-ruby-node~NTOPA4.dockerbuild Expired
263 KB
sha256:8c6627439d262ee9b0aa7ddf405fbda9ac0f29df23bf565a62d2853922a2d240
timbru31~docker-ruby-node~OCMUMZ.dockerbuild Expired
115 KB
sha256:c776e1dcab43a0253ff3c5d005eea5e22084f481a290e929cad4a5b9b345f112
timbru31~docker-ruby-node~OSCVGO.dockerbuild Expired
119 KB
sha256:e92862a536250365ab22cf6cee3d355f62fa83f11aae8eda98d8cb7adf359219
timbru31~docker-ruby-node~PSSTMM.dockerbuild Expired
181 KB
sha256:f85a7c0edde094c1429a8bcbe6b09cab741e27ca8b8f35923fa81a47dc89bdf0
timbru31~docker-ruby-node~QNQAJ5.dockerbuild Expired
174 KB
sha256:4549221d9d461952beaf4e42d58f21fe7b93a25e4f7b069e5b6f31a2ad0634d0
timbru31~docker-ruby-node~R1PLF5.dockerbuild Expired
16.8 KB
sha256:e7c1108978969430cf4a318549b2d70da819b0375f5b7e5c7121d4b37cf2c2b4
timbru31~docker-ruby-node~SWZSKY.dockerbuild Expired
117 KB
sha256:3b5d372d6bf3552d624a07956352c92753a05636b0c899debba53218fe997b0e
timbru31~docker-ruby-node~TIEE3A.dockerbuild Expired
169 KB
sha256:5ca4ece7499d446cd919241202458fef3f95c41084b76d4a8acd11052c38ac79
timbru31~docker-ruby-node~UL2LZ5.dockerbuild Expired
16.6 KB
sha256:e29c7e81d27b68e98cf2a8adbaebecb69db0c2a1159d0d063daab8261aef2a17
timbru31~docker-ruby-node~UN2OBP.dockerbuild Expired
14.1 KB
sha256:1bdbeea659c321bda0b2d4e8b6e75775ace0ed410f3c4b06a0e1df8105743013
timbru31~docker-ruby-node~UZPJBA.dockerbuild Expired
14.5 KB
sha256:4276ab98046f2e6f457f9c07c2b2242adf488459b86349ecfaec22a9640b9cea
timbru31~docker-ruby-node~VDWPRS.dockerbuild Expired
13.4 KB
sha256:e386f1e36b8eae14c6990b8347447eb3a0acb61c3d0b1e5ec202598c94ce173a
timbru31~docker-ruby-node~VKX370.dockerbuild Expired
115 KB
sha256:341acb310102e03b879d347206b0396d48dd0a60ea4d77fa0ba689f13aa5577c
timbru31~docker-ruby-node~VNA6CL.dockerbuild Expired
16.6 KB
sha256:0b10077d6a2c613c3c545de89b2bcf491051c3d5386b0c990641722c37955e13
timbru31~docker-ruby-node~W17BOY.dockerbuild Expired
178 KB
sha256:922a0fa6a4de8c71d69966522287a4ec8ec927a67efb2fac9e3ec56d9dbc225e
timbru31~docker-ruby-node~WI438R.dockerbuild Expired
14.8 KB
sha256:b5ba3dd3950a0bdc85ecd9ed6a8652123fdbd79624b3e9e36058493bbaee1743
timbru31~docker-ruby-node~X4S3U6.dockerbuild Expired
121 KB
sha256:2f4fa12803c557f02e97cbea5076407077d1b802548bb5b4a8bb8b26506b3d5a
timbru31~docker-ruby-node~Y404PE.dockerbuild Expired
176 KB
sha256:f43e0dda6431ff65075c6211766b7b85f7f6a3286d9c75b8b104300c78e2411b
timbru31~docker-ruby-node~YDE4MR.dockerbuild Expired
137 KB
sha256:0006c42bfbd3e1ea82d7b5b48d5dddf39dafce2aab0f2f8102a5c573e14477f1
timbru31~docker-ruby-node~YPT27U.dockerbuild Expired
177 KB
sha256:ab1aac7b2202c2a57547058b3085f5b6b24514773c2b155a5f8cee152926b751