buildx #2112
timbru31Annotations
57 errors and 60 warnings
|
buildx (3.1, 20, alpine)
Process completed with exit code 1.
|
|
buildx (3.1, 20, alpine)
Process completed with exit code 1.
|
|
buildx (3.1, 18, slim)
Process completed with exit code 1.
|
|
buildx (3.1, 18, slim)
Process completed with exit code 1.
|
|
buildx (3.1, 18, alpine)
Process completed with exit code 1.
|
|
buildx (3.1, 18, alpine)
Process completed with exit code 1.
|
|
buildx (3.1, 22, slim)
Process completed with exit code 1.
|
|
buildx (3.1, 22, slim)
Process completed with exit code 1.
|
|
buildx (3.1, 20, slim)
Process completed with exit code 1.
|
|
buildx (3.1, 20, slim)
Process completed with exit code 1.
|
|
buildx (3.2, 18, slim)
Process completed with exit code 1.
|
|
buildx (3.2, 18, slim)
Process completed with exit code 1.
|
|
buildx (3.2, 20, slim)
Process completed with exit code 1.
|
|
buildx (3.2, 20, slim)
Process completed with exit code 1.
|
|
buildx (3.2, 18, alpine)
Process completed with exit code 1.
|
|
buildx (3.2, 18, alpine)
Process completed with exit code 1.
|
|
buildx (3.2, 22, slim)
Process completed with exit code 1.
|
|
buildx (3.2, 22, slim)
Process completed with exit code 1.
|
|
buildx (3.3, 18, alpine)
Process completed with exit code 1.
|
|
buildx (3.3, 18, alpine)
Process completed with exit code 1.
|
|
buildx (3.1, 22, alpine)
Process completed with exit code 1.
|
|
buildx (3.1, 22, alpine)
Process completed with exit code 1.
|
|
buildx (3.2, 22, alpine)
Process completed with exit code 1.
|
|
buildx (3.2, 22, alpine)
Process completed with exit code 1.
|
|
buildx (3.2, 20, alpine)
Process completed with exit code 1.
|
|
buildx (3.2, 20, alpine)
Process completed with exit code 1.
|
|
buildx (3.3, 18, slim)
Process completed with exit code 1.
|
|
buildx (3.3, 18, slim)
Process completed with exit code 1.
|
|
buildx (3.3, 22, slim)
Process completed with exit code 1.
|
|
buildx (3.3, 22, slim)
Process completed with exit code 1.
|
|
buildx (3.3, 20, slim)
Process completed with exit code 1.
|
|
buildx (3.3, 20, slim)
Process completed with exit code 1.
|
|
buildx (3.4, 18, alpine)
Process completed with exit code 1.
|
|
buildx (3.4, 18, alpine)
Process completed with exit code 1.
|
|
buildx (3.4, 20, alpine)
Process completed with exit code 1.
|
|
buildx (3.4, 20, alpine)
Process completed with exit code 1.
|
|
buildx (3.3, 20, alpine)
Process completed with exit code 1.
|
|
buildx (3.3, 20, alpine)
Process completed with exit code 1.
|
|
buildx (3.3, 22, alpine)
Process completed with exit code 1.
|
|
buildx (3.3, 22, alpine)
Process completed with exit code 1.
|
|
buildx (3.4, 18, slim)
Process completed with exit code 1.
|
|
buildx (3.4, 18, slim)
Process completed with exit code 1.
|
|
buildx (3.4, 22, alpine)
Process completed with exit code 1.
|
|
buildx (3.4, 22, alpine)
Process completed with exit code 1.
|
|
buildx (3.4, 20, slim)
Process completed with exit code 1.
|
|
buildx (3.4, 20, slim)
Process completed with exit code 1.
|
|
buildx (3.4, 22, slim)
Process completed with exit code 1.
|
|
buildx (3.4, 22, slim)
Process completed with exit code 1.
|
|
buildx (3.1, 20, default)
Process completed with exit code 1.
|
|
buildx (3.4, 20, default)
Process completed with exit code 1.
|
|
buildx (3.3, 22, default)
Process completed with exit code 1.
|
|
buildx (3.2, 20, default)
Process completed with exit code 1.
|
|
buildx (3.4, 22, default)
Process completed with exit code 1.
|
|
buildx (3.1, 18, default)
Process completed with exit code 1.
|
|
buildx (3.4, 18, default)
Process completed with exit code 1.
|
|
buildx (3.3, 18, default)
Process completed with exit code 1.
|
|
buildx (3.2, 18, default)
Process completed with exit code 1.
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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.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, 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#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.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.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.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.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.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.4, 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.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.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.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.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.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/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
timbru31~docker-ruby-node~1S2E0M.dockerbuild
|
105 KB |
|
|
timbru31~docker-ruby-node~3KLFYI.dockerbuild
|
104 KB |
|
|
timbru31~docker-ruby-node~77YNT4.dockerbuild
|
106 KB |
|
|
timbru31~docker-ruby-node~8Z58PW.dockerbuild
|
103 KB |
|
|
timbru31~docker-ruby-node~D6VOSD.dockerbuild
|
138 KB |
|
|
timbru31~docker-ruby-node~GL1EKA.dockerbuild
|
104 KB |
|
|
timbru31~docker-ruby-node~HCTG4B.dockerbuild
|
103 KB |
|
|
timbru31~docker-ruby-node~J02921.dockerbuild
|
102 KB |
|
|
timbru31~docker-ruby-node~MUW9XI.dockerbuild
|
106 KB |
|
|
timbru31~docker-ruby-node~O7GXFD.dockerbuild
|
102 KB |
|
|
timbru31~docker-ruby-node~X9XZ0U.dockerbuild
|
105 KB |
|
|
timbru31~docker-ruby-node~ZDMRLT.dockerbuild
|
104 KB |
|