Skip to content
Triggered via schedule April 27, 2023 10:03
Status Failure
Total duration 57s
Artifacts

ci.yml

on: schedule
minimal
20s
minimal
git-context
18s
git-context
git-context-secret
22s
git-context-secret
path-context
21s
path-context
example
30s
example
error
7s
error
error-buildx
31s
error-buildx
docker-driver
13s
docker-driver
export-docker
5s
export-docker
secret
11s
secret
network
15s
network
shm-size
11s
shm-size
ulimit
11s
ulimit
cgroup-parent
12s
cgroup-parent
add-hosts
17s
add-hosts
no-cache-filters
22s
no-cache-filters
registry-cache
23s
registry-cache
github-cache
19s
github-cache
standalone
14s
standalone
named-context-pin
16s
named-context-pin
named-context-docker
5s
named-context-docker
named-context-container
17s
named-context-container
Matrix: attests-compat
Matrix: digest
Matrix: multi
Matrix: provenance
Matrix: sbom
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
error
buildx failed with: ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
named-context-docker
write EPROTO 139882260658112:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac:../deps/openssl/openssl/ssl/record/ssl3_record.c:677:
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:60b4d3dc2addf4c8bd3eb9b27c30950d88bd757f0dbd532609aeaba429595c03": dial tcp 127.0.0.1:5000: connect: connection refused
secret
INVALID_SECRET= is not a valid secret