chore(deps): Bump @docker/actions-toolkit from 0.20.0 to 0.22.0 #1567
crazy-maxci.yml
on: pull_request
minimal
11s
git-context
16s
git-context-secret
16s
path-context
17s
example
14s
error
5s
error-buildx
18s
docker-driver
8s
export-docker
12s
secret
18s
secret-envs
11s
network
12s
shm-size
15s
ulimit
10s
cgroup-parent
11s
add-hosts
10s
no-cache-filters
10s
registry-cache
25s
github-cache
15s
local-cache
23s
standalone
12s
named-context-pin
18s
named-context-docker
15s
named-context-container
22s
docker-config-malformed
10s
proxy-docker-config
17s
proxy-buildkitd
26s
annotations
30s
multi-output
19s
load-and-push
15s
Matrix: attests-compat
Matrix: digest
Matrix: multi
Matrix: provenance
Matrix: sbom
Annotations
2 errors and 4 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:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1": 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
|
|
attests-compat (v0.9.1, moby/buildkit:buildx-stable-1)
Attestations are only supported by buildx >= 0.10.0; the inputs 'attests', 'provenance' and 'sbom' are ignored.
|