Dockerfile Builder #5102
Triggered via workflow run
December 6, 2024 06:58
github-merge-queue[bot]
completed
caca439
Status
Success
Total duration
4m 5s
Artifacts
5
Annotations
11 warnings
build-and-publish (mrtnzlml-meta)
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:
src/mrtnzlml-meta/Dockerfile#L27
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/
|
build-and-publish (abacus-tools)
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:
src/abacus-tools/Dockerfile#L20
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/
|
build-and-publish (abacus-kochka)
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:
src/abacus-kochka/Dockerfile#L22
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/
|
build-and-publish (abacus-backoffice)
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:
src/abacus-backoffice/Dockerfile#L22
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/
|
build-and-publish (abacus)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Relative workdir without an absolute workdir declared within the build can have unexpected results if the base image changes:
src/abacus/Dockerfile#L5
WorkdirRelativePath: Relative workdir "app" can have unexpected results if the base image changes
More info: https://docs.docker.com/go/dockerfile/rule/workdir-relative-path/
|
Relative workdir without an absolute workdir declared within the build can have unexpected results if the base image changes:
src/abacus/Dockerfile#L13
WorkdirRelativePath: Relative workdir "app" can have unexpected results if the base image changes
More info: https://docs.docker.com/go/dockerfile/rule/workdir-relative-path/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
adeira~universe~FJLKAN.dockerbuild
|
62.7 KB |
|
adeira~universe~KGRX8A.dockerbuild
|
63 KB |
|
adeira~universe~M8OE7E.dockerbuild
|
56.1 KB |
|
adeira~universe~OTXIOG.dockerbuild
|
60 KB |
|
adeira~universe~WJRRJ7.dockerbuild
|
66.8 KB |
|