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

msi installer file created successfully but file has no owner and creating permission problems #5855

Open
paul-mateos opened this Issue Jul 26, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@paul-mateos
Copy link

paul-mateos commented Jul 26, 2018

Please provide answers to the following questions to help us narrow down, reproduce, and fix the problem. Fill out one section and delete the others.

Triage

  • Created a WPF solution and WIX Setup project in visual studio 2017 with WIX extensions installed.

  • Downloaded WIX binaries and configured WIX setup project to use the binaries for MSBUILD

  • Using docker image microsoft/dotnet-framework:3.5-sdk to build the solution

  • Solution builds successfully and MSI created successfully

  • Attempted to use/copy/archive the msi but unable to. Access denied permission error raised.

  • Running the build and msi creation within VS2017 works fine and the permission problem does not exist

Discussions and support

  • I attempted to create a file in the same location as the msi using PS>New-Item as part of the docker run command right after the msbuild succeeded. The file i created had no issues.
  • The permission problem occurs within the docker container and on the docker host machine when the file is volumed out.

Bugs

If this issue is a bug:

  • Which version of WiX are you building with?
    3.11.1

  • Which version of Visual Studio are you building with (if any)?

2017 Enterprise

  • Which version of the WiX Toolset Visual Studio Extension are you building with (if any)?

2017

  • Which version of .NET are you building with?

4.5.2

  • Describe the problem and the steps to reproduce it.
  • create msi as part of the msbuild process using docker
  • copy created msi to another location and error will be produced
  • Describe the behavior you expected and how it differed from the actual behavior.

file permission should allow for file use

@barnson

This comment has been minimized.

Copy link
Member

barnson commented Aug 2, 2018

Please try the -sacl switch to Light.exe to suppress the default ACL resetting behavior. If that works, please let us know; we'll investigate what we can do to make Docker's behavior work.

@barnson barnson modified the milestones: v4.0, v4.x Aug 2, 2018

@vorsth

This comment has been minimized.

Copy link

vorsth commented Nov 2, 2018

I ran into this same issue. I set the -sacl switch by adding <SuppressAclReset>True</SuppressAclReset> in a PropertyGroup in my .wixproj which did allow me to build the MSI installers and I was able to copy/archive them.

I was able to test this using on two different versions of Windows which did have different base Docker images, but only saw the issue on Windows Server 2016 version 1607.

Windows Version Base Docker Image Had This Issue
Windows Server 2016 version 1607 microsoft/dotnet-framework:4.7.1-windowsservercore-ltsc2016 Yes
Windows 10 Pro version 1709 microsoft/dotnet-framework:4.7.1 No

I both cases I was using:
WiX 3.11.1
Docker 18.06.1-ce, build e68fc7a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment