Skip to content

buildx

buildx #2251

Triggered via schedule May 11, 2025 05:43
Status Success
Total duration 3m 31s
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.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.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.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.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.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.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.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/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.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.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/
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.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.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/
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/

Artifacts

Produced during runtime
Name Size Digest
timbru31~docker-ruby-node~8HJBVM.dockerbuild
178 KB
sha256:17bbf4f27da8251dc563017b26f1384edab6cb91b9ee96bd7e49f6024d31af29
timbru31~docker-ruby-node~8LWZIL.dockerbuild
181 KB
sha256:9cee8155cc2a9c48179247446478d9eae5645221821ba8800ff5ef17aab8b842
timbru31~docker-ruby-node~E07JIR.dockerbuild
119 KB
sha256:51373fc49ee8edf54424bbb97766912b79274d801fd064a262cd9c20a7c09dcb
timbru31~docker-ruby-node~F1FAJG.dockerbuild
171 KB
sha256:bad2759321f0e55cf7dd9069d81c0a48c4775c3f0190755e6798d5436a429e7d
timbru31~docker-ruby-node~FTNBAB.dockerbuild
148 KB
sha256:e602a171d730e1d0cac5a6b06a788d840da4745e2f43d339acc3d5014e4ec3a0
timbru31~docker-ruby-node~KBT7GI.dockerbuild
105 KB
sha256:2247675472d6fecadd25867376ebddb0bc72a2596fc8b0b30aa226d22b8e4468
timbru31~docker-ruby-node~KLSPF0.dockerbuild
105 KB
sha256:270dabacf02f6e078d367956519951d215dc93bceb04c91f98b862145cd6e150
timbru31~docker-ruby-node~KV9U0J.dockerbuild
122 KB
sha256:43b10dd5e4befc3f22a7bd9536951282b5e35aba104e3fe21c3508041857525b
timbru31~docker-ruby-node~M0OTSL.dockerbuild
169 KB
sha256:5f64e9916058819e7914cba8d3b8512e7613d5f972f3f3e405511c5ab223b9e5
timbru31~docker-ruby-node~NOQGYC.dockerbuild
141 KB
sha256:ef3c97f62e1a876ba4cc13994cada8a4032976f941b0c62c8495b1e90a92ccc2
timbru31~docker-ruby-node~NT5VN3.dockerbuild
121 KB
sha256:76c0fe2b02d8e93ad08400f6a647c3d3c5670222342036d077a88d5005619262
timbru31~docker-ruby-node~OIIC29.dockerbuild
104 KB
sha256:9aa30c149bca305a90ea0fb8c24314e3167e1eaafe99eb4b0d17f3ce7d51d72b
timbru31~docker-ruby-node~R8XM5F.dockerbuild
119 KB
sha256:c3f4b6fe35b91ca56e911eedcf7a864211c39c5b25cf3b86edb9d91d680cdde6
timbru31~docker-ruby-node~SAIRM5.dockerbuild
177 KB
sha256:0cd58086fd5ab54bb0ccdd4bc81259e787967842fb407e9ab7045b3f3deefd5f
timbru31~docker-ruby-node~SKARHW.dockerbuild
104 KB
sha256:f48edcd6cb13b5afc4b2e77100be0482c3ff13e79ee5173c780d59def741b46f
timbru31~docker-ruby-node~WCA9VZ.dockerbuild
120 KB
sha256:e2cc500c939828212598041082a6fe62e22c26f14debd16eaff504e78b24937c
timbru31~docker-ruby-node~XK6Q66.dockerbuild
104 KB
sha256:d8c23534ef23216ec3659663d387c20466baebf41bda743ae59f5ee9f60621cc
timbru31~docker-ruby-node~Z7AQVD.dockerbuild
232 KB
sha256:34eabf934861f0ef3b366e78e00adca420473b2d47bec01b7cc37bbb177462b7