build(deps): bump docker/setup-buildx-action from 3.7.1 to 3.8.0 #2071
dependabot[bot]Annotations
15 errors and 104 warnings
|
buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)
RPC failed; HTTP 503 curl 22 The requested URL returned error: 503
|
|
|
|
buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)
the remote end hung up unexpectedly
|
|
buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)
RPC failed; HTTP 503 curl 22 The requested URL returned error: 503
|
|
|
|
buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)
The process '/usr/bin/git' failed with exit code 128
|
|
buildx (3.2/18/slim, 3.2-slim-18 3.2-slim-hydrogen, linux/amd64,linux/arm64,linux/arm/v7)
unable to access 'https://github.com/timbru31/docker-ruby-node/': The requested URL returned error: 503
|
|
buildx (3.2/18/slim, 3.2-slim-18 3.2-slim-hydrogen, linux/amd64,linux/arm64,linux/arm/v7)
RPC failed; HTTP 503 curl 22 The requested URL returned error: 503
|
|
|
|
buildx (3.2/18/slim, 3.2-slim-18 3.2-slim-hydrogen, linux/amd64,linux/arm64,linux/arm/v7)
unable to access 'https://github.com/timbru31/docker-ruby-node/': The requested URL returned error: 502
|
|
buildx (3.2/18/slim, 3.2-slim-18 3.2-slim-hydrogen, linux/amd64,linux/arm64,linux/arm/v7)
The process '/usr/bin/git' failed with exit code 128
|
|
buildx (3.2/20/alpine, 3.2-alpine-20 3.2-alpine-iron 3.2-alpine, linux/amd64,linux/arm64,linux/pp...
RPC failed; HTTP 503 curl 22 The requested URL returned error: 503
|
|
|
|
buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)
unable to access 'https://github.com/timbru31/docker-ruby-node/': The requested URL returned error: 503
|
|
buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)
expected 'packfile'
|
|
buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...
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.1/20/alpine, 3.1-alpine-20 3.1-alpine-iron 3.1-alpine, linux/amd64,linux/arm64,linux/pp...
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, 3.2-alpine-18 3.2-alpine-hydrogen, linux/amd64,linux/arm64,linux/ppc64le,l...
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/18/alpine, 3.1-alpine-18 3.1-alpine-hydrogen, linux/amd64,linux/arm64,linux/ppc64le,l...
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, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...
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.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
|
|
buildx (3.2/18/slim, 3.2-slim-18 3.2-slim-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
|
|
buildx (3.2/20/alpine, 3.2-alpine-20 3.2-alpine-iron 3.2-alpine, linux/amd64,linux/arm64,linux/pp...
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.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.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.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/
|
|
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/
|
|
buildx (3.3/18/alpine, 3.3-alpine-18 3.3-alpine-hydrogen, linux/amd64,linux/arm64,linux/ppc64le,l...
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.3/20/alpine, 3.3-alpine-20 3.3-alpine-iron 3.3-alpine 3-alpine alpine, linux/amd64,linu...
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/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...
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.1/20/slim, 3.1-slim-20 3.1-slim-iron 3.1-slim, 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/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.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.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.2/20/slim, 3.2-slim-20 3.2-slim-iron 3.2-slim, 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/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.4/18/alpine, 3.4-alpine-18 3.4-alpine-hydrogen, linux/amd64,linux/arm64,linux/ppc64le,l...
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.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/
|
|
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#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/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/
|
|
buildx (3.4/20/alpine, 3.4-alpine-20 3.4-alpine-iron 3.4-alpine, linux/amd64,linux/arm64,linux/pp...
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.1/18/slim, 3.1-slim-18 3.1-slim-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/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/alpine, 3.4-alpine-22 3.4-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...
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/20/slim, 3.3-slim-20 3.3-slim-iron 3.3-slim 3-slim slim, linux/amd64,linux/arm64,lin...
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/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.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.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, 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.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/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.4/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.4/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/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
|
|
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/
|
|
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/
|
|
buildx (3.3/18/slim, 3.3-slim-18 3.3-slim-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/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/20/slim, 3.4-slim-20 3.4-slim-iron 3.4-slim, 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.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/
|
|
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/
|
|
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
|
|
Legacy key/value format with whitespace separator should not be used:
3.4/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.4/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/18/slim, 3.4-slim-18 3.4-slim-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.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 | |
|---|---|---|
|
timbru31~docker-ruby-node~0CFQ2V.dockerbuild
|
69.3 KB |
|
|
timbru31~docker-ruby-node~5NIR7A.dockerbuild
|
57.4 KB |
|
|
timbru31~docker-ruby-node~82IPZP.dockerbuild
|
68.5 KB |
|
|
timbru31~docker-ruby-node~A7JH7Z.dockerbuild
|
59.5 KB |
|
|
timbru31~docker-ruby-node~BPFK1S.dockerbuild
|
97.4 KB |
|
|
timbru31~docker-ruby-node~C5CGAN.dockerbuild
|
98.6 KB |
|
|
timbru31~docker-ruby-node~CK6TZD.dockerbuild
|
59.8 KB |
|
|
timbru31~docker-ruby-node~DBEXJE.dockerbuild
|
103 KB |
|
|
timbru31~docker-ruby-node~H9LDHN.dockerbuild
|
98.4 KB |
|
|
timbru31~docker-ruby-node~ITZ1PS.dockerbuild
|
66.9 KB |
|
|
timbru31~docker-ruby-node~JSYNOX.dockerbuild
|
105 KB |
|
|
timbru31~docker-ruby-node~K6752M.dockerbuild
|
70.9 KB |
|
|
timbru31~docker-ruby-node~KLB8Z8.dockerbuild
|
68.1 KB |
|
|
timbru31~docker-ruby-node~KVTUIK.dockerbuild
|
58.8 KB |
|
|
timbru31~docker-ruby-node~L5JBOR.dockerbuild
|
92 KB |
|
|
timbru31~docker-ruby-node~L6AD5C.dockerbuild
|
69.8 KB |
|
|
timbru31~docker-ruby-node~LCYWEZ.dockerbuild
|
58.8 KB |
|
|
timbru31~docker-ruby-node~M9JZFG.dockerbuild
|
101 KB |
|
|
timbru31~docker-ruby-node~MSVKU2.dockerbuild
|
57.3 KB |
|
|
timbru31~docker-ruby-node~N7RLEQ.dockerbuild
|
98.1 KB |
|
|
timbru31~docker-ruby-node~ONSYHQ.dockerbuild
|
70.2 KB |
|
|
timbru31~docker-ruby-node~P9YL4M.dockerbuild
|
59.2 KB |
|
|
timbru31~docker-ruby-node~QE584F.dockerbuild
|
58.1 KB |
|
|
timbru31~docker-ruby-node~QOD022.dockerbuild
|
57.4 KB |
|
|
timbru31~docker-ruby-node~RANKH6.dockerbuild
|
102 KB |
|
|
timbru31~docker-ruby-node~T00INP.dockerbuild
|
103 KB |
|
|
timbru31~docker-ruby-node~T6IJX4.dockerbuild
|
57.1 KB |
|
|
timbru31~docker-ruby-node~V82IMT.dockerbuild
|
105 KB |
|
|
timbru31~docker-ruby-node~VHSKQ7.dockerbuild
|
68.5 KB |
|
|
timbru31~docker-ruby-node~WTECTR.dockerbuild
|
68.4 KB |
|
|
timbru31~docker-ruby-node~Y4O5NO.dockerbuild
|
104 KB |
|
|
timbru31~docker-ruby-node~Y8830C.dockerbuild
|
59.3 KB |
|
|
timbru31~docker-ruby-node~Z5BX0E.dockerbuild
|
58.2 KB |
|
|
timbru31~docker-ruby-node~ZW2RLZ.dockerbuild
|
68.4 KB |
|