chore(deps): Bump @docker/actions-toolkit from 0.22.0 to 0.23.0 #1605
crazy-maxci.yml
on: pull_request
minimal
20s
git-context
28s
git-context-secret
24s
path-context
25s
example
14s
error
8s
error-buildx
17s
docker-driver
13s
export-docker
10s
secret
12s
secret-envs
12s
network
14s
shm-size
26s
ulimit
18s
cgroup-parent
11s
add-hosts
13s
no-cache-filters
11s
registry-cache
31s
github-cache
40s
local-cache
18s
standalone
17s
named-context-pin
11s
named-context-docker
14s
named-context-container
18s
docker-config-malformed
13s
proxy-docker-config
30s
proxy-buildkitd
21s
annotations
14s
multi-output
20s
load-and-push
21s
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:bca4290a96390d7a6fc6f2f9929370d06f8dfcacba591c76e3d5c5044e7f420c": 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.
|