Skip to content
pcap-monitor-build-and-push-ghcr

bump arkime to v5.6.1 #508

Sign in to view logs

bump arkime to v5.6.1

bump arkime to v5.6.1 #508

Triggered via push February 13, 2025 22:38
@mmguerommguero
pushed 8463c0e
main
Status Failure
Total duration 1m 12s
Artifacts 1

pcap-monitor-build-and-push-ghcr.yml

on: push
Matrix: docker
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
docker (ubuntu-24.04, amd64, linux/amd64)
Cache not found for keys: trivy-binary-v0.57.1-Linux-X64
docker (ubuntu-24.04, amd64, linux/amd64)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Legacy key/value format with whitespace separator should not be used: Dockerfiles/pcap-monitor.Dockerfile#L16
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: Dockerfiles/pcap-monitor.Dockerfile#L17
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: Dockerfiles/pcap-monitor.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: Dockerfiles/pcap-monitor.Dockerfile#L41
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: Dockerfiles/pcap-monitor.Dockerfile#L42
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: Dockerfiles/pcap-monitor.Dockerfile#L102
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: Dockerfiles/pcap-monitor.Dockerfile#L15
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: Dockerfiles/pcap-monitor.Dockerfile#L22
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: Dockerfiles/pcap-monitor.Dockerfile#L39
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: Dockerfiles/pcap-monitor.Dockerfile#L43
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
mmguero-dev~Malcolm~LUOLI5.dockerbuild Expired
58.6 KB