Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Registry Symbolic Link lost when building an image #5316

Closed
1 of 2 tasks
robe070 opened this issue Dec 13, 2019 · 5 comments
Closed
1 of 2 tasks

Registry Symbolic Link lost when building an image #5316

robe070 opened this issue Dec 13, 2019 · 5 comments

Comments

@robe070
Copy link

robe070 commented Dec 13, 2019

  • I have tried with the latest version of my channel (Stable or Edge)
  • I have uploaded Diagnostics. I don't know which diagnostics are relevant to this Windows behavior.
  • Diagnostics ID:

Expected behavior

Registry Symbolic Link continues to work in Container

Actual behavior

Symbolic link is no longer recongised by Windows as a symbolic link
PS C:> reg query HKEY_LOCAL_MACHINE\Software\LANSA

HKEY_LOCAL_MACHINE\Software\LANSA
SymbolicLinkValue REG_LINK 5C00520065006700690073007400720079005C004D0041004300480049004E0045005C0053006F0066007400
77006100720065005C0057006F00770036003400330032004E006F00640065005C004C0041004E0053004100

Information

  • It is reproducible
  • Its in Images mcr.microsoft.com/windows/servercore/iis:windowsservercore-1903 and 1909
  • Host Windows Version: Microsoft Windows [Version 10.0.18363.535]
  • Docker Desktop Version: 2.1.0.5 (40693)
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM:
    No

Steps to see behavior working

  1. Run a 1909 container
    docker run -it --isolation=process -v h:\temp:c:\temp mcr.microsoft.com/windows/servercore/iis:windowsservercore-1909

Note: Put the program x64SoftwareKeyLink.exe, described in repro section, in the h:\temp directory or equivalent.

  1. Run another powershell session into the container

docker exec -it [id] powershell

  1. Run same commands as in the dockerfile below
reg add HKEY_LOCAL_MACHINE\Software\WOW6432Node\LANSA; `
reg query HKEY_LOCAL_MACHINE\Software\WOW6432Node\LANSA; `
c:\temp\x64SoftwareKeyLink.exe LANSA; `
reg query HKEY_LOCAL_MACHINE\Software\LANSA
  1. Result:
The operation completed successfully.

HKEY_LOCAL_MACHINE\Software\WOW6432Node\LANSA
    (Default)    REG_SZ

Setting symlink key succeeded

HKEY_LOCAL_MACHINE\Software\LANSA
    (Default)    REG_SZ

Steps to reproduce the behavior

  1. Dockerfile
# escape=`
FROM mcr.microsoft.com/windows/servercore/iis:windowsservercore-1909
SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"]
RUN Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope LocalMachine
COPY .\*.exe .\
RUN reg add HKEY_LOCAL_MACHINE\Software\WOW6432Node\LANSA; `
    reg query HKEY_LOCAL_MACHINE\Software\WOW6432Node\LANSA; `
    .\x64SoftwareKeyLink.exe LANSA; `
    reg query HKEY_LOCAL_MACHINE\Software\LANSA
  1. The program .\x64SoftwareKeyLink.exe and its source code may be found [here]. (https://www.codeproject.com/Articles/11973/Registry-Symbolic-Links). The program needs to be in the Dockerfile directory

  2. Run the new image and powershell into it and run this command

reg query HKEY_LOCAL_MACHINE\Software\LANSA

  1. Result:
HKEY_LOCAL_MACHINE\Software\LANSA
    SymbolicLinkValue    REG_LINK    5C00520065006700690073007400720079005C004D0041004300480049004E0045005C0053006F0066007400
77006100720065005C0057006F00770036003400330032004E006F00640065005C004C0041004E0053004100
@docker-robott
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d 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

@robe070
Copy link
Author

robe070 commented Mar 12, 2020 via email

@robe070
Copy link
Author

robe070 commented Mar 12, 2020 via email

@mat007
Copy link
Member

mat007 commented Mar 12, 2020

This does not look like an issue with the Docker Desktop application itself but with the upstream docker windows container implementation so I'm closing this issue. Could you please open an issue on https://github.com/moby/moby instead as that is the more appropriate place?

@mat007 mat007 closed this as completed Mar 12, 2020
@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jul 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants