Skip to content

ci

ci #310

Triggered via schedule January 8, 2024 10:02
Status Success
Total duration 1m 39s
Artifacts

ci.yml

on: schedule
minimal
26s
minimal
git-context
26s
git-context
git-context-secret
27s
git-context-secret
path-context
12s
path-context
example
25s
example
error
6s
error
error-buildx
14s
error-buildx
docker-driver
7s
docker-driver
export-docker
6s
export-docker
secret
13s
secret
secret-envs
13s
secret-envs
network
8s
network
shm-size
13s
shm-size
ulimit
9s
ulimit
cgroup-parent
11s
cgroup-parent
add-hosts
7s
add-hosts
no-cache-filters
15s
no-cache-filters
registry-cache
20s
registry-cache
github-cache
22s
github-cache
standalone
14s
standalone
named-context-pin
23s
named-context-pin
named-context-docker
19s
named-context-docker
named-context-container
12s
named-context-container
docker-config-malformed
7s
docker-config-malformed
proxy-docker-config
14s
proxy-docker-config
proxy-buildkitd
17s
proxy-buildkitd
annotations
25s
annotations
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:4ba2d4bcf1d79c6acf909a4b82c8d4b4851377c7219aecfffe5835d0b6f1f1f6": dial tcp 127.0.0.1:5000: connect: connection refused
secret-envs
INVALID_SECRET= is not a valid secret
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