You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi folks,
we're using action-kaniko on some workflows, but recently one stopped working with the following message:
$/usr/bin/docker run --name a62b0ab75364e68e47cc90d5aa9e43fcc042_cf3c0a --label 39a62b (...)
Unable to find image '39a62b:0ab75364e68e47cc90d5aa9e43fcc042' locally
docker: Error response from daemon: pull access denied for 39a62b, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'.
before that, in github actions, we're running the following step:
/usr/bin/docker build -t [3](https://github.com/ivaoaero/scripts/actions/runs/4359030674/jobs/7641610911#step:2:3)9a62b:0ab7536[4](https://github.com/ivaoaero/scripts/actions/runs/4359030674/jobs/7641610911#step:2:4)e68e47cc90d[5](https://github.com/ivaoaero/scripts/actions/runs/4359030674/jobs/7641610911#step:2:5)aa9e43fcc042 -f "/home/debian/actions-runner/_work/_actions/aevea/action-kaniko/master/Dockerfile" "/home/debian/actions-runner/_work/_actions/aevea/action-kaniko/master"
WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
#1 [internal] load build definition from Dockerfile
#1 transferring dockerfile: 931B 0.0s done
#1 DONE 0.1s
#2 [internal] load .dockerignore
#2 transferring context: [6](https://github.com/ivaoaero/scripts/actions/runs/4359030674/jobs/7641610911#step:2:6)3B 0.0s done
#2 DONE 0.0s
#3 [internal] load metadata for docker.io/library/alpine:latest
#3 DONE 0.4s
#4 [internal] load metadata for gcr.io/kaniko-project/executor:v1.9.1-debug
#4 DONE 0.3s
#5 [stage-1 1/4] FROM gcr.io/kaniko-project/executor:v1.9.1-debug@sha256:ac169[7](https://github.com/ivaoaero/scripts/actions/runs/4359030674/jobs/7641610911#step:2:7)23b2076f9d5[8](https://github.com/ivaoaero/scripts/actions/runs/4359030674/jobs/7641610911#step:2:8)04f4bc05c[9](https://github.com/ivaoaero/scripts/actions/runs/4359030674/jobs/7641610911#step:2:9)8397e286da6fdcdd5a09fdc179f06ccb3be1
#5 resolve gcr.io/kaniko-project/executor:v1.9.1-debug@sha256:ac169723b2076f9d5804f4bc05c98397e286da6fdcdd5a09fdc179f06ccb3be1 0.0s done
#5 DONE 0.0s
#6 [certs 1/2] FROM docker.io/library/alpine@sha256:69665d02cb32192e52e07644d76bc6f25abeb54[10](https://github.com/ivaoaero/scripts/actions/runs/4359030674/jobs/7641610911#step:2:10)edc1c7a81a10ba3f0efb90a
#6 resolve docker.io/library/alpine@sha256:69665d02cb32192e52e07644d76bc6f25abeb5410edc1c7a81a10ba3f0efb90a 0.0s done
#6 DONE 0.0s
#7 [internal] load build context
#7 transferring context: 35B done
#7 DONE 0.0s
#8 [certs 2/2] RUN apk --update add ca-certificates
#8 CACHED
#9 [stage-1 2/4] RUN wget -O /kaniko/jq https://github.com/stedolan/jq/releases/download/jq-1.6/jq-linux64 && chmod +x /kaniko/jq && wget -O /kaniko/reg https://github.com/genuinetools/reg/releases/download/v0.16.1/reg-linux-386 && chmod +x /kaniko/reg && wget -O /crane.tar.gz https://github.com/google/go-containerregistry/releases/download/v0.8.0/go-containerregistry_Linux_x86_64.tar.gz && tar -xvzf /crane.tar.gz crane -C /kaniko && rm /crane.tar.gz
#9 CACHED
#10 [stage-1 3/4] COPY entrypoint.sh /
#10 CACHED
#[11](https://github.com/ivaoaero/scripts/actions/runs/4359030674/jobs/7641610911#step:2:11) [stage-[1](https://github.com/ivaoaero/scripts/actions/runs/4359030674/jobs/7641610911#step:3:1) 4/4] COPY --from=certs /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/ca-certificates.crt
#[1](https://github.com/ivaoaero/scripts/actions/runs/4359030674/jobs/7641610911#step:4:1)1 CACHED
Does anyone have any clue about what's going on here?
Thanks!
The text was updated successfully, but these errors were encountered:
Hi folks,
we're using action-kaniko on some workflows, but recently one stopped working with the following message:
before that, in github actions, we're running the following step:
Does anyone have any clue about what's going on here?
Thanks!
The text was updated successfully, but these errors were encountered: