prgeor
commented
1 year ago @paulmenzel can you pull the latest debian slave and run a clean build.
Open paulmenzel opened 1 year ago
prgeor
commented
1 year ago @paulmenzel can you pull the latest debian slave and run a clean build.
prgeor
commented
1 year ago @paulmenzel local key could be expired. latest pull request is passing in buildimage repo
paulmenzel
commented
1 year ago @prgeor, sorry I do not know what you mean. It is my understanding, that the Docker image is built from the Dockerfile and not downloaded. It’s built from debian:buster.
Checking sonic-slave-base image: sonic-slave-buster:74a1fa3d404
Image sonic-slave-buster:74a1fa3d404 not found. Building...
Sending build context to Docker daemon 274.4kB
Step 1/82 : FROM debian:busterdebian:buster is from six days ago:
$ docker images | grep buster
debian buster fecc81bbfb5f 6 days ago 114MB
wenwang00
commented
5 months ago Hi, I also encountered the same problem. How did you solve it in the end?
yuipoi2486
commented
3 weeks ago Hi,I encountered the same issue. Did you manage to resolve it
wenwang00
commented
3 weeks ago Hi,I encountered the same issue. Did you manage to resolve it
You need to update the pubkey.
yuipoi2486
commented
3 weeks ago @wenwang00 Thanks for your response. My issue is somewhat different from the original post. Here is my error message:
Unable to find image 'sonic-slave-buster:314903b0b3' locally Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Error: No such container:path: sonic-slave-buster-314903b0b3:/etc/os-release Error: No such container:path: sonic-slave-buster-314903b0b3:/usr/local/share/buildinfo/pre-versions Error: No such container:path: sonic-slave-buster-314903b0b3:/usr/local/share/buildinfo/post-versions Error response from daemon: No such image: sonic-slave-buster:314903b0b3 [+] Building 21.1s (3/4) => [internal] load build definition from Dockerfile.cleanup 0.0s => => transferring dockerfile: 315B 0.0s => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => ERROR FROM docker.io/library/sonic-slave-buster:314903b0b3 21.1s => => resolve docker.io/library/sonic-slave-buster:314903b0b3 21.0s FROM docker.io/library/sonic-slave-buster:314903b0b3: failed to load cache key: failed to do request: Head "https://registry-1.docker.io/v2/library/sonic-slave-buster/manifests/314903b0b3": dial tcp 185.60.219.36:443: connect: connection refused [+] Building 21.1s (3/3) FINISHED => [internal] load build definition from Dockerfile.cleanup 0.0s => => transferring dockerfile: 46B 0.0s => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => ERROR [internal] load metadata for docker.io/library/sonic-slave-buster:314903b0b3 21.0s [internal] load metadata for docker.io/library/sonic-slave-buster:314903b0b3: failed to solve with frontend dockerfile.v0: failed to create LLB definition: failed to do request: Head "https://registry-1.docker.io/v2/library/sonic-slave-buster/manifests/314903b0b3": dial tcp 185.60.219.36:443: connect: connection refused Error: No such image: tmp-sonic-slave-buster:314903b0b3 Error: No such container:path: sonic-slave-buster-314903b0b3:/usr/local/share/buildinfo/log sync: error opening 'sonic-slave-buster/vcache/cache.base64': No such file or directory Error: No such container: sonic-slave-buster-314903b0b3 Makefile.work:616: recipe for target 'configure' failed make[1]: [configure] Error 1 make[1]: Leaving directory "/home/yui/sonic-buildimage" Makefile:109: recipe for target 'configure' failed make: [configure] Error 2
My question is whether the "sonic-slave-buster" is pulled from DockerHub or from the local environment. I found that there is a directory named "sonic-slave-buster" in my downloaded "sonic-buildimage," which contains the following files:
-rw-rw-r-- 1 yui yui 69 Oct 30 11:41 apt-retries-count drwxrwxr-x 4 yui yui 4096 Oct 30 11:41 buildinfo -rw-rw-r-- 1 yui yui 14029 Oct 30 11:41 Dockerfile -rw-rw-r-- 1 yui yui 262 Oct 30 11:41 Dockerfile.cleanup -rw-rw-r-- 1 yui yui 23096 Oct 30 11:27 Dockerfile.j2 -rw-rw-r-- 1 yui yui 671 Oct 30 11:40 Dockerfile.user -rw-rw-r-- 1 yui yui 841 Oct 30 11:27 Dockerfile.user.j2 -rw-rw-r-- 1 yui yui 178 Oct 30 11:27 no-check-valid-until -rw-rw-r-- 1 yui yui 398 Oct 30 11:27 sonic-jenkins-id_rsa.pub -rw-rw-r-- 1 yui yui 20900 Oct 30 11:41 sonic-slave-buster_314903b0b3.log -rw-rw-r-- 1 yui yui 769 Oct 30 11:41 sources.list.amd64 drwxrwxrwx 2 yui yui 4096 Oct 30 11:41 vcache
wenwang00
commented
3 weeks ago @wenwang00 Thanks for your response. My issue is somewhat different from the original post. Here is my error message:
Unable to find image 'sonic-slave-buster:314903b0b3' locally Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Error: No such container:path: sonic-slave-buster-314903b0b3:/etc/os-release Error: No such container:path: sonic-slave-buster-314903b0b3:/usr/local/share/buildinfo/pre-versions Error: No such container:path: sonic-slave-buster-314903b0b3:/usr/local/share/buildinfo/post-versions Error response from daemon: No such image: sonic-slave-buster:314903b0b3 [+] Building 21.1s (3/4) => [internal] load build definition from Dockerfile.cleanup 0.0s => => transferring dockerfile: 315B 0.0s => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => ERROR FROM docker.io/library/sonic-slave-buster:314903b0b3 21.1s => => resolve docker.io/library/sonic-slave-buster:314903b0b3 21.0s FROM docker.io/library/sonic-slave-buster:314903b0b3: failed to load cache key: failed to do request: Head "https://registry-1.docker.io/v2/library/sonic-slave-buster/manifests/314903b0b3": dial tcp 185.60.219.36:443: connect: connection refused [+] Building 21.1s (3/3) FINISHED => [internal] load build definition from Dockerfile.cleanup 0.0s => => transferring dockerfile: 46B 0.0s => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => ERROR [internal] load metadata for docker.io/library/sonic-slave-buster:314903b0b3 21.0s [internal] load metadata for docker.io/library/sonic-slave-buster:314903b0b3: failed to solve with frontend dockerfile.v0: failed to create LLB definition: failed to do request: Head "https://registry-1.docker.io/v2/library/sonic-slave-buster/manifests/314903b0b3": dial tcp 185.60.219.36:443: connect: connection refused Error: No such image: tmp-sonic-slave-buster:314903b0b3 Error: No such container:path: sonic-slave-buster-314903b0b3:/usr/local/share/buildinfo/log sync: error opening 'sonic-slave-buster/vcache/cache.base64': No such file or directory Error: No such container: sonic-slave-buster-314903b0b3 Makefile.work:616: recipe for target 'configure' failed make[1]: [configure] Error 1 make[1]: Leaving directory "/home/yui/sonic-buildimage" Makefile:109: recipe for target 'configure' failed make: [configure] Error 2
My question is whether the "sonic-slave-buster" is pulled from DockerHub or from the local environment. I found that there is a directory named "sonic-slave-buster" in my downloaded "sonic-buildimage," which contains the following files:
-rw-rw-r-- 1 yui yui 69 Oct 30 11:41 apt-retries-count drwxrwxr-x 4 yui yui 4096 Oct 30 11:41 buildinfo -rw-rw-r-- 1 yui yui 14029 Oct 30 11:41 Dockerfile -rw-rw-r-- 1 yui yui 262 Oct 30 11:41 Dockerfile.cleanup -rw-rw-r-- 1 yui yui 23096 Oct 30 11:27 Dockerfile.j2 -rw-rw-r-- 1 yui yui 671 Oct 30 11:40 Dockerfile.user -rw-rw-r-- 1 yui yui 841 Oct 30 11:27 Dockerfile.user.j2 -rw-rw-r-- 1 yui yui 178 Oct 30 11:27 no-check-valid-until -rw-rw-r-- 1 yui yui 398 Oct 30 11:27 sonic-jenkins-id_rsa.pub -rw-rw-r-- 1 yui yui 20900 Oct 30 11:41 sonic-slave-buster_314903b0b3.log -rw-rw-r-- 1 yui yui 769 Oct 30 11:41 sources.list.amd64 drwxrwxrwx 2 yui yui 4096 Oct 30 11:41 vcache
It seems to me that it is built locally
chetansk
commented
3 weeks ago Hi,I encountered the same issue. Did you manage to resolve it
You need to update the pubkey.
I am facing similar problem, how do I update the pubkey? Doesn't trusted=yes solve? It did not for me
Trying to build the platform vs, I get the error below: