Test on Windows machine

[veitveit]

Somebody with a Windows computer should test how to run the docker image.

[veitveit]

@jgriss @gvinterhalter

I now managed to find somebody to test it. It was Windows 10 Home edition and this means that docker does only work in a virtual machine. This is done automatically by the Docker Toolbox, nicely described in https://docs.docker.com/toolbox/toolbox_install_windows/

But then folder mounting becomes rather tricky as the virtual machine embedding the docker engine would need to be configured to include shared folders.

On top of this issue, the "open browser" command won't work and the URL is 192.168.99.100:8888 (access to the virtual machine) instead of 0.0.0.0:8888.

My suggestion for the batch file is:

• Check for whether it is Docker or Docker Toolbox
• In the latter case, do not open a browser and do not mount /data and /data/OUT
• Add text such as "Open the protocol by writing the URL '192.168.99.100:8888' in your browser"
• Add text "Files can be uploaded into IsoLabeledProtocol using the browser interface. We recommend adding them to the '/data' folder"

Would that work?

And yes, Hyper-V (hardware virtualization) is usually not enabled in the BIOS. This will be fun when thinking about 25 different computers :-)

[jgriss]

I believe for people on Windows to really be able to use the protocol we'll have to create a proper tutorial including screenshots to guide them through the process. I'm currently trying to get a windows 10 license for one of my computers. Then I can run through the process once and write everything down. But this might still take a few days.

[jgriss]

Currently testing on a fresh Windows 10:

• Docker install worked without a problem
• run.sh downloaded the image as expected
• launching the browser and creating the OUT folder fails:

Status: Downloaded newer image for veitveit/isolabeledprotocol:release-0.1
Adress: http://localhost:8888
The system cannot find the file openBrowser.
Access is denied.
Error: Can't create folder OUT
Run error
Press any key to continue . . .

[jgriss]

Additionally, even though based on the command line output the image was downloaded correctly, the script tries to download it again when launching it again.

[jgriss]

I'm now adding separate issues for these bugs to keep track of this

[jgriss]

This has been addressed through the ProtProtocols/docker-launcher tool