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

Automatic build on release and push to Docker Hub #908

Sign in to view logs

Automatic build on release and push to Docker Hub

Automatic build on release and push to Docker Hub #908

Triggered via push December 22, 2025 20:07
@dkorunicdkorunic
⁠ acdf3c6
2.6.23
Status Failure
Total duration 27m 9s
Artifacts 2

docker_auto.yml

on: push
main
25m 59s
main
Fit to window
Zoom out
Zoom in

Annotations

1 error and 10 warnings
main
buildx failed with: ERROR: failed to build: failed to solve: failed to read dockerfile: open Dockerfile.api: no such file or directory
Legacy key/value format with whitespace separator should not be used: 2.6/Dockerfile#L26
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.6/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.6/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.6/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.6/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/
Legacy key/value format with whitespace separator should not be used: 2.6/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.6/Dockerfile#L34
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.6/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.6/Dockerfile#L20
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.6/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 Digest
haproxytech~haproxy-docker-ubuntu~CHRCWQ.dockerbuild
224 KB
sha256:a504ff219d02b49636ba481f62fd10b39b19cf1046237ecb458f74eb31aad519
haproxytech~haproxy-docker-ubuntu~Z7HI45.dockerbuild
7.32 KB
sha256:1bc24c193f66cfe0d198816ea09bbf704414c2b63ad9a8bd1f4a49246cd9e54b