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: | ||
=== | ===Consult the System Administrator of the Computer=== | ||
Some system administrators will block users from installing WSL2.0. If this is the case, the Windows operating system needs to be reinstalled to avoid that blocking. | Some system administrators will block users from installing WSL2.0. If this is the case, the Windows operating system needs to be reinstalled to avoid that blocking. | ||
Revision as of 13:30, 10 February 2022
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:
Consult the System Administrator of the Computer
Some system administrators will block users from installing WSL2.0. If this is the case, the Windows operating system needs to be reinstalled to avoid that blocking.
Windows Subsystem for Linux (WSL) Update
After installing Docker Desktop, Windows 10 will often ask for the installation of WSL update. Please follow the wizard, and install the update accordingly.
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 the interfering VPN software before installing Docker. Please note that not all VPN software interferes with WSL. In case you don't want to remove 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.