Skip to content
ci

display proxy configuration #1042

Sign in to view logs

display proxy configuration

display proxy configuration #1042

Triggered via pull request June 5, 2023 10:02
@crazy-maxcrazy-max
synchronize #872
crazy-max:ci-proxy
Status Failure
Total duration 1m 26s
Artifacts –

ci.yml

on: pull_request
minimal
18s
minimal
git-context
24s
git-context
git-context-secret
18s
git-context-secret
path-context
15s
path-context
example
19s
example
error
4s
error
error-buildx
19s
error-buildx
docker-driver
11s
docker-driver
export-docker
9s
export-docker
secret
12s
secret
network
18s
network
shm-size
8s
shm-size
ulimit
12s
ulimit
cgroup-parent
8s
cgroup-parent
add-hosts
13s
add-hosts
no-cache-filters
16s
no-cache-filters
registry-cache
21s
registry-cache
github-cache
25s
github-cache
standalone
12s
standalone
named-context-pin
12s
named-context-pin
named-context-docker
18s
named-context-docker
named-context-container
16s
named-context-container
proxy-docker-config
18s
proxy-docker-config
proxy-buildkitd
17s
proxy-buildkitd
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?
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:015ee8d9fb3dca1b18815f1e4ee0d325d1f40cde6f2df4dd307918f7b69167d7": dial tcp 127.0.0.1:5000: connect: connection refused
proxy-buildkitd
buildx failed with: ERROR: failed to solve: process "/bin/sh -c printenv HTTP_PROXY" did not complete successfully: exit code: 1
secret
INVALID_SECRET= is not a valid secret