You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The junction created by 'powershell New-Item -ItemType Junction' when building a docker image points to nothing
In contrast:
The junction created by 'mklink /J' when building a docker image works
The junction created by 'powershell New-Item -ItemType Junction' in the running container works
Expected behavior
The junction should point to the target location
Information
Windows Version: 10.0.19043.1237
Docker Desktop Version: 4.0.0 (67817)
WSL2 or Hyper-V backend? WSL2
Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No
Steps to reproduce the behavior
On the hosting machine: docker build -t test .
Dockerfile
FROM mcr.microsoft.com/windows/servercore:ltsc2019
RUN mkdir test
RUN mklink /J sym1 C:\test
RUN mklink /J sym2 \\?\C:\test
RUN powershell New-Item -ItemType Junction -Path C:\sym3 -Value C:\test
RUN dir
Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.
Prevent issues from auto-closing with an /lifecycle frozen comment.
If this issue is safe to close now please do so.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale
Actual behavior
The junction created by 'powershell New-Item -ItemType Junction' when building a docker image points to nothing
In contrast:
The junction created by 'mklink /J' when building a docker image works
The junction created by 'powershell New-Item -ItemType Junction' in the running container works
Expected behavior
The junction should point to the target location
Information
Steps to reproduce the behavior
Dockerfile
Output
The text was updated successfully, but these errors were encountered: