Skip to content
Build and Push Container

Build and Push Container #65

Sign in to view logs

Build and Push Container

Build and Push Container #65

Manually triggered December 4, 2024 15:24
@ailoxailox
⁠ eb34049
main
Status Failure
Total duration 3m 57s
Artifacts 1

push.yml

on: workflow_dispatch
push-postgres
1m 48s
push-postgres
Matrix: push-service
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
push-service (opensight-keycloak-postgres, opensight/opensight-postgres, sha256:643ec75235fb32931...
Workflow run failed with conclusion failure ❌.
push-service (opensight-keycloak-postgres, opensight/opensight-postgres, sha256:643ec75235fb32931...
Process completed with exit code 1.
Legacy key/value format with whitespace separator should not be used: 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: 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: Dockerfile#L33
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: 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/

Artifacts

Produced during runtime
Name Size
greenbone~opensight-postgres~OIL886.dockerbuild Expired
68.6 KB