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

build-mono-docker.ps1 fails to run out the box #453

Closed
ChrisMaddock opened this issue Aug 18, 2018 · 4 comments · Fixed by #716
Closed

build-mono-docker.ps1 fails to run out the box #453

ChrisMaddock opened this issue Aug 18, 2018 · 4 comments · Fixed by #716
Assignees
Milestone

Comments

@ChrisMaddock
Copy link
Member

ChrisMaddock commented Aug 18, 2018

I don't generally touch mono, but just tried out this script to debug #452. I followed the instructions in BUILDING.MD, which just say to install docker, and run .\build-mono-docker.ps1 -t test.

The script failed with the below message:

PS C:\Users\Chris\Documents\git\nunit-console> .\build-mono-docker.ps1 -t test
C:\ProgramData\chocolatey\lib\docker\tools\docker\docker.exe: error during connect: Post
 http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.33/containers/create: open //./pipe/docker_engine: 
The system cannot find the file specified. In the default daemon configuration on Windows, 
the docker client must be run elevated to connect. This error may also indicate that the 
docker daemon is not running.
See 'C:\ProgramData\chocolatey\lib\docker\tools\docker\docker.exe run --help'.

I've never touched Docker before, so have no idea what to do with that information! 😄 Anyone more familiar than I am have any guesses as to a fix we could put in?

@mikkelbu
Copy link
Member

@ChrisMaddock Probably a stupid question 😄, but did you run the docker client in elevated mode as the error message hinted?

@ChrisMaddock
Copy link
Member Author

I ran the script in elevated mode, yep. I presume I don’t need to be running something else separately, alongside running this script?

@mikkelbu
Copy link
Member

mikkelbu commented Nov 30, 2018

Running in an elevated PS shell I was able to get all the way to the Tests task. There TestNet20Engine and TestNet20Console succeeded, but the NetStandard failed with the following errors. Perhaps we need to update @rprouse's image, I can see that he has been working on this lately https://github.com/rprouse/nunit-docker.

========================================
TestNetStandard16Engine
========================================
Executing task: TestNetStandard16Engine
It was not possible to find any compatible framework version
The specified framework 'Microsoft.NETCore.App', version '1.1.2' was not found.
  - Check application dependencies and target a framework version installed at:
      /usr/share/dotnet/
  - Installing .NET Core prerequisites might help resolve this problem:
      https://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409
  - The .NET Core framework and SDK can be installed from:
      https://aka.ms/dotnet-download
  - The following versions are installed:
      2.1.6 at [/usr/share/dotnet/shared/Microsoft.NETCore.App]
An error occurred when executing task 'TestNetStandard16Engine'.

========================================
TestNetStandard20Engine
========================================
Executing task: TestNetStandard20Engine
It was not possible to find any compatible framework version
The specified framework 'Microsoft.NETCore.App', version '2.0.6' was not found.
  - Check application dependencies and target a framework version installed at:
      /usr/share/dotnet/
  - Installing .NET Core prerequisites might help resolve this problem:
      https://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409
  - The .NET Core framework and SDK can be installed from:
      https://aka.ms/dotnet-download
  - The following versions are installed:
      2.1.6 at [/usr/share/dotnet/shared/Microsoft.NETCore.App]
An error occurred when executing task 'TestNetStandard20Engine'.

@rprouse
Copy link
Member

rprouse commented Dec 2, 2018

@ChrisMaddock I got the same error message you did after a Docker upgrade. For some reason docker didn't start up after the update. A reboot fixed it.

@mikkelbu the error you reported slipped in with my updates to the docker image, sorry. I updated the image recently for the changes to the engine so that we had the newer .NET Core SDKs to build with. I didn't test with a few of the final changes though. It looks like I need to install .NET Core 1.1.2 and 2.0.6 into the image. I'll assign this to myself.

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

Successfully merging a pull request may close this issue.

3 participants