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

Automatic build on release and push to Docker Hub #972

Sign in to view logs

Automatic build on release and push to Docker Hub

Automatic build on release and push to Docker Hub #972

Triggered via push March 9, 2026 13:24
@dkorunicdkorunic
⁠ 0a88fcd
2.4.30
Status Failure
Total duration 34m 3s
Artifacts 2

docker_auto.yml

on: push
main
33m 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.4/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.4/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: 2.4/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.4/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.4/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.4/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/
Legacy key/value format with whitespace separator should not be used: 2.4/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/
Legacy key/value format with whitespace separator should not be used: 2.4/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.4/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.4/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/

Artifacts

Produced during runtime
Name Size Digest
haproxytech~haproxy-docker-debian~ARRX5B.dockerbuild
7.28 KB
sha256:5f0e3c1d21ce01ef2cb6f0021643843d8ba2823da89f49d97ace9a49d6ed1259
haproxytech~haproxy-docker-debian~H30M4N.dockerbuild
218 KB
sha256:afc72205b45025bb5d7c0eb052ce5f45e960623439ec5a26a093dc46ffc0527f