Skip to content

ci

ci #263

Triggered via schedule November 22, 2023 10:02
Status Success
Total duration 1m 54s
Artifacts

ci.yml

on: schedule
minimal
13s
minimal
git-context
17s
git-context
git-context-secret
23s
git-context-secret
path-context
21s
path-context
example
15s
example
error
4s
error
error-buildx
21s
error-buildx
docker-driver
7s
docker-driver
export-docker
5s
export-docker
secret
14s
secret
secret-envs
15s
secret-envs
network
8s
network
shm-size
17s
shm-size
ulimit
14s
ulimit
cgroup-parent
9s
cgroup-parent
add-hosts
11s
add-hosts
no-cache-filters
24s
no-cache-filters
registry-cache
18s
registry-cache
github-cache
20s
github-cache
standalone
14s
standalone
named-context-pin
9s
named-context-pin
named-context-docker
13s
named-context-docker
named-context-container
14s
named-context-container
docker-config-malformed
7s
docker-config-malformed
proxy-docker-config
15s
proxy-docker-config
proxy-buildkitd
26s
proxy-buildkitd
annotations
15s
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:56ea5e69610a02d4dd2bdbd089434254c1303644215f24bf9d1c79ad2e151981": dial tcp 127.0.0.1:5000: connect: connection refused
secret
INVALID_SECRET= is not a valid secret
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