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

Automatic build on release and push to Docker Hub #907

Sign in to view logs

Automatic build on release and push to Docker Hub

Automatic build on release and push to Docker Hub #907

Triggered via push December 22, 2025 20:07
@dkorunicdkorunic
⁠ 4d418cd
2.4.30
Status Failure
Total duration 26m 57s
Artifacts 2

docker_auto.yml

on: push
main
26m 53s
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#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#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.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#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.4/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.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#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#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.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#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-ubuntu~SGERH1.dockerbuild
7.77 KB
sha256:79678e71beb7dca13fabb6ab51c6df0ebea9ff8f1d6fbae5eb0e3f5e549b6b11
haproxytech~haproxy-docker-ubuntu~SYPEG0.dockerbuild
220 KB
sha256:1bb36134f9d5f57017503aa5a03f34e15e21b10e61265e8cd55b9b1bee767b6f