Skip to content

Automatic build on release and push to Docker Hub #874

Automatic build on release and push to Docker Hub

Automatic build on release and push to Docker Hub #874

Triggered via push November 21, 2025 16:07
Status Failure
Total duration 42m 57s
Artifacts 2

docker_auto.yml

on: push
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#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#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#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#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#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#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/
The MAINTAINER instruction is deprecated, use a label instead to define an image author: 2.4/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.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#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.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/

Artifacts

Produced during runtime
Name Size Digest
haproxytech~haproxy-docker-ubuntu~DVV710.dockerbuild
7.1 KB
sha256:1173a7bdb727a27cf50391471d4c42c4b49a19ed78f6f6e29c19abc5d02faa60
haproxytech~haproxy-docker-ubuntu~EZ1WEQ.dockerbuild
225 KB
sha256:ab7efac68cf4f7ff76257c6926c9ca805a37af1d725bbd3d920a1d4514639c96