Skip to content
Automatic build on release and push to Docker Hub

Automatic build on release and push to Docker Hub #798

Sign in to view logs

Automatic build on release and push to Docker Hub

Automatic build on release and push to Docker Hub #798

Triggered via push March 28, 2025 13:09
@dkorunicdkorunic
⁠ 09d0f63
2.9.15
Status Success
Total duration 1h 36m 28s
Artifacts 1

docker_auto.yml

on: push
main
1h 36m
main
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
Legacy key/value format with whitespace separator should not be used: 2.9/Dockerfile#L24
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: 2.9/Dockerfile#L31
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/
The MAINTAINER instruction is deprecated, use a label instead to define an image author: 2.9/Dockerfile#L18
MaintainerDeprecated: Maintainer instruction is deprecated in favor of using label More info: https://docs.docker.com/go/dockerfile/rule/maintainer-deprecated/
Legacy key/value format with whitespace separator should not be used: 2.9/Dockerfile#L21
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: 2.9/Dockerfile#L22
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: 2.9/Dockerfile#L23
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: 2.9/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: 2.9/Dockerfile#L29
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: 2.9/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: 2.9/Dockerfile#L4
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
haproxytech~haproxy-docker-alpine~CQ5FWS.dockerbuild Expired
232 KB
sha256:4628fc5323d373f22906398d21f8b9c2f3141e3a7dc95e920bfec7c7c56dd28e