Skip to content

ci

ci #252

Triggered via schedule November 13, 2023 10:02
Status Success
Total duration 2m 4s
Artifacts

ci.yml

on: schedule
minimal
13s
minimal
git-context
15s
git-context
git-context-secret
20s
git-context-secret
path-context
21s
path-context
example
26s
example
error
7s
error
error-buildx
20s
error-buildx
docker-driver
12s
docker-driver
export-docker
8s
export-docker
secret
8s
secret
secret-envs
20s
secret-envs
network
23s
network
shm-size
18s
shm-size
ulimit
10s
ulimit
cgroup-parent
14s
cgroup-parent
add-hosts
18s
add-hosts
no-cache-filters
11s
no-cache-filters
registry-cache
34s
registry-cache
github-cache
37s
github-cache
standalone
18s
standalone
named-context-pin
10s
named-context-pin
named-context-docker
20s
named-context-docker
named-context-container
1m 8s
named-context-container
docker-config-malformed
9s
docker-config-malformed
proxy-docker-config
27s
proxy-docker-config
proxy-buildkitd
30s
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:3f85c135e959731f30489b3af95ba3e26cdffbe8864c72c76ebc70df52749a81": dial tcp 127.0.0.1:5000: connect: connection refused
secret
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-envs
INVALID_SECRET= is not a valid secret