Skip to content

buildx

buildx #2277

Triggered via schedule June 4, 2025 05:45
Status Success
Total duration 3m 35s
Artifacts 18

buildx.yml

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

Annotations

36 warnings
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.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.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/
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.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.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/
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/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/
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/
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.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/
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.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/
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.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.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.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/
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/
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.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/
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/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.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.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/
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/
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/
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/
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.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.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/

Artifacts

Produced during runtime
Name Size Digest
timbru31~docker-ruby-node~4K0RAA.dockerbuild
111 KB
sha256:f1a9faf5b3b621070c28e51be3f2b8feb8b6b47b4a4b6bab8bf0013033b4403c
timbru31~docker-ruby-node~7BQQWH.dockerbuild
110 KB
sha256:3ed2cef7236d6ddc14f169a9902a15b9e44354c5ccfe6c0972f7a9fb65217568
timbru31~docker-ruby-node~BOB0EH.dockerbuild
121 KB
sha256:7c508a5bd82f9d63016bb13e66fff004e0b30913a9d3c4204f4eabc05fa6b697
timbru31~docker-ruby-node~BVREBO.dockerbuild
146 KB
sha256:2618ca54b5c6a0407c0a93359564982d279fca6dbaf50b4944b43f44f244a69c
timbru31~docker-ruby-node~CWWPB2.dockerbuild
237 KB
sha256:46045201f82103f46a489505c76dc6681c6232fa8462bec63a0e4d3b3e530ece
timbru31~docker-ruby-node~E6YM2Z.dockerbuild
178 KB
sha256:5a664212ac97355a57bc8ab5fe4544ef84ad8005d67a0f5487ee144f41cec69b
timbru31~docker-ruby-node~GJRD9B.dockerbuild
111 KB
sha256:6e239b3c2d9a0870d5b5e37c97a39bc3055cd14ddc2cd44679579a559096c5f9
timbru31~docker-ruby-node~I2G12K.dockerbuild
121 KB
sha256:99fda22d553507f3a0fcc6fa23aa97829e8c35d6398c9ecec9a616be1a91eda6
timbru31~docker-ruby-node~IO4QOD.dockerbuild
121 KB
sha256:9d45939aca4f9f17897992892b45ae826599146f6a4700c1f91692f3f0d1b0e1
timbru31~docker-ruby-node~M716PR.dockerbuild
110 KB
sha256:0e967aabb08386d4c418f2743fb42aa5b3ee2ef896cbeeef7e22b8d48589b787
timbru31~docker-ruby-node~NB4FTQ.dockerbuild
108 KB
sha256:1524d23b0f9d74fc703cbd618f4abd23072f04cd5ce27a509adfc247c0475e37
timbru31~docker-ruby-node~ODO39Y.dockerbuild
180 KB
sha256:90b956ce902960132b18317f861888823959f19e88ffac0f2870714078c501ba
timbru31~docker-ruby-node~SBEC1F.dockerbuild
181 KB
sha256:b06ad63674de94a76c303500c4010b9f6ed04785acc31c64ce686fb578413b5e
timbru31~docker-ruby-node~U0RXIQ.dockerbuild
177 KB
sha256:1e1df5739e56d2a94e099ce9c743f33b477ecb411228525cf07f318b0a30e9f7
timbru31~docker-ruby-node~URAOGX.dockerbuild
117 KB
sha256:38982814ed923e2e9476a1a3bcceebf6f8cfbf61b58735d1a6a39eb1847521ba
timbru31~docker-ruby-node~WG95WJ.dockerbuild
122 KB
sha256:f8176c25d98d94113084d86859b7602e470b31c79123eb1c0661068f116f0eff
timbru31~docker-ruby-node~XP261E.dockerbuild
174 KB
sha256:e770f1ffc164f5644175650b0c3ae7cb5664b64eeae11ac81098508363abd9dd
timbru31~docker-ruby-node~YW4LAL.dockerbuild
150 KB
sha256:918629ea28e662180d2135af0f19620167f2de8ec47100fa23fd51b5afd08b54