We value your feedback, questions and trouble reports. Please contact me at: mfthomps at nps.edu
Or, use GitHub to report issues: https://github.com/mfthomps/Labtainers
- VMWare virtual machine windows sometimes become hard to use, depending on your platform. Try using: "View" / "Autosize" / select "Autofit Guest".
- If you have trouble installing a 64-bit guest on VirtualBox on Windows 10, refer to this link:
https://forums.virtualbox.org/viewtopic.php?f=1&t=62339 Or, run
bcdedit /set hypervisorlaunchtype offfrom an elevated command prompt.
- If a VMWare virtual machine becomes unable to reach your network, this can usually be resolved by rebooting your system, e.g., your Mac. Alternately, these commands often work from within a terminal on the Mac:
- sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --configure
- sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --stop
- sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli –start
- Get updates by running update-labtainer.sh (These include fixes to student and instructor environments.)
- If the "labtainer" (or start.py) commands do not do anything, your installation has been corrupted. You can recover from that as follows:
Go to https://my.nps.edu/web/cisr/labtainers
Click the link named: “Download the Labtainer framework” and save the file into your Downloads directory.
Then extract it:
tar -xf ~/Downloads/labtainer.tar
Then return to ~/labtainer/labtainer-student and try again.
- Get updates by running labtainer/setup_scripts/update-designer.sh
- Periodically use the /labtainer/setup_scripts/cleanupDocker.sh to remove unused images. This will reclaim disk space consumed when doing many iterations of building the same lab.
- As a last resort, use the labtainer/setup_scripts/destroy-docker.sh to fully erase all local Docker images. Then use pull-all.sh to pull in all baseline images (several GB download).