Difference between revisions of "Windows Anamolies"
| Line 1: | Line 1: | ||
Since [[PKC]] is designed around Linux-based containerization technology, which means that it will have many incompatibilities with [[Windows]] inherently. There are some tips that we captured here: | Since [[PKC]] is designed around Linux-based containerization technology, which means that it will have many incompatibilities with [[Windows]] inherently. There are some tips that we captured here: | ||
===VPN Software Interfering with WSL=== | ===VPN Software Interfering with WSL=== | ||
Under Windows 10 Environment, some VPN software might interfere with [[Docker]]'s Windows Subsystem for Linux, a.k.a. [[wikipedia:Windows Subsystem for Linux|Windows Subsystem for Linux (WSL)]], you will need to remove VPN software before [[Docker Runtime Installation|installing Docker]]. In case you don't want to remvoe your VPN software, or your Docker and Bash have compatibility issues, please try the following solution:[[Installing VirtualBox for PKC]]. | |||
===Choosing adequate directories=== | ===Choosing adequate directories=== | ||
Make sure that you don't pick a directory outside of your usual Users/Documents directory. If you choose some directories outside of your User/Documents directory, it is possible that certain batch script commands will stop to work, due to file right access authority issues. | [[Mitch Altman]] identified the following scenarios for [[PKC]] installation on [[Windows 10]], which indicate that Windows users will face many unexpected problems during installation, the following lists are some important ones. Make sure that you don't pick a directory outside of your usual Users/Documents directory. If you choose some directories outside of your User/Documents directory, it is possible that certain batch script commands will stop to work, due to file right access authority issues. | ||
===GNU TAR might not work=== | ===GNU TAR might not work=== | ||
[[Mitch Altman|Mitch]] also found that tar command may not work on certain machines. To ensure that [[PKC]] will install smoothly on [[Windows 10]] machines, we put an <code>.exe</code> (Windows executable) file <code>[[unzip.exe]]</code><ref>{{:Unzip.exe}}</ref> in the <code>PKC/resources</code> directory. We also made sure that a initial data package, namely mountPoint.zip is included in the <code>resources</code> directory, so that the <code>up.bat</code> script will be able to conduct the automatic installation and initial launch process completely. | |||
<noinclude> | <noinclude> | ||
==References== | ==References== | ||
<references/> | <references/> | ||
</noinclude> | </noinclude> | ||
Revision as of 07:35, 29 August 2021
Since PKC is designed around Linux-based containerization technology, which means that it will have many incompatibilities with Windows inherently. There are some tips that we captured here:
VPN Software Interfering with WSL
Under Windows 10 Environment, some VPN software might interfere with Docker's Windows Subsystem for Linux, a.k.a. Windows Subsystem for Linux (WSL), you will need to remove VPN software before installing Docker. In case you don't want to remvoe your VPN software, or your Docker and Bash have compatibility issues, please try the following solution:Installing VirtualBox for PKC.
Choosing adequate directories
Mitch Altman identified the following scenarios for PKC installation on Windows 10, which indicate that Windows users will face many unexpected problems during installation, the following lists are some important ones. Make sure that you don't pick a directory outside of your usual Users/Documents directory. If you choose some directories outside of your User/Documents directory, it is possible that certain batch script commands will stop to work, due to file right access authority issues.
GNU TAR might not work
Mitch also found that tar command may not work on certain machines. To ensure that PKC will install smoothly on Windows 10 machines, we put an .exe (Windows executable) file unzip.exe[1] in the PKC/resources directory. We also made sure that a initial data package, namely mountPoint.zip is included in the resources directory, so that the up.bat script will be able to conduct the automatic installation and initial launch process completely.
References
- ↑ Works, Stahl (20 August 2021). ZIP Related Tools.