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

Automatic build on release and push to Docker Hub #875

Sign in to view logs

Automatic build on release and push to Docker Hub

Automatic build on release and push to Docker Hub #875

Triggered via push November 21, 2025 16:07
@dkorunicdkorunic
⁠ e3803ab
2.6.23
Status Failure
Total duration 41m 27s
Artifacts 2

docker_auto.yml

on: push
main
40m 36s
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
The MAINTAINER instruction is deprecated, use a label instead to define an image author: 2.6/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.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#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#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#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#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#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.6/Dockerfile#L28
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#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/

Artifacts

Produced during runtime
Name Size Digest
haproxytech~haproxy-docker-ubuntu~TJBOD9.dockerbuild
7.88 KB
sha256:7bf2cb014c1d3fb9f9c019f4c9485c2d1220f67640e1dd78d249cff0e37e0d43
haproxytech~haproxy-docker-ubuntu~ZAMTS0.dockerbuild
228 KB
sha256:a7522b7dd7ed250acb42d1ee2eeea7bde97abbb77155de28267bf5562d10a02d