-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
Open
Labels
BuildLibrary building on various platformsLibrary building on various platformsClosing CandidateMay be closeable, needs more eyeballsMay be closeable, needs more eyeballs
Description
When I tried to use the Dockerfile provided in the root directory to build my local developing environment, I encountered the following error:
[+] Building 21.7s (2/2) FINISHED docker:default
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 957B 0.0s
=> ERROR [internal] load metadata for docker.io/library/python:3.11.13 21.6s
------
> [internal] load metadata for docker.io/library/python:3.11.13:
------
Dockerfile:1
--------------------
1 | >>> FROM python:3.11.13
2 | WORKDIR /home/pandas
3 |
--------------------
ERROR: failed to build: failed to solve: python:3.11.13: failed to resolve source metadata for docker.io/library/python:3.11.13: failed to do request: Head "https://registry-1.docker.io/v2/library/python/manifests/3.11.13": dialing registry-1.docker.io:443 container via direct connection because disabled has no HTTPS proxy: connecting to registry-1.docker.io:443: dial tcp [2a03:2880:f127:283:face:b00c:0:25de]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
It shows that the base image used in the Dockerfile no longer exists, and I searched the Dockerhub and confirmed that it no longer exits.Now I changed the base image to python:3.11.14 as an alternative.
I think it is necessary to update this Dockerfile.
Metadata
Metadata
Assignees
Labels
BuildLibrary building on various platformsLibrary building on various platformsClosing CandidateMay be closeable, needs more eyeballsMay be closeable, needs more eyeballs