microsoft/Windows-Containers

Pull failure, “invalid hard link in layer”, when pulling windows:10.0.19042.1889

Opened this issue · 1 comments

JianhongGao commented

Please fill out all the sections below for bug issues, otherwise it'll be closed as it won't be actionable for us to address.

Describe the bug
When execute "docker pull mcr.microsoft.com/windows:10.0.19042.1889", it failed.

The execution output:
10.0.19042.1889: Pulling from windows
f26dc4584b4d: Pull complete
ad7b58431666: Extracting [==================================================>] 3.306 GB/3.306 GB
failed to register layer: re-exec error: exit status 1: output: invalid hard link in layer

The Docker for Windows log:
[15:49:15.291][ApiProxy ][Info ] proxy >> GET /_ping
[15:49:15.291][ApiProxy ][Info ] Dial name pipe \.\pipe\docker_engine_windows
[15:49:15.291][ApiProxy ][Info ] Successfully dialed name pipe \.\pipe\docker_engine_windows
[15:49:15.292][ApiProxy ][Info ] proxy << GET /_ping
[15:49:15.729][ApiProxy ][Info ] proxy >> POST /v1.27/images/create?fromImage=mcr.microsoft.com%2Fwindows&tag=10.0.19042.1889
[15:49:15.729][ApiProxy ][Info ] Dial name pipe \.\pipe\docker_engine_windows
[15:49:15.729][ApiProxy ][Info ] Successfully dialed name pipe \.\pipe\docker_engine_windows
[16:09:46.056][ApiProxy ][Info ] proxy << POST /v1.27/images/create?fromImage=mcr.microsoft.com%2Fwindows&tag=10.0.19042.1889
[16:09:46.056][WindowsDockerDaemon][Info ] time="2024-06-21T16:09:46.056336600+08:00" level=error msg="Error trying v2 registry: failed to register layer: re-exec error: exit status 1: output: invalid hard link in layer"
[16:09:46.056][WindowsDockerDaemon][Info ] time="2024-06-21T16:09:46.056336600+08:00" level=error msg="Attempting next endpoint for pull after error: failed to register layer: re-exec error: exit status 1: output: invalid hard link in layer"
[16:11:16.811][WindowsDockerDaemon][Info ] time="2024-06-21T16:11:16.811845600+08:00" level=info msg="Layer sha256:fe97d2fde0ecfd65fa85c3a6046563046bea73f89637f9cdf1b9b60718484cc0 cleaned up"
[16:12:42.075][SegmentApi ][Info ] Usage statistic: actionMenuFeedback
[16:12:44.405][FeedbackSettings][Info ] Open logs

To Reproduce
Step 1: Right click docker icon and click "Switch to Windows containers..."
Step 2: open CMD
Step 3: docker pull mcr.microsoft.com/windows:10.0.19042.1889

Expected behavior
Pull success.

Configuration:

  • Edition: [e.g. Windows 11, Windows Server]
    Windows 10 Enterprise:
    22H2
    19045.2006
    Windows Feature Experience Pack 120.2212.4180.0

  • Base Image being used: [e.g. Windows Server Core]
    windows:10.0.19042.1889

  • Container engine: [e.g. docker]

  • Container Engine version [e.g. 22]
    Docker for Windows,
    Version 17.03.1-ce-rc1-win3 (10625)
    Channel: edge
    1795b35

Additional context
Add any other context about the problem here.

ntrappe-msft commented

Update: This did not repro on our most recent build. We'll try to see if it does repro on Windows 10.