[Questions] How to build image FROM local images

[gbdjxgp]

Hello, I used a local image when trying to build an image using docker buildx build, but Docker still tried to find this image on Docker Hub.

docker build -t aaa:bbb -f model-infer/docker/Dockerfile-xx-ci-xxxx-release-cache . 
[+] Building 30.0s (2/2) FINISHED                                          docker-container:mybuilder-v1.1.0
 => [internal] load build definition from Dockerfile-xx-ci-gpustack-release-cache                      0.0s
 => => transferring dockerfile: 1.31kB                                                                  0.0s
 => ERROR [internal] load metadata for docker.io/library/abc-dev:v2-4                                  30.0s
------
 > [internal] load metadata for docker.io/library/abc-dev:v2-4:
------
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
Dockerfile-xx-ci-gpustack-release-cache:1
--------------------
   1 | >>> FROM abc-dev:v2-4 AS abc-install
   2 |     
   3 |     ENV PIPX_LOCAL_VENVS=/root/.local/share/pipx/venvs
--------------------
ERROR: failed to solve: abc-dev:v2-4: failed to resolve source metadata for docker.io/library/abc-dev:v2-4: failed to do request: Head "https://registry-1.docker.io/v2/library/abc-dev/manifests/v2-4": dial tcp 199.59.148.6:443: i/o timeout

The dockerfile likes this:

FROM abc-dev:v2-4 AS abc-install

ENV PIPX_LOCAL_VENVS=/root/.local/share/pipx/venvs
...

and i use this command to build a image:docker build -t aaa:bbb -f model-infer/docker/Dockerfile-xx-ci-xxxx-release-cache .
I guarantee that the images (abc-dev:v2-4) exist on my local server and can be viewed through docker images
How can I avoid this problem? Or is this intentional design of Buildkit? Looking forward to your reply!

[gbdjxgp]

The problem may occur in docker buildkit, which may be caused by the BuildKit container not having access to dockerhub. For those who later viewed this issue, please try setting the environment variable: DOCKER_SULLDKIT=1 to avoid running with the build container.

[gbdjxgp]

reference:
1.However, this method currently has some limitations. The docker-container driver cannot access the local Docker image cache (reference), so all images referenced in FROM must exist in an image registry.
2.Cannot give a local image to FROM when using docker-container