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

Version 1.20.2 fails to run on Windows 10 v1809 #2758

Closed
ajkauffmann opened this issue Mar 7, 2019 · 12 comments
Closed

Version 1.20.2 fails to run on Windows 10 v1809 #2758

ajkauffmann opened this issue Mar 7, 2019 · 12 comments

Comments

@ajkauffmann
Copy link

@ajkauffmann ajkauffmann commented Mar 7, 2019

Bug description
Version 1.20.2 fails to start on Windows 10 v1809.
Error message returned from:

docker : Error response from daemon: container 5fb0aa8da94f5862adc267727babc0a09386286928fea8b708cb6d03415ff353 encountered an error during Start: failure in a Windows system call: The virtual machine or container exited unexpectedly. (0xc0370106)
At line:1 char:1
+ docker start portainer
+ ~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Error response ...y. (0xc0370106):String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError
 
Error: failed to start containers: portainer

Expected behavior
Version 1.20.1 runs without problems. I expect version 1.20.2 to do the same. ;-)

Steps to reproduce the issue:

docker pull portainer/portainer
docker run -d --restart always --name portainer --isolation process -h portainer -p 9000:9000 -v C:\ProgramData\Portainer:C:\Data -v //./pipe/docker_engine://./pipe/docker_engine portainer/portainer

Technical details:

  • Portainer version: 1.20.2
  • Docker version (managed by Portainer): 18.09.3
  • Platform (windows/linux): Windows 10 Pro v1809
  • Command used to start Portainer: docker run -d --restart always --name portainer --isolation process -h portainer -p 9000:9000 -v C:\ProgramData\Portainer:C:\Data -v //./pipe/docker_engine://./pipe/docker_engine portainer/portainer
  • Browser: Chrome

Additional context
Version 1.20.1 works without any problem.

@deviantony

This comment has been minimized.

Copy link
Member

@deviantony deviantony commented Mar 7, 2019

@ssbkang can you reproduce this one?

@ssbkang

This comment has been minimized.

Copy link
Contributor

@ssbkang ssbkang commented Mar 7, 2019

@deviantony Yeah, I can reproduce this

docker run -d --restart always --name portainer --isolation process -h portainer -p 9000:9000 -v C:\ProgramData\Portainer:C:\Data -v //./pipe/docker_engine://./pipe/docker_engine portainer/portainer:1.20.2
834f7cc4ebf3e6fd7a564eb77ebb2f85794c99e65d60b886f3eab2e79e4267bf
C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: container 834f7cc4ebf3e6fd7a564eb77ebb2f85794c99e65d60b886f3eab2e79e4267bf encountered an error during Start: failure in a Windows system call: The virtual machine or container exited unexpectedly. (0xc0370106).
@NAVspecialist

This comment has been minimized.

Copy link

@NAVspecialist NAVspecialist commented Mar 7, 2019

Yes I can reproceduce it too with same parameters.

@ssbkang ssbkang self-assigned this Mar 7, 2019
@linquize

This comment has been minimized.

Copy link
Contributor

@linquize linquize commented Mar 7, 2019

docker run portainer/portainer:1.20.2 (windows)

with --isolation process,
error message is encountered an error during Start: failure in a Windows system call: The virtual machine or container exited unexpectedly.

without --isolation process,
The container is created, but docker start stucks.

No problem if I compile 1.20.2 from source and run portainer like this
docker run -d -p 9000:9000 -v %CD%\dist:C:\app -v %TMP%\portainer:C:\data -v \\.\pipe\docker_engine:\\.\pipe\docker_engine --name portainer mcr.microsoft.com/windows/nanoserver:1809 C:\app\portainer.exe --no-analytics --template-file C:\app\templates.json

@ssbkang

This comment has been minimized.

Copy link
Contributor

@ssbkang ssbkang commented Mar 8, 2019

@ajkauffmann @NAVspecialist @linquize would you please give another go with the latest image?

PS C:\Users\skan0> docker image pull portainer/portainer:latest
latest: Pulling from portainer/portainer
Digest: sha256:a75450f44e2f5bcece74a273afcd0627029e423f6ea1ba20b3af62a5556bbb06
Status: Downloaded newer image for portainer/portainer:latest
PS C:\Users\skan0>
PS C:\Users\skan0> docker run -d -p 9000:9000 --name portainer --restart always -v C:\ProgramData\Portainer:C:\Data -v \\.\pipe\docker_engine:\\.\pipe\docker_engine portainer/portainer:latest
20d93158f13f4a0c1a64f8a77238872aa22e270395d5a49495dc860b418dfc8d
PS C:\Users\skan0> docker logs -f 20d
2019/03/08 14:59:06 Starting Portainer 1.20.2 on :9000
@ssbkang

This comment has been minimized.

Copy link
Contributor

@ssbkang ssbkang commented Mar 8, 2019

Please try without --isolation process for now, there seems to be an issue with this.

@NAVspecialist

This comment has been minimized.

Copy link

@NAVspecialist NAVspecialist commented Mar 8, 2019

Hello there

I have tried without the --isolation process and then I can start Portainer without an error. But but when I try to connect to an endpoint (Local) then I get the error:

"Failure -Endpoint is unreachable and there is no snapshot available for offline browsing."

I tried to change the \.\pipe\docker_engine:\.\pipe\docker_engine (backslash to forwardslash) but that made no difference.

In 1.20.1 - //./pipe/docker_engine://./pipe/docker_engine works quite fine also with --isolation process

@ajkauffmann

This comment has been minimized.

Copy link
Author

@ajkauffmann ajkauffmann commented Mar 8, 2019

I'm running by default in isolation process mode, so removing the option doesn't do much I guess.

Pulled the latest image (created 2019-03-08 02:20:41) and created the container. No error message during container creation, but it won't work after all.

Docker logs gives me this error log:

docker : 2019/03/08 16:24:09 open C:\data/portainer.db: Access is denied.
At line:1 char:1
+ docker logs portainer
+ ~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (2019/03/08 16:2...cess is denied.:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError
 
2019/03/08 16:24:10 open C:\data/portainer.db: Access is denied.
2019/03/08 16:24:11 open C:\data/portainer.db: Access is denied.
2019/03/08 16:24:12 open C:\data/portainer.db: Access is denied.

This was with volume -v C:\ProgramData\Portainer:C:\Data
When create the container without this volume, I get this output from the logs:

docker : 2019/03/08 16:18:08 mkdir C:\data/tls: Access is denied.
At line:1 char:1
+ docker logs portainer
+ ~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (2019/03/08 16:1...cess is denied.:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError
 
2019/03/08 16:18:09 mkdir C:\data/tls: Access is denied.
2019/03/08 16:18:10 mkdir C:\data/tls: Access is denied.
2019/03/08 16:18:11 mkdir C:\data/tls: Access is denied.
2019/03/08 16:18:13 mkdir C:\data/tls: Access is denied.

Reverting back to version 1.20.1 and everything is normal again.

@ssbkang

This comment has been minimized.

Copy link
Contributor

@ssbkang ssbkang commented Mar 11, 2019

@ajkauffmann Thanks for testing. We've noticed that there is an issue with our current build - please use 1.20.1 for now, and we will get back to you soon as the build is fixed.

@ssbkang

This comment has been minimized.

Copy link
Contributor

@ssbkang ssbkang commented Mar 11, 2019

@ajkauffmann The latest image will be good now, please try again.

@ajkauffmann

This comment has been minimized.

Copy link
Author

@ajkauffmann ajkauffmann commented Mar 11, 2019

@ssbkang Tested and confirmed, it works with the latest image. Thanks for great work, much appreciated!

@ssbkang

This comment has been minimized.

Copy link
Contributor

@ssbkang ssbkang commented Mar 11, 2019

Awesome, thanks a lot for raising & testing this issue - closing!

@ssbkang ssbkang closed this Mar 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.