Skip to content

fix: buildx syntax #2114

fix: buildx syntax

fix: buildx syntax #2114

Triggered via pull request January 16, 2025 08:38
Status Failure
Total duration 3m 50s
Artifacts 12

buildx.yml

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

Annotations

24 errors and 60 warnings
buildx (3.1, 18, slim)
buildx failed with: ERROR: unable to prepare context: path "./3.1/18/$" not found
buildx (3.1, 18, alpine)
buildx failed with: ERROR: unable to prepare context: path "./3.1/18/$" not found
buildx (3.1, 22, alpine)
buildx failed with: ERROR: unable to prepare context: path "./3.1/22/$" not found
buildx (3.1, 20, slim)
buildx failed with: ERROR: unable to prepare context: path "./3.1/20/$" not found
buildx (3.1, 20, alpine)
buildx failed with: ERROR: unable to prepare context: path "./3.1/20/$" not found
buildx (3.1, 22, slim)
buildx failed with: ERROR: unable to prepare context: path "./3.1/22/$" not found
buildx (3.2, 20, alpine)
buildx failed with: ERROR: unable to prepare context: path "./3.2/20/$" not found
buildx (3.2, 18, alpine)
buildx failed with: ERROR: unable to prepare context: path "./3.2/18/$" not found
buildx (3.2, 18, slim)
buildx failed with: ERROR: unable to prepare context: path "./3.2/18/$" not found
buildx (3.3, 18, alpine)
buildx failed with: ERROR: unable to prepare context: path "./3.3/18/$" not found
buildx (3.2, 22, alpine)
buildx failed with: ERROR: unable to prepare context: path "./3.2/22/$" not found
buildx (3.3, 18, slim)
buildx failed with: ERROR: unable to prepare context: path "./3.3/18/$" not found
buildx (3.2, 20, slim)
buildx failed with: ERROR: unable to prepare context: path "./3.2/20/$" not found
buildx (3.2, 22, slim)
buildx failed with: ERROR: unable to prepare context: path "./3.2/22/$" not found
buildx (3.3, 20, slim)
buildx failed with: ERROR: unable to prepare context: path "./3.3/20/$" not found
buildx (3.3, 20, alpine)
buildx failed with: ERROR: unable to prepare context: path "./3.3/20/$" not found
buildx (3.3, 22, alpine)
buildx failed with: ERROR: unable to prepare context: path "./3.3/22/$" not found
buildx (3.3, 22, slim)
buildx failed with: ERROR: unable to prepare context: path "./3.3/22/$" not found
buildx (3.4, 18, slim)
buildx failed with: ERROR: unable to prepare context: path "./3.4/18/$" not found
buildx (3.4, 20, alpine)
buildx failed with: ERROR: unable to prepare context: path "./3.4/20/$" not found
buildx (3.4, 18, alpine)
buildx failed with: ERROR: unable to prepare context: path "./3.4/18/$" not found
buildx (3.4, 22, alpine)
buildx failed with: ERROR: unable to prepare context: path "./3.4/22/$" not found
buildx (3.4, 22, slim)
buildx failed with: ERROR: unable to prepare context: path "./3.4/22/$" not found
buildx (3.4, 20, slim)
buildx failed with: ERROR: unable to prepare context: path "./3.4/20/$" not found
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, 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, 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.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, 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, 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.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, 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, 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, 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.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, 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.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.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.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, 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.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, 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, 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, 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.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.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#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, 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.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.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.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.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.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.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#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.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, 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/

Artifacts

Produced during runtime
Name Size Digest
timbru31~docker-ruby-node~0HJU07.dockerbuild Expired
57.8 KB
sha256:b23bba1c2db7ba4c550643614acf2bdcf0161f4fb370fe650f95caa22bbdb10b
timbru31~docker-ruby-node~0N65I6.dockerbuild Expired
59.5 KB
sha256:67c049d4351e25dcbe8610f9db3a91c3c9ebea0af2094ea0f1d1c17a3e66dd8b
timbru31~docker-ruby-node~71B3ZQ.dockerbuild Expired
59.7 KB
sha256:3c4283b5799095cdc35251b0e95a73455bd9a8d9b761e424040c15d10adffeed
timbru31~docker-ruby-node~I34ZLE.dockerbuild Expired
59 KB
sha256:ea5149b50f59a03daf83e57129817dd266764a06568182ba24593f5b965006b4
timbru31~docker-ruby-node~O96WQP.dockerbuild Expired
58.7 KB
sha256:808ba8116f050d177bcd68aca034d0f080f0d68473556453423842161a23b036
timbru31~docker-ruby-node~P2NAIW.dockerbuild Expired
60.2 KB
sha256:86251697a8cb5e83d0d60b23efef6860f08e0d30ed262e14e847d3b96b97cb2f
timbru31~docker-ruby-node~RA4U92.dockerbuild Expired
59.3 KB
sha256:2a55b8977e0b29c537c90b30fe13baddae1426319a5d5c1d1bfd8df8cced3f79
timbru31~docker-ruby-node~SEIDZH.dockerbuild Expired
57.3 KB
sha256:bbc31cf69420421ae20a48a86e5170b3f7b165542f6f845cb2baa04f49219989
timbru31~docker-ruby-node~UVLGE8.dockerbuild Expired
59.2 KB
sha256:90adc91e29064fe0dc53263f03654e728d26381391d8fe7501897b32ec8ece03
timbru31~docker-ruby-node~VAXPY4.dockerbuild Expired
60.3 KB
sha256:ea00443eda5eddcc8b4aea61640047933d881b66ae60c92598cadcab718af2bf
timbru31~docker-ruby-node~W8DE70.dockerbuild Expired
58.4 KB
sha256:c37cadab5ea332e08ee52fe9f194a0d28bed1ae0b7d06fd560b5f21e01eb18fd
timbru31~docker-ruby-node~WO5T5E.dockerbuild Expired
57.4 KB
sha256:3f74b7a51dca982da307d8f29fca8177db0bafb461f36ec6fa186ac71d01af87