Skip to content

ci

ci #668

Triggered via schedule November 14, 2024 10:03
Status Success
Total duration 2m 57s
Artifacts 51

ci.yml

on: schedule
minimal
24s
minimal
git-context
37s
git-context
git-context-secret
46s
git-context-secret
path-context
21s
path-context
example
23s
example
error
4s
error
error-buildx
30s
error-buildx
docker-driver
15s
docker-driver
export-docker
19s
export-docker
secret
23s
secret
secret-envs
26s
secret-envs
network
13s
network
shm-size
15s
shm-size
ulimit
17s
ulimit
cgroup-parent
16s
cgroup-parent
add-hosts
15s
add-hosts
no-cache-filters
15s
no-cache-filters
registry-cache
31s
registry-cache
github-cache
18s
github-cache
local-cache
45s
local-cache
standalone
11s
standalone
named-context-pin
16s
named-context-pin
named-context-docker
20s
named-context-docker
named-context-container
22s
named-context-container
docker-config-malformed
16s
docker-config-malformed
proxy-docker-config
21s
proxy-docker-config
proxy-buildkitd
29s
proxy-buildkitd
annotations
16s
annotations
multi-output
24s
multi-output
load-and-push
29s
load-and-push
summary-disable
23s
summary-disable
summary-disable-deprecated
20s
summary-disable-deprecated
summary-not-supported
20s
summary-not-supported
record-upload-disable
27s
record-upload-disable
annotations-disabled
12s
annotations-disabled
Matrix: attests-compat
Matrix: checks
Matrix: digest
Matrix: multi
Matrix: provenance
Matrix: record-retention-days
Matrix: sbom
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 14 warnings
error
buildx failed with: ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
error-buildx
buildx failed with: ERROR: failed to solve: failed to push localhost:5000/name/app:latest: failed to do request: Head "http://localhost:5000/v2/name/app/blobs/sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1": dial tcp [::1]:5000: connect: connection refused
secret
INVALID_SECRET= is not a valid secret
secret-envs
INVALID_SECRET= is not a valid secret
The MAINTAINER instruction is deprecated, use a label instead to define an image author: test/lint.Dockerfile#L5
MaintainerDeprecated: Maintainer instruction is deprecated in favor of using label More info: https://docs.docker.com/go/dockerfile/rule/maintainer-deprecated/
All commands within the Dockerfile should use the same casing (either upper or lower): test/lint.Dockerfile#L1
ConsistentInstructionCasing: Command 'frOM' should match the case of the command majority (uppercase) More info: https://docs.docker.com/go/dockerfile/rule/consistent-instruction-casing/
All commands within the Dockerfile should use the same casing (either upper or lower): test/lint.Dockerfile#L2
ConsistentInstructionCasing: Command 'cOpy' should match the case of the command majority (uppercase) More info: https://docs.docker.com/go/dockerfile/rule/consistent-instruction-casing/
All commands within the Dockerfile should use the same casing (either upper or lower): test/lint.Dockerfile#L4
ConsistentInstructionCasing: Command 'from' should match the case of the command majority (uppercase) More info: https://docs.docker.com/go/dockerfile/rule/consistent-instruction-casing/
All commands within the Dockerfile should use the same casing (either upper or lower): test/lint.Dockerfile#L6
ConsistentInstructionCasing: Command 'COPy' should match the case of the command majority (uppercase) More info: https://docs.docker.com/go/dockerfile/rule/consistent-instruction-casing/
Multiple instructions of the same type should not be used in the same stage: test/lint.Dockerfile#L10
MultipleInstructionsDisallowed: Multiple CMD instructions should not be used in the same stage because only the last one will be used More info: https://docs.docker.com/go/dockerfile/rule/multiple-instructions-disallowed/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: test/lint.Dockerfile#L12
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
attests-compat (latest, moby/buildkit:v0.10.6)
Process "docker run" closed with code 1
docker-config-malformed
Unable to parse config file /home/runner/.docker/config.json: SyntaxError: Unexpected non-whitespace character after JSON at position 139
attests-compat (v0.9.1, moby/buildkit:buildx-stable-1)
Attestations are only supported by buildx >= 0.10.0; the inputs 'attests', 'provenance' and 'sbom' are ignored.
standalone
Docker is required to export a build record
summary-disable-deprecated
DOCKER_BUILD_NO_SUMMARY is deprecated. Set DOCKER_BUILD_SUMMARY to false instead.

Artifacts

Produced during runtime
Name Size
crazy-max~docker-build-push-action~09EHC9.dockerbuild
18.4 KB
crazy-max~docker-build-push-action~2YQEA2.dockerbuild
44.3 KB
crazy-max~docker-build-push-action~3IES7Z.dockerbuild
17.1 KB
crazy-max~docker-build-push-action~49YRFQ.dockerbuild
25.8 KB
crazy-max~docker-build-push-action~4NW15I.dockerbuild Expired
18.4 KB
crazy-max~docker-build-push-action~5KDSLD.dockerbuild
23.4 KB
crazy-max~docker-build-push-action~5LVBAN.dockerbuild
24.5 KB
crazy-max~docker-build-push-action~769T3C.dockerbuild
17.3 KB
crazy-max~docker-build-push-action~8A9DYK.dockerbuild
23.8 KB
crazy-max~docker-build-push-action~DAW87L.dockerbuild
17 KB
crazy-max~docker-build-push-action~E1R681.dockerbuild
40.3 KB
crazy-max~docker-build-push-action~EPP59L.dockerbuild
29.5 KB
crazy-max~docker-build-push-action~FIHQ28.dockerbuild
39.8 KB
crazy-max~docker-build-push-action~GKP841.dockerbuild
11.9 KB
crazy-max~docker-build-push-action~H4CFE1.dockerbuild
28.6 KB
crazy-max~docker-build-push-action~H8CM16.dockerbuild
18.6 KB
crazy-max~docker-build-push-action~HQ5RHH.dockerbuild
17.4 KB
crazy-max~docker-build-push-action~HWGPJ9.dockerbuild
26.5 KB
crazy-max~docker-build-push-action~HXBLUJ.dockerbuild
36.1 KB
crazy-max~docker-build-push-action~I59GQK.dockerbuild
39 KB
crazy-max~docker-build-push-action~I5EZK9.dockerbuild
36.3 KB
crazy-max~docker-build-push-action~ICKH4X.dockerbuild
44.4 KB
crazy-max~docker-build-push-action~KAF8YT.dockerbuild
14.8 KB
crazy-max~docker-build-push-action~KUA2TZ.dockerbuild
16.9 KB
crazy-max~docker-build-push-action~LF4Z1Q.dockerbuild
17.4 KB
crazy-max~docker-build-push-action~LQ99S1.dockerbuild
17.1 KB
crazy-max~docker-build-push-action~LRWD29.dockerbuild
14 KB
crazy-max~docker-build-push-action~MWZHUW.dockerbuild
17.2 KB
crazy-max~docker-build-push-action~MZIUHB.dockerbuild
28.6 KB
crazy-max~docker-build-push-action~NDSBSP.dockerbuild
14.2 KB
crazy-max~docker-build-push-action~NNR3RB.dockerbuild
17.3 KB
crazy-max~docker-build-push-action~NQE2M7.dockerbuild
50.3 KB
crazy-max~docker-build-push-action~O58RRU.dockerbuild
48.5 KB
crazy-max~docker-build-push-action~OAO842.dockerbuild
16.7 KB
crazy-max~docker-build-push-action~P4OI2W.dockerbuild
17.4 KB
crazy-max~docker-build-push-action~QA2X6H.dockerbuild
41.3 KB
crazy-max~docker-build-push-action~QAMSGM.dockerbuild
17.3 KB
crazy-max~docker-build-push-action~ROE4BI.dockerbuild
24.1 KB
crazy-max~docker-build-push-action~SFF48W.dockerbuild
17.3 KB
crazy-max~docker-build-push-action~SGEK2E.dockerbuild
25.6 KB
crazy-max~docker-build-push-action~U1W767.dockerbuild
18.5 KB
crazy-max~docker-build-push-action~UE6EL9.dockerbuild
25.7 KB
crazy-max~docker-build-push-action~UH506U.dockerbuild
17.3 KB
crazy-max~docker-build-push-action~V6BD29.dockerbuild
17.3 KB
crazy-max~docker-build-push-action~VMF3H3.dockerbuild
23 KB
crazy-max~docker-build-push-action~VQZ9JY.dockerbuild
16.9 KB
crazy-max~docker-build-push-action~VX1LNN.dockerbuild
16.9 KB
crazy-max~docker-build-push-action~WFSCZP.dockerbuild
18.6 KB
crazy-max~docker-build-push-action~X6BKH1.dockerbuild
25.5 KB
crazy-max~docker-build-push-action~YOI3I7.dockerbuild
14.8 KB
crazy-max~docker-build-push-action~ZY5G5H.dockerbuild
52.1 KB