Skip to content
Create and publish Docker images

Merge branch 'enricoros:v2-dev' into v2-dev #1

Sign in to view logs

Merge branch 'enricoros:v2-dev' into v2-dev

Merge branch 'enricoros:v2-dev' into v2-dev #1

Triggered via push December 17, 2024 08:28
@darthalex2014darthalex2014
pushed 04d009c
v2-dev
Status Success
Total duration 16m 51s
Artifacts 1

docker-image.yml

on: push
build-and-push-image
16m 42s
build-and-push-image
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
build-and-push-image
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: Dockerfile#L3
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: Dockerfile#L15
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: Dockerfile#L32
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: Dockerfile#L54
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: Dockerfile#L55
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
darthalex2014~1-16-0~OID6UR.dockerbuild
90.1 KB