Skip to content

ci

ci #1327

Triggered via schedule November 4, 2023 10:03
Status Success
Total duration 58s
Artifacts

ci.yml

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

Annotations

2 errors and 3 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:93180bf38a98062d8f3858c7a1bc2460e2eb5314e2198e90d79729fcacad09a6": dial tcp 127.0.0.1:5000: connect: connection refused
secret-envs
INVALID_SECRET= is not a valid secret
docker-config-malformed
Unable to parse config file /home/runner/.docker/config.json: SyntaxError: Unexpected non-whitespace character after JSON at position 139
secret
INVALID_SECRET= is not a valid secret