Skip to content

ci

ci #1437

Triggered via schedule January 31, 2024 10:03
Status Success
Total duration 58s
Artifacts

ci.yml

on: schedule
minimal
10s
minimal
git-context
24s
git-context
git-context-secret
35s
git-context-secret
path-context
22s
path-context
example
13s
example
error
7s
error
error-buildx
21s
error-buildx
docker-driver
12s
docker-driver
export-docker
7s
export-docker
secret
22s
secret
secret-envs
7s
secret-envs
network
19s
network
shm-size
14s
shm-size
ulimit
7s
ulimit
cgroup-parent
13s
cgroup-parent
add-hosts
18s
add-hosts
no-cache-filters
19s
no-cache-filters
registry-cache
31s
registry-cache
github-cache
12s
github-cache
standalone
13s
standalone
named-context-pin
20s
named-context-pin
named-context-docker
10s
named-context-docker
named-context-container
20s
named-context-container
docker-config-malformed
8s
docker-config-malformed
proxy-docker-config
22s
proxy-docker-config
proxy-buildkitd
20s
proxy-buildkitd
annotations
18s
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:349846702c2e587c5795c88a078474a04762355b3471e47804c575d0715c33ee": 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