build: move automated job later #2067
Annotations
38 errors and 126 warnings
buildx (8, jdk, 20, alpine)
Process completed with exit code 1.
|
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 (17, jdk, 20, default)
Process completed with exit code 1.
|
buildx (17, jdk, 22, default)
Process completed with exit code 1.
|
buildx (17, jdk, 18, default)
Process completed with exit code 1.
|
buildx (17, jre, 18, default)
Process completed with exit code 1.
|
buildx (11, jdk, 20, default)
Process completed with exit code 1.
|
buildx (11, jdk, 18, default)
Process completed with exit code 1.
|
buildx (11, jre, 18, default)
Process completed with exit code 1.
|
buildx (11, jdk, 22, 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 (17, jre, 22, default)
Process completed with exit code 1.
|
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: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, 22, alpine)
Process completed with exit code 1.
|
buildx (17, jre, 20, default)
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, 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, 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, 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, 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 (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, 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 (21, jdk, 18, default)
Process completed with exit code 1.
|
buildx (21, jdk, 20, default)
Process completed with exit code 1.
|
buildx (21, jdk, 22, default)
Process completed with exit code 1.
|
buildx (21, jre, 20, default)
Process completed with exit code 1.
|
buildx (21, jre, 18, default)
Process completed with exit code 1.
|
buildx (21, jre, 22, default)
Process completed with exit code 1.
|
buildx (8, jdk, 18, default)
Process completed with exit code 1.
|
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, 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 (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#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/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 (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 (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#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:
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/
|
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 (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, 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 (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 (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 (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, 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 (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
|
Legacy key/value format with whitespace separator should not be used:
21/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:
21/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 (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
|
Legacy key/value format with whitespace separator should not be used:
21/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/
|
Legacy key/value format with whitespace separator should not be used:
21/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/
|
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
|
Legacy key/value format with whitespace separator should not be used:
21/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:
21/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 (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
|
Legacy key/value format with whitespace separator should not be used:
8/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:
8/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 (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
|
Legacy key/value format with whitespace separator should not be used:
8/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:
8/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 (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 (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 (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, 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, 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 (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#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/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/
|
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 (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 (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/
|
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 (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 (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 (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 (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, 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, 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, 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, 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, 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, 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 (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 (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
|
Legacy key/value format with whitespace separator should not be used:
21/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:
21/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 (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
|
Legacy key/value format with whitespace separator should not be used:
21/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:
21/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 (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
|
Legacy key/value format with whitespace separator should not be used:
21/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:
21/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 (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
|
Legacy key/value format with whitespace separator should not be used:
21/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:
21/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 (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
|
Legacy key/value format with whitespace separator should not be used:
8/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:
8/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/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
timbru31~docker-java-node~1CQCVG.dockerbuild
|
50.3 KB |
|
timbru31~docker-java-node~1IHOD6.dockerbuild
|
50.2 KB |
|
timbru31~docker-java-node~1L1T10.dockerbuild
|
50.1 KB |
|
timbru31~docker-java-node~2EDBON.dockerbuild
|
12.6 KB |
|
timbru31~docker-java-node~3SG24F.dockerbuild
|
40.3 KB |
|
timbru31~docker-java-node~3Z4NQA.dockerbuild
|
39.2 KB |
|
timbru31~docker-java-node~6AIDPC.dockerbuild
|
14.7 KB |
|
timbru31~docker-java-node~920LX6.dockerbuild
|
51.1 KB |
|
timbru31~docker-java-node~940NJ6.dockerbuild
|
170 KB |
|
timbru31~docker-java-node~9R8Y1Y.dockerbuild
|
38.4 KB |
|
timbru31~docker-java-node~BCC8LH.dockerbuild
|
14.3 KB |
|
timbru31~docker-java-node~BPX5NF.dockerbuild
|
133 KB |
|
timbru31~docker-java-node~IN2GDR.dockerbuild
|
40.1 KB |
|
timbru31~docker-java-node~IRJMRT.dockerbuild
|
134 KB |
|
timbru31~docker-java-node~ISPBQH.dockerbuild
|
132 KB |
|
timbru31~docker-java-node~K1BPTK.dockerbuild
|
134 KB |
|
timbru31~docker-java-node~KOS11H.dockerbuild
|
40.2 KB |
|
timbru31~docker-java-node~KUWEJ6.dockerbuild
|
50.9 KB |
|
timbru31~docker-java-node~KVJ174.dockerbuild
|
50.1 KB |
|
timbru31~docker-java-node~NIUVUY.dockerbuild
|
134 KB |
|
timbru31~docker-java-node~NULNIU.dockerbuild
|
133 KB |
|
timbru31~docker-java-node~O2R1G4.dockerbuild
|
50.1 KB |
|
timbru31~docker-java-node~O6YDD9.dockerbuild
|
106 KB |
|
timbru31~docker-java-node~OL3XP4.dockerbuild
|
39.9 KB |
|
timbru31~docker-java-node~ORVTQD.dockerbuild
|
134 KB |
|
timbru31~docker-java-node~PHGHFP.dockerbuild
|
12.9 KB |
|
timbru31~docker-java-node~PM7QWC.dockerbuild
|
170 KB |
|
timbru31~docker-java-node~PXNX1H.dockerbuild
|
51.4 KB |
|
timbru31~docker-java-node~QKXNW1.dockerbuild
|
14.7 KB |
|
timbru31~docker-java-node~R1F7KY.dockerbuild
|
132 KB |
|
timbru31~docker-java-node~R9ORRL.dockerbuild
|
50 KB |
|
timbru31~docker-java-node~REPYBS.dockerbuild
|
39.4 KB |
|
timbru31~docker-java-node~RG3EQ8.dockerbuild
|
12 KB |
|
timbru31~docker-java-node~RODV74.dockerbuild
|
38.5 KB |
|
timbru31~docker-java-node~RWHNDE.dockerbuild
|
12.9 KB |
|
timbru31~docker-java-node~RXO8GM.dockerbuild
|
135 KB |
|
timbru31~docker-java-node~T8L7II.dockerbuild
|
106 KB |
|
timbru31~docker-java-node~U6VH37.dockerbuild
|
39.7 KB |
|
timbru31~docker-java-node~U7XM53.dockerbuild
|
105 KB |
|
timbru31~docker-java-node~V2P6K5.dockerbuild
|
37.7 KB |
|
timbru31~docker-java-node~W826H6.dockerbuild
|
103 KB |
|
timbru31~docker-java-node~WADR6M.dockerbuild
|
38 KB |
|
timbru31~docker-java-node~XDENTV.dockerbuild
|
172 KB |
|
timbru31~docker-java-node~XF9B9B.dockerbuild
|
105 KB |
|
timbru31~docker-java-node~XS45A2.dockerbuild
|
104 KB |
|
timbru31~docker-java-node~ZBTMNS.dockerbuild
|
14.6 KB |
|
timbru31~docker-java-node~ZJIMHO.dockerbuild
|
13.9 KB |
|
timbru31~docker-java-node~ZQ83A3.dockerbuild
|
104 KB |
|