Skip to content

ci

ci #1166

Triggered via schedule August 14, 2023 10:03
Status Success
Total duration 51s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

ci.yml

on: schedule
minimal
12s
minimal
git-context
29s
git-context
git-context-secret
17s
git-context-secret
path-context
23s
path-context
example
13s
example
error
4s
error
error-buildx
25s
error-buildx
docker-driver
9s
docker-driver
export-docker
7s
export-docker
secret
9s
secret
network
18s
network
shm-size
12s
shm-size
ulimit
16s
ulimit
cgroup-parent
10s
cgroup-parent
add-hosts
11s
add-hosts
no-cache-filters
18s
no-cache-filters
registry-cache
30s
registry-cache
github-cache
20s
github-cache
standalone
14s
standalone
named-context-pin
10s
named-context-pin
named-context-docker
17s
named-context-docker
named-context-container
21s
named-context-container
proxy-docker-config
15s
proxy-docker-config
proxy-buildkitd
24s
proxy-buildkitd
Matrix: attests-compat
Matrix: digest
Matrix: multi
Matrix: provenance
Matrix: sbom
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
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:6cb7db05a34d4050861cf4de7c06bbb39fe2c103db5c857165a279dab2602bf7": dial tcp 127.0.0.1:5000: connect: connection refused
secret
INVALID_SECRET= is not a valid secret