Differences

This shows you the differences between two versions of the page.

--- services:labtest:start [2025/04/01 14:48] – jas
+++ services:labtest:start [2025/04/02 13:53] (current) – jas
@@ Line 1320: / Line 1320: @@
 </code>
-NOTE: Your standard EECS home directory has limited storage space and is on network storage.  This is not ideal for working with containers.  Faculty who have their own research servers or personal machines can use these machines to experiment with containers, the result of which can be uploaded to the course ltinit directory.  For other uses, consult with tech.
+**NOTE:** Your EECS home directory has limited storage space and is on network storage.  **This is not ideal for working with containers.**  Faculty who have their own research servers or personal workstations can use this equipment to generate images, the result of which can be used in labtest.  Failing this, faculty can use /tmp space for **temporary** container development.  For more information, consult with tech.  For information on using containers in EECS click [[services:podman|here]].
 Start up the container from the ubuntu:latest image, and call it my-ubuntu:
@@ Line 1328: / Line 1328: @@
 </code>
-Make changes -- in this case, we'll just add a file, but you could install packages, create accounts, etc:
+Make changes -- in this case, we'll just add an empty file named "file", but you could install additional packages, add users or groups, and configure the system in any way you like:
 <code>
@@ Line 1354: / Line 1354: @@
 </code>
-Place my-new-ubuntu.tar into ltinit directory of the labtest:
+Place my-new-ubuntu.tar into ltinit directory in the course labtest web directory:
-Now in ltinit/labtest.sh we can load the image, start the container, and open up a Terminal window from the container:
+In ltinit/labtest.sh we can load the image, start the container, and open up a Terminal window connected to the container:
 <code>
@@ Line 1372: / Line 1372: @@
   * my-new-ubuntu is the image used to create the container
-NOTE: Large container downloads with large multi lab labtests could result in performance issues since all users will be downloading the container on login.  In this case, discuss with tech how we could instead add the container to the course labtest web directory, then include an alias in the users .cshrc file which will load the image, and start the containers.  As users will be doing this manually, and will be doing this at different times, the chance of performance issue is much less.
+**NOTE:** Large container downloads with large multi lab labtests could result in performance issues since all users will be downloading the container on login.  In this case, discuss with tech how we could instead add the container to the course labtest web directory, then include an alias in the users .cshrc file which will download the image with curl or wget, load the image, and start the container.  As users will be doing this manually, and will be doing this at different times, the chance of performance issue is much less.
 ====== Labtest File Synchronization (ltsave) ======