Skip to content

ci

ci #1328

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

ci.yml

on: schedule
minimal
16s
minimal
git-context
19s
git-context
git-context-secret
16s
git-context-secret
path-context
13s
path-context
example
15s
example
error
7s
error
error-buildx
15s
error-buildx
docker-driver
18s
docker-driver
export-docker
9s
export-docker
secret
17s
secret
secret-envs
10s
secret-envs
network
22s
network
shm-size
8s
shm-size
ulimit
25s
ulimit
cgroup-parent
18s
cgroup-parent
add-hosts
8s
add-hosts
no-cache-filters
15s
no-cache-filters
registry-cache
33s
registry-cache
github-cache
1m 43s
github-cache
standalone
12s
standalone
named-context-pin
15s
named-context-pin
named-context-docker
22s
named-context-docker
named-context-container
20s
named-context-container
docker-config-malformed
11s
docker-config-malformed
proxy-docker-config
27s
proxy-docker-config
proxy-buildkitd
27s
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:072e0cf488f0945b842ab61ebead2a1ad91a13da2093bcad6d07c4331d3fcea6": 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