Skip to content

ci

ci #242

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

ci.yml

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