Skip to content

ci

ci #1342

Triggered via schedule November 16, 2023 10:03
Status Success
Total duration 58s
Artifacts

ci.yml

on: schedule
minimal
18s
minimal
git-context
32s
git-context
git-context-secret
27s
git-context-secret
path-context
21s
path-context
example
21s
example
error
7s
error
error-buildx
14s
error-buildx
docker-driver
14s
docker-driver
export-docker
7s
export-docker
secret
8s
secret
secret-envs
17s
secret-envs
network
11s
network
shm-size
8s
shm-size
ulimit
13s
ulimit
cgroup-parent
15s
cgroup-parent
add-hosts
18s
add-hosts
no-cache-filters
18s
no-cache-filters
registry-cache
17s
registry-cache
github-cache
13s
github-cache
standalone
9s
standalone
named-context-pin
9s
named-context-pin
named-context-docker
13s
named-context-docker
named-context-container
21s
named-context-container
docker-config-malformed
9s
docker-config-malformed
proxy-docker-config
21s
proxy-docker-config
proxy-buildkitd
16s
proxy-buildkitd
annotations
11s
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:408e632b3dfdbbbd67ac85290c74f2e5cdc91a692a73a7637c6484a63e56bbbe": 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