buildx #2120
timbru31Annotations
18 errors and 104 warnings
|
buildx (3.4, 22, slim)
buildx failed with: ERROR: failed to solve: ruby:3.4-slim: failed to resolve source metadata for docker.io/library/ruby:3.4-slim: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/ruby/manifests/sha256:b3c5ff853c4a4468300592cb1c86b4d613a7e3791a413515c6d9cd6fb2df38c9: 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)
Process completed with exit code 1.
|
|
buildx (3.4, 22, default)
Process completed with exit code 1.
|
|
buildx (3.4, 22, default)
buildx failed with: ERROR: failed to solve: ruby:3.4: failed to resolve source metadata for docker.io/library/ruby:3.4: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/ruby/manifests/sha256:ac4f8074376743a56db23139238bd642a6249a25d4aaa250ca7e93332d11681c: 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, slim)
Process completed with exit code 1.
|
|
buildx (3.2, 18, slim)
Process completed with exit code 1.
|
|
buildx (3.3, 20, default)
Process completed with exit code 1.
|
|
buildx (3.4, 20, alpine)
Process completed with exit code 1.
|
|
buildx (3.4, 22, alpine)
Process completed with exit code 1.
|
|
buildx (3.3, 22, default)
Process completed with exit code 1.
|
|
buildx (3.3, 20, slim)
Process completed with exit code 1.
|
|
buildx (3.3, 22, slim)
Process completed with exit code 1.
|
|
buildx (3.3, 18, default)
Process completed with exit code 1.
|
|
buildx (3.3, 18, slim)
Process completed with exit code 1.
|
|
buildx (3.4, 18, default)
Process completed with exit code 1.
|
|
buildx (3.4, 20, default)
Process completed with exit code 1.
|
|
buildx (3.4, 20, slim)
Process completed with exit code 1.
|
|
buildx (3.4, 18, slim)
Process completed with exit code 1.
|
|
buildx (3.1, 18, alpine)
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/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/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/
|
|
buildx (3.2, 22, alpine)
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/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/
|
|
buildx (3.2, 20, alpine)
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/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/
|
|
buildx (3.1, 20, alpine)
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/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/
|
|
buildx (3.2, 18, alpine)
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/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/
|
|
buildx (3.1, 22, alpine)
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/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/
|
|
buildx (3.3, 20, alpine)
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/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/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/
|
|
buildx (3.3, 18, alpine)
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/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/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/
|
|
buildx (3.1, 20, default)
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/
|
|
buildx (3.2, 20, default)
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/
|
|
buildx (3.1, 22, default)
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#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/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, default)
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.1, 20, slim)
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/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/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.2, 20, slim)
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/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.3, 22, alpine)
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/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, 18, alpine)
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.4/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.4/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/
|
|
buildx (3.2, 18, default)
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.1, 18, default)
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.1, 22, slim)
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#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/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.2, 22, slim)
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/
|
|
buildx (3.4, 22, slim)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
buildx (3.4, 22, default)
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, slim)
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.2, 18, slim)
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/
|
|
buildx (3.3, 20, default)
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.4, 20, alpine)
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.4/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.4/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/
|
|
buildx (3.4, 22, alpine)
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.4/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.4/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.3, 22, default)
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, 20, slim)
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#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/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.3, 22, slim)
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/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/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/
|
|
buildx (3.3, 18, default)
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#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/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.3, 18, slim)
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/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/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/
|
|
buildx (3.4, 18, default)
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.4/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.4/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, 20, default)
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.4/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.4/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.4, 20, slim)
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.4/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.4/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.4, 18, slim)
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.4/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.4/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~03WBZ3.dockerbuild
Expired
|
174 KB |
sha256:bed97965ae94e8b32c972db2841459d452a18eadda7e5c8178ba08d3d2e36af5
|
|
|
timbru31~docker-ruby-node~1KFDBC.dockerbuild
Expired
|
121 KB |
sha256:356f1f64b341c7dad8d8c1e5a76104a6275044e268a937392ca19d126602beaa
|
|
|
timbru31~docker-ruby-node~2QHZL3.dockerbuild
Expired
|
106 KB |
sha256:a13f5605328095c0e05b050fb3f38ad81ec03bcb15c8c91b706a85ba1da5e5ed
|
|
|
timbru31~docker-ruby-node~2UP7W7.dockerbuild
Expired
|
105 KB |
sha256:66e2681bbbde47cd3895f0244cd88834cc927932b25825ffa4313abc7407b32e
|
|
|
timbru31~docker-ruby-node~361D1W.dockerbuild
Expired
|
106 KB |
sha256:98e8c8be0e2061ebd9ad1f52c1381ddbb31111165f21d83f6a32ffd5aa3877c9
|
|
|
timbru31~docker-ruby-node~3MVGK7.dockerbuild
Expired
|
104 KB |
sha256:f3ab7abc162902489a4a477625e099abde4fd26262492fc14035f0ea89375aaf
|
|
|
timbru31~docker-ruby-node~4U5O39.dockerbuild
Expired
|
111 KB |
sha256:8106731e12c3c57252695b8a9ac11a58577862d92600b93d034f464e79f7a7b6
|
|
|
timbru31~docker-ruby-node~9BLR5M.dockerbuild
Expired
|
114 KB |
sha256:7b8e6dab7c9040a56be03e688abece9b940aeb60bf2502618acc6d87ffecde2c
|
|
|
timbru31~docker-ruby-node~9VI2KZ.dockerbuild
Expired
|
105 KB |
sha256:c4727e59646aa68bf11b1ca3a393d29e7d965fcd26b7c6b26726bf06b8229dbf
|
|
|
timbru31~docker-ruby-node~A3423B.dockerbuild
Expired
|
102 KB |
sha256:5f63e3ea6365d5f5d47ff0359870f9d187f6833bdea96155751335215a7155c4
|
|
|
timbru31~docker-ruby-node~AS22K9.dockerbuild
Expired
|
105 KB |
sha256:9af64029039012083ddf9c32c78f8e00d9647997072c196fb6b953270c7554c3
|
|
|
timbru31~docker-ruby-node~AZSI2C.dockerbuild
Expired
|
112 KB |
sha256:a894f003bd1a9b1c2928685c68dc70e86574899136b3a3f448b5afa81ab44a79
|
|
|
timbru31~docker-ruby-node~CCENUV.dockerbuild
Expired
|
17.9 KB |
sha256:daf94498abd2685ea20453d2a7f16e1fd3bbd3d704582ff1c400f7aa7a17488c
|
|
|
timbru31~docker-ruby-node~FMUJAJ.dockerbuild
Expired
|
172 KB |
sha256:cf964169d300c9c0eac123726c7d45226dbc17cabb432f0b294d89e4eb99c5c4
|
|
|
timbru31~docker-ruby-node~J8R65P.dockerbuild
Expired
|
105 KB |
sha256:97b935e48cfda01fda09e14451d103f4ce74b32b899bbabadc018b4c0ed5ae9a
|
|
|
timbru31~docker-ruby-node~L2YEQT.dockerbuild
Expired
|
111 KB |
sha256:94bba2bccdd26f3d8716771dfc3c22e6ef561affb8b97456fc9632c1a06d8bd0
|
|
|
timbru31~docker-ruby-node~L4WMLE.dockerbuild
Expired
|
230 KB |
sha256:483ffd49eb9fdc6ff0102ae529123afed18a5bfe0da75abad0df7355084b30d9
|
|
|
timbru31~docker-ruby-node~L8XKRG.dockerbuild
Expired
|
174 KB |
sha256:da19b145564f48599a6ea3a091854b8bf81dc4572ac4e313f29f94222aa24868
|
|
|
timbru31~docker-ruby-node~MLRC4Q.dockerbuild
Expired
|
103 KB |
sha256:0e84a1241f56d7523d94211c6aa6134eccd647da08cf20e20c6129cf8352c484
|
|
|
timbru31~docker-ruby-node~N7I2HI.dockerbuild
Expired
|
181 KB |
sha256:b865a1dbbffc467e12061235633d5623250d7e2e531192091cf6805109635079
|
|
|
timbru31~docker-ruby-node~N8BUPC.dockerbuild
Expired
|
116 KB |
sha256:a59a3ad2efd8e86a2008abb176d7e839a5c1921cd15e865e09c111dba4a0819f
|
|
|
timbru31~docker-ruby-node~NRUAVZ.dockerbuild
Expired
|
179 KB |
sha256:fbe98e91895e577013aba2efa35d9fec55bbcc421bab517ffd581ed0b776ec0a
|
|
|
timbru31~docker-ruby-node~O0GGGL.dockerbuild
Expired
|
115 KB |
sha256:9f90398ffbaa1b867c6cc5081bbdfdbb7a3af747d454a2c6917cc67f906e4b9f
|
|
|
timbru31~docker-ruby-node~O8YPFY.dockerbuild
Expired
|
179 KB |
sha256:a3604c7de2655ca6321e5744d48a26f322c66e91473082174e14b38d0ab90899
|
|
|
timbru31~docker-ruby-node~O9E3NS.dockerbuild
Expired
|
168 KB |
sha256:8064b998ad91bd7fc5fa6d553c8e91199cdeddfcaf2aa0f078efb38d23b03222
|
|
|
timbru31~docker-ruby-node~OFD340.dockerbuild
Expired
|
169 KB |
sha256:1b74d6e6a8cbb6d41b981f30981521e3383e7b4b5b74f39fc9ec37c97646367c
|
|
|
timbru31~docker-ruby-node~OGCVL0.dockerbuild
Expired
|
181 KB |
sha256:49998bf701fb4b99d3668d4c6b1a031d488da72dda9ca6c27094b04462627b8f
|
|
|
timbru31~docker-ruby-node~QOU36I.dockerbuild
Expired
|
105 KB |
sha256:d8a6d0f5fd23028034d0115b70363645ced5427c4b4cef46fb1340cee2622c6d
|
|
|
timbru31~docker-ruby-node~QW6GXN.dockerbuild
Expired
|
176 KB |
sha256:3d873c6355f2f04a7b3862b3b2359b24518986aa6cf0b9931d01dfc16b649e67
|
|
|
timbru31~docker-ruby-node~R33VUO.dockerbuild
Expired
|
114 KB |
sha256:300cc72343c62528ac49c7f071bd65091ab6560c79fa01d021a71582e5c745f1
|
|
|
timbru31~docker-ruby-node~RVIXDB.dockerbuild
Expired
|
104 KB |
sha256:71cc463790d6efa6556c60e3417ff3335322c3af4471ec13ae11464ed1ea3293
|
|
|
timbru31~docker-ruby-node~TPU71Q.dockerbuild
Expired
|
14.3 KB |
sha256:a17eb061f19e9e340ea08759a0301354783ffc6cc957db72c8661f3fc0e86a9b
|
|
|
timbru31~docker-ruby-node~VPSE1Z.dockerbuild
Expired
|
174 KB |
sha256:9c4fc4039fb410dd168476355d1a3652c41b37c166e1033ec3b3990a0c65e406
|
|
|
timbru31~docker-ruby-node~VTM01R.dockerbuild
Expired
|
115 KB |
sha256:42263912820b1a66bbeae62413d3e6f22bdd5a20116c6ac99d2495a06fb76fa8
|
|
|
timbru31~docker-ruby-node~WUCEIJ.dockerbuild
Expired
|
116 KB |
sha256:9882d3b46a1ab2c37e52f7a4b2d75f6a1768afff3a8e1b8c3739044c732652a5
|
|
|
timbru31~docker-ruby-node~ZFR68Q.dockerbuild
Expired
|
114 KB |
sha256:bf03b8c0904ec2594b53beecb63e0f0c928e9aaa0e6e1baf5d329668a793eca2
|
|