I was getting this weird error on Docker for the same container that was building fine just minutes go.
$ docker build -t hummingbird:1.0.0 .
[+] Building 0.3s (3/3) FINISHED
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 37B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> ERROR [internal] load metadata for docker.io/cellprofiler/cellprofiler:4.0.6 0.0s
------
> [internal] load metadata for docker.io/cellprofiler/cellprofiler:4.0.6:
------
failed to solve with frontend dockerfile.v0: failed to create LLB definition: failed to do request: Head "https://registry-1.docker.io/v2/cellprofiler/cellprofiler/manifests/4.0.6": proxyconnect tcp: dial tcp 192.168.65.1:3128: connect: network is unreachable
Turned out, this error can appear when the disk is full (observed in MacOS), with no issue from the built container image itself. How did the desk get full within a few minutes? Of course, by building a few Docker containers and them remaining in cache. Deleting some files to get some storage space and restarting Docker made the build succeed again.
No comments:
Post a Comment
You are welcome to provide your opinions in the comments. Spam comments and comments with random links will be deleted.