Docker failed to pull image no such file or directory

Question

I'm creating a docker image from another image using the most simple docker file:

FROM <source image>

The image builds and tags successfully. However when I push it to an Azure Container Registry and pull the image I get the following error:

Failed to pull image "<tagged image name>": rpc error: code = Unknown desc = failed to pull and unpack image "<tagged image name>": failed to extract layer sha256:<layer id>: link /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/2700/fs/Files/Program Files/common files/Microsoft Shared/Ink/en-US/micaut.dll.mui /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/2700/fs/Files/Program Files (x86)/common files/Microsoft Shared/ink/en-US/micaut.dll.mui: no such file or directory: unknown

The original image from the same registry pulls and runs successfully.

Any idea what I'm doing wrong?

can you share the code you use to build and tag the container? image names must be fully qualified — code_monk, Nov 23 '21 at 15:31

score 0 · Answer 1 · answered Nov 23 '21 at 14:09

0

Azure Container Registry is a private registry. Hence, make sure you login to the registry before pulling the image. Refer the link to know ways to authenticate https://learn.microsoft.com/en-us/azure/container-registry/container-registry-authentication?tabs=azure-cli

answered Nov 23 '21 at 14:09

Kavya

105
1
15

I'm reasonably sure this isn't an authentication issue. I can pull the original image from the same repo fine. – Giles Roberts Nov 23 '21 at 14:16
Where is this new image being built? Is this "other image" in Azure Registry? – Kavya Nov 25 '21 at 06:06

score 0 · Answer 2 · answered Nov 01 '22 at 08:32

0

I meet the same issue since I ran Windows container on Linux node. Please make sure your Windows container is running on Windows node.

answered Nov 01 '22 at 08:32

GTMer

11
3

Docker failed to pull image no such file or directory

2 Answers2