Flowzone

Update ghcr.io/balena-io-modules/confd-releases Docker tag to v0.0.6 #1202

Sign in to view logs

Triggered via pull request November 18, 2024 20:48

balena-renovate[bot]

opened #378

renovate/ghcr.io-balena-io-modules-confd-releases-0.0.x

Status Success

Total duration 5m 21s

Artifacts 9

flowzone.yml

on: pull_request

Matrix: Flowzone / Event Types

Flowzone / Versioned source

Flowzone / Clean GitHub release

Flowzone / Is custom

Flowzone / Is rust

Flowzone / Is npm

Flowzone / Is python

Flowzone / Is docker

Flowzone / Generate release notes

Flowzone / Is balena

Flowzone / Is website

Flowzone / Is CloudFormation

Flowzone / Lint workflows

Matrix: Flowzone / Test custom

Matrix: Flowzone / Clean custom

Matrix: Flowzone / Finalize custom

Matrix: Flowzone / Test rust

Flowzone / Finalize rust

Matrix: Flowzone / Test npm

Flowzone / Finalize npm

Flowzone / Finalize npm docs

Matrix: Flowzone / Test python poetry

Flowzone / Finalize python

Matrix: Flowzone / Test docker

Matrix: Flowzone / Finalize docker

Flowzone / Prepare deploy message

Flowzone / Finalize GitHub release

Matrix: Flowzone / Finalize balena

Matrix: Flowzone / Test CloudFormation

Matrix: Flowzone / Finalize CloudFormation

Flowzone / Generate SBOM for cargo

Flowzone / Generate SBOM for NPM

Flowzone / Generate SBOM for python

Matrix: Flowzone / Publish custom

Matrix: Flowzone / Publish rust

Flowzone / Publish npm

Flowzone / Publish to test PyPI

Matrix: Flowzone / Publish balena

Flowzone / Publish website

Matrix: Flowzone / Publish docker

Flowzone / All tests

Matrix: Flowzone / Always custom

Flowzone / Publish Github release

Flowzone / All jobs

Flowzone / Auto-merge

Annotations

14 warnings

Legacy key/value format with whitespace separator should not be used: Dockerfile.no-systemd#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: Dockerfile.no-systemd#L6

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.no-systemd#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: Dockerfile.no-systemd#L6

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#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: Dockerfile#L6

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#L80

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#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: Dockerfile#L6

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#L80

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/

Flowzone / Publish docker (docker.io/balena/open-balena-base, no-systemd, no-systemd, amd64 arm64v8)

gpg: key "FB5DB77FD5C118B80511ADA8A6310ACC4672475C" not found gpg: FB5DB77FD5C118B80511ADA8A6310ACC4672475C: delete key failed: Not found

Flowzone / Publish docker (docker.io/balena/open-balena-base, no-systemd, no-systemd, amd64 arm64v8)

Publishing Docker images without docker compose tests!

Flowzone / Publish docker (docker.io/balena/open-balena-base, default, default, amd64 arm64v8)

gpg: key "FB5DB77FD5C118B80511ADA8A6310ACC4672475C" not found gpg: FB5DB77FD5C118B80511ADA8A6310ACC4672475C: delete key failed: Not found

Flowzone / Publish docker (docker.io/balena/open-balena-base, default, default, amd64 arm64v8)

Publishing Docker images without docker compose tests!

Artifacts

Produced during runtime

Name	Size
balena-io-modules~open-balena-base~AL4DIZ.dockerbuild	49.4 KB
balena-io-modules~open-balena-base~GZ07I3.dockerbuild	49.9 KB
balena-io-modules~open-balena-base~ORIWV4.dockerbuild	79.8 KB
balena-io-modules~open-balena-base~T694A6.dockerbuild	80.1 KB
docker-default-amd64 Expired	247 MB
docker-default-arm64v8 Expired	241 MB
docker-no-systemd-amd64 Expired	109 MB
docker-no-systemd-arm64v8 Expired	107 MB
release-notes Expired	236 Bytes