Web Content Display Web Content Display

Labtainers Support

We value your feedback, questions and trouble reports.  Please contact me at: mfthomps at nps.edu.  Or, use GitHub to report issues. 

If you'd like to be notified of updates to the Labtainer framework, please send an email to labtainers-request [at] freelists.org with 'subscribe' in the Subject field OR by visiting our mail list page.

Troubleshooting suggestions are listed below.  You can update your Labtainers installation by running:

    update-labtainers.sh

from your labtainers-student directory.  

Important update notice:

Virtual Machine images were replaced on July 5, 2018.  If you are using older VM images, you might consider transitioning to the newer VM.  Otherwise, running new labs will require large downloads that may consume your VM resources.

Troubleshooting

Virtual machine troubleshooting (problems with the VM appliance)

Labtainers trouble shooting

Developer troubleshooting

 

Virtual Machine Troubleshooting:

  • 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 off from 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
  • Ubuntu Package manager error (red stop symbol in upper right of desktop):  If an Ubuntu VM reports package errors, try using the "sudo apt-get install -f" command and then reboot. 

Labtainers Troubleshooting

  • Get updates by running update-labtainer.sh (These include fixes to student and instructor environments.)
  • When starting a new Labtainer, if you see an error such as "No JSON object could be decoded", try updating your installation (per above).
  • 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:
   cd
   tar -xf ~/Downloads/labtainer.tar 
Then return to ~/labtainer/labtainer-student and try again.
 

Developer Troubleshooting:

  • 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).