Skip to content

ci

ci #1332

Triggered via schedule November 9, 2023 10:03
Status Success
Total duration 1m 25s
Artifacts

ci.yml

on: schedule
minimal
13s
minimal
git-context
33s
git-context
git-context-secret
1m 8s
git-context-secret
path-context
23s
path-context
example
13s
example
error
5s
error
error-buildx
23s
error-buildx
docker-driver
14s
docker-driver
export-docker
12s
export-docker
secret
19s
secret
secret-envs
11s
secret-envs
network
11s
network
shm-size
15s
shm-size
ulimit
19s
ulimit
cgroup-parent
17s
cgroup-parent
add-hosts
11s
add-hosts
no-cache-filters
17s
no-cache-filters
registry-cache
22s
registry-cache
github-cache
25s
github-cache
standalone
11s
standalone
named-context-pin
21s
named-context-pin
named-context-docker
15s
named-context-docker
named-context-container
18s
named-context-container
docker-config-malformed
8s
docker-config-malformed
proxy-docker-config
26s
proxy-docker-config
proxy-buildkitd
17s
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:07cfa3903441f1927a158ad6b22e9fe8b4e7bc82776987ffe5aeecc414a5f7f4": 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