Skip to content

buildx

buildx #2062

Triggered via schedule January 16, 2025 04:44
Status Failure
Total duration 10m 31s
Artifacts 48

buildx.yml

on: schedule
Matrix: buildx

Annotations

50 errors and 106 warnings
buildx (21, jdk, 18, alpine)
Process completed with exit code 1.
buildx (17, jre, 22, alpine)
Process completed with exit code 1.
buildx (17, jre, 20, alpine)
Process completed with exit code 1.
buildx (21, jdk, 20, alpine)
Process completed with exit code 1.
buildx (21, jdk, 22, alpine)
Process completed with exit code 1.
buildx (21, jre, 18, alpine)
Process completed with exit code 1.
buildx (21, jre, 18, alpine)
buildx failed with: ERROR: failed to solve: eclipse-temurin:21-jre-alpine: failed to resolve source metadata for docker.io/library/eclipse-temurin:21-jre-alpine: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:4300bfe1e11f3dfc3e3512f39939f9093cf18d0e581d1ab1ccd0512f32fe33f0: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (21, jre, 18, default)
buildx failed with: ERROR: failed to solve: eclipse-temurin:21-jre: failed to resolve source metadata for docker.io/library/eclipse-temurin:21-jre: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:c18ede999b05bef3e2da98c2ed2e2d5eda605385cdfb691858abb1b6161c6a35: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (21, jre, 18, default)
Process completed with exit code 1.
buildx (21, jre, 20, default)
Process completed with exit code 1.
buildx (21, jre, 20, default)
buildx failed with: ERROR: failed to solve: eclipse-temurin:21-jre: failed to resolve source metadata for docker.io/library/eclipse-temurin:21-jre: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:c1f2e1f082e26dd30c4ea73b3b17b24b473ab122226225dd8dcba71406167537: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (21, jdk, 22, default)
buildx failed with: ERROR: failed to solve: eclipse-temurin:21-jdk: failed to resolve source metadata for docker.io/library/eclipse-temurin:21-jdk: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:a20cfa6afdbf57ff2c4de77ae2d0e3725a6349f1936b5ad7c3d1b06f6d1b840a: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (21, jdk, 22, default)
Process completed with exit code 1.
buildx (21, jre, 22, default)
buildx failed with: ERROR: failed to solve: eclipse-temurin:21-jre: failed to resolve source metadata for docker.io/library/eclipse-temurin:21-jre: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:c1f2e1f082e26dd30c4ea73b3b17b24b473ab122226225dd8dcba71406167537: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (21, jre, 22, default)
Process completed with exit code 1.
buildx (21, jre, 22, alpine)
Process completed with exit code 1.
buildx (21, jre, 22, alpine)
buildx failed with: ERROR: failed to solve: eclipse-temurin:21-jre-alpine: failed to resolve source metadata for docker.io/library/eclipse-temurin:21-jre-alpine: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:4300bfe1e11f3dfc3e3512f39939f9093cf18d0e581d1ab1ccd0512f32fe33f0: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (8, jdk, 18, default)
Process completed with exit code 1.
buildx (8, jdk, 18, default)
buildx failed with: ERROR: failed to solve: eclipse-temurin:8-jdk: failed to resolve source metadata for docker.io/library/eclipse-temurin:8-jdk: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:b99df91afc036cf1ca0ff9fe21a96ed405a5e3f4bbfbadf60c646eb181ca780d: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (8, jdk, 18, alpine)
Process completed with exit code 1.
buildx (8, jdk, 18, alpine)
buildx failed with: ERROR: failed to solve: eclipse-temurin:8-jdk-alpine: failed to resolve source metadata for docker.io/library/eclipse-temurin:8-jdk-alpine: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:cbae408cfb32eae0bd7e763f5348a38e048f2230f4f5fc2abf604a5214b74c0e: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (8, jdk, 20, alpine)
buildx failed with: ERROR: failed to solve: eclipse-temurin:8-jdk-alpine: failed to resolve source metadata for docker.io/library/eclipse-temurin:8-jdk-alpine: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:cbae408cfb32eae0bd7e763f5348a38e048f2230f4f5fc2abf604a5214b74c0e: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (8, jdk, 20, alpine)
Process completed with exit code 1.
buildx (21, jre, 20, alpine)
Process completed with exit code 1.
buildx (21, jre, 20, alpine)
buildx failed with: ERROR: failed to solve: eclipse-temurin:21-jre-alpine: failed to resolve source metadata for docker.io/library/eclipse-temurin:21-jre-alpine: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:4300bfe1e11f3dfc3e3512f39939f9093cf18d0e581d1ab1ccd0512f32fe33f0: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (8, jdk, 20, default)
buildx failed with: ERROR: failed to solve: eclipse-temurin:8-jdk: failed to resolve source metadata for docker.io/library/eclipse-temurin:8-jdk: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:b99df91afc036cf1ca0ff9fe21a96ed405a5e3f4bbfbadf60c646eb181ca780d: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (8, jdk, 20, default)
Process completed with exit code 1.
buildx (8, jdk, 22, default)
Process completed with exit code 1.
buildx (8, jdk, 22, default)
buildx failed with: ERROR: failed to solve: eclipse-temurin:8-jdk: failed to resolve source metadata for docker.io/library/eclipse-temurin:8-jdk: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:b99df91afc036cf1ca0ff9fe21a96ed405a5e3f4bbfbadf60c646eb181ca780d: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (8, jdk, 22, alpine)
buildx failed with: ERROR: failed to solve: eclipse-temurin:8-jdk-alpine: failed to resolve source metadata for docker.io/library/eclipse-temurin:8-jdk-alpine: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:ea401b4adeaa7b487270a550076837529a2e05c141e786348487b391454c6ce0: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (8, jdk, 22, alpine)
Process completed with exit code 1.
buildx (8, jre, 18, alpine)
buildx failed with: ERROR: failed to solve: eclipse-temurin:8-jre-alpine: failed to resolve source metadata for docker.io/library/eclipse-temurin:8-jre-alpine: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:6af5651ab87b8cac585e45f7887a2bfdcf42ca6f1cf63fb32f7d51c496963951: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (8, jre, 18, alpine)
Process completed with exit code 1.
buildx (8, jre, 18, default)
Process completed with exit code 1.
buildx (8, jre, 18, default)
buildx failed with: ERROR: failed to solve: eclipse-temurin:8-jre: failed to resolve source metadata for docker.io/library/eclipse-temurin:8-jre: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:337cde9d0484d24079bb7a5b543faf00a65ee9842646ec1ef96c6dd13a7f9a34: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (8, jre, 20, alpine)
buildx failed with: ERROR: failed to solve: eclipse-temurin:8-jre-alpine: failed to resolve source metadata for docker.io/library/eclipse-temurin:8-jre-alpine: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:6af5651ab87b8cac585e45f7887a2bfdcf42ca6f1cf63fb32f7d51c496963951: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (8, jre, 20, alpine)
Process completed with exit code 1.
buildx (8, jre, 20, default)
buildx failed with: ERROR: failed to solve: eclipse-temurin:8-jre: failed to resolve source metadata for docker.io/library/eclipse-temurin:8-jre: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:337cde9d0484d24079bb7a5b543faf00a65ee9842646ec1ef96c6dd13a7f9a34: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (8, jre, 20, default)
Process completed with exit code 1.
buildx (8, jre, 22, alpine)
Process completed with exit code 1.
buildx (8, jre, 22, alpine)
buildx failed with: ERROR: failed to solve: eclipse-temurin:8-jre-alpine: failed to resolve source metadata for docker.io/library/eclipse-temurin:8-jre-alpine: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:6af5651ab87b8cac585e45f7887a2bfdcf42ca6f1cf63fb32f7d51c496963951: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (8, jre, 22, default)
buildx failed with: ERROR: failed to solve: eclipse-temurin:8-jre: failed to resolve source metadata for docker.io/library/eclipse-temurin:8-jre: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:337cde9d0484d24079bb7a5b543faf00a65ee9842646ec1ef96c6dd13a7f9a34: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
buildx (8, jre, 22, default)
Process completed with exit code 1.
buildx (17, jre, 20, default)
Process completed with exit code 1.
buildx (11, jre, 20, default)
Process completed with exit code 1.
buildx (11, jre, 22, default)
Process completed with exit code 1.
buildx (21, jdk, 18, default)
Process completed with exit code 1.
buildx (11, jdk, 18, default)
Process completed with exit code 1.
buildx (21, jdk, 20, default)
Process completed with exit code 1.
buildx (11, jdk, 22, default)
Process completed with exit code 1.
buildx (11, jdk, 20, alpine)
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: 11/jdk/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: 11/jdk/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 (11, jre, 18, alpine)
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: 11/jre/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: 11/jre/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 (11, jre, 22, alpine)
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: 11/jre/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: 11/jre/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 (17, jdk, 22, alpine)
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: 17/jdk/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: 17/jdk/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 (17, jdk, 18, alpine)
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: 17/jdk/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: 17/jdk/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 (11, jdk, 18, alpine)
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: 11/jdk/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/
Legacy key/value format with whitespace separator should not be used: 11/jdk/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/
buildx (17, jdk, 20, alpine)
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: 17/jdk/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: 17/jdk/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 (17, jre, 18, alpine)
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: 17/jre/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: 17/jre/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 (11, jre, 20, alpine)
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: 11/jre/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: 11/jre/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 (11, jdk, 22, alpine)
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: 11/jdk/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: 11/jdk/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 (21, jdk, 18, alpine)
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: 21/jdk/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: 21/jdk/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 (17, jre, 22, alpine)
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: 17/jre/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: 17/jre/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 (17, jre, 20, alpine)
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: 17/jre/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: 17/jre/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 (21, jdk, 20, alpine)
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: 21/jdk/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: 21/jdk/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 (21, jdk, 22, alpine)
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: 21/jdk/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: 21/jdk/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 (21, jre, 18, alpine)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (21, jre, 18, default)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (21, jre, 20, default)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (21, jdk, 22, default)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (21, jre, 22, default)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (21, jre, 22, alpine)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (8, jdk, 18, default)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (8, jdk, 18, alpine)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (8, jdk, 20, alpine)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (21, jre, 20, alpine)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (8, jdk, 20, default)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (8, jdk, 22, default)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (8, jdk, 22, alpine)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (8, jre, 18, alpine)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (8, jre, 18, default)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (8, jre, 20, alpine)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (8, jre, 20, default)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (8, jre, 22, alpine)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (8, jre, 22, default)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
buildx (17, jdk, 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: 17/jdk/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: 17/jdk/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 (17, jre, 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: 17/jre/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: 17/jre/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 (17, jdk, 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: 17/jdk/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: 17/jdk/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 (17, jdk, 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: 17/jdk/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: 17/jdk/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 (11, jre, 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: 11/jre/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: 11/jre/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 (17, jre, 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: 17/jre/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: 17/jre/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 (11, jdk, 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: 11/jdk/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: 11/jdk/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 (17, jre, 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: 17/jre/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: 17/jre/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 (11, jre, 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: 11/jre/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: 11/jre/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 (11, jre, 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: 11/jre/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: 11/jre/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 (21, jdk, 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: 21/jdk/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: 21/jdk/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 (11, jdk, 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: 11/jdk/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: 11/jdk/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 (21, jdk, 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: 21/jdk/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: 21/jdk/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 (11, jdk, 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: 11/jdk/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: 11/jdk/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/

Artifacts

Produced during runtime
Name Size
timbru31~docker-java-node~0IPJFH.dockerbuild
13.6 KB
timbru31~docker-java-node~2034KY.dockerbuild
39.5 KB
timbru31~docker-java-node~2YJ55Y.dockerbuild
14.2 KB
timbru31~docker-java-node~4B8Z36.dockerbuild
50.8 KB
timbru31~docker-java-node~5ZJ898.dockerbuild
171 KB
timbru31~docker-java-node~9TJMUB.dockerbuild
12.2 KB
timbru31~docker-java-node~AF1H7G.dockerbuild
12 KB
timbru31~docker-java-node~APB8VV.dockerbuild
39 KB
timbru31~docker-java-node~C2WOZ3.dockerbuild
12.6 KB
timbru31~docker-java-node~DZLAA7.dockerbuild
132 KB
timbru31~docker-java-node~E81G6R.dockerbuild
171 KB
timbru31~docker-java-node~F3RXFN.dockerbuild
38.6 KB
timbru31~docker-java-node~FKUHML.dockerbuild
14.6 KB
timbru31~docker-java-node~GAIV5P.dockerbuild
38.4 KB
timbru31~docker-java-node~GL6XQ8.dockerbuild
13.2 KB
timbru31~docker-java-node~GRXJRS.dockerbuild
50.3 KB
timbru31~docker-java-node~H05EBG.dockerbuild
14.4 KB
timbru31~docker-java-node~H2MZ6A.dockerbuild
12.7 KB
timbru31~docker-java-node~IM9KQH.dockerbuild
14.1 KB
timbru31~docker-java-node~IP8YGT.dockerbuild
135 KB
timbru31~docker-java-node~JDKW0N.dockerbuild
12.1 KB
timbru31~docker-java-node~KHM8OY.dockerbuild
104 KB
timbru31~docker-java-node~KK9821.dockerbuild
50.8 KB
timbru31~docker-java-node~LKC1B0.dockerbuild
105 KB
timbru31~docker-java-node~LKTU9M.dockerbuild
134 KB
timbru31~docker-java-node~LVIM7X.dockerbuild
14.5 KB
timbru31~docker-java-node~MIE6C8.dockerbuild
134 KB
timbru31~docker-java-node~MUMCGY.dockerbuild
50.8 KB
timbru31~docker-java-node~NK19SN.dockerbuild
134 KB
timbru31~docker-java-node~NUJXQA.dockerbuild
40 KB
timbru31~docker-java-node~NYT8HU.dockerbuild
103 KB
timbru31~docker-java-node~OFG24A.dockerbuild
18.5 KB
timbru31~docker-java-node~PZU0NH.dockerbuild
40.3 KB
timbru31~docker-java-node~QYC7HI.dockerbuild
39.3 KB
timbru31~docker-java-node~RA32R8.dockerbuild
104 KB
timbru31~docker-java-node~RCRTC2.dockerbuild
13.9 KB
timbru31~docker-java-node~S29IMZ.dockerbuild
13 KB
timbru31~docker-java-node~T4K8E2.dockerbuild
11.8 KB
timbru31~docker-java-node~TPAKHI.dockerbuild
170 KB
timbru31~docker-java-node~U067CU.dockerbuild
39 KB
timbru31~docker-java-node~U4FAMJ.dockerbuild
14.1 KB
timbru31~docker-java-node~WXD4HY.dockerbuild
39.3 KB
timbru31~docker-java-node~WXRUKV.dockerbuild
12.9 KB
timbru31~docker-java-node~X0NGVB.dockerbuild
104 KB
timbru31~docker-java-node~X5SVEH.dockerbuild
132 KB
timbru31~docker-java-node~YVPPWF.dockerbuild
50.8 KB
timbru31~docker-java-node~Z0PDON.dockerbuild
13.6 KB
timbru31~docker-java-node~Z2A55W.dockerbuild
49.9 KB