Troubleshooting NCShare Class Containers (Faculty)

Containers are a new option for giving students access to the software you want them to have for classes, without the need for complicated, error-prone configuration processes. All your students need is a Web browser. Based on your input, an image is built containing all the needed software. Each student then opens a container environment based on that image. Class containers are identical, spawned from the same image file. Because each instance of a container is identical to all other instances, image/system problems tend to manifest quickly and widely, and solving the problem in one place typically solves it for everyone. Problems unique to one student are most likely bad data or user error. Here are some steps to help narrow down issues before reporting the problem to T&I. Finally, many problems can be resolved by thorough testing of materials before distribution – a little time spent up front can save a lot of effort down the road.


  1. Can the student(s) access the Container Manager site properly? If not, please contact T&I
  2. Is the student using the correct container? In addition to the containers designated for particular classes, NCShare maintains several generic containers used for demonstrations of single applications. Make sure your students know to only use the container named for your course, emphasizing that all containers are purpose-built for particular classes. Also, if they do accidentally do work in the wrong container, make sure they manually copy their work into the new container.
  3. Is the problem affecting multiple users?  If so, please contact T&I.
  4. Does the problem continue after a container restart? Have the user log into Container Manager and select the problem container from the My Reservations list, then under Container Controls click Request Restart. Note: This is not the same as restarting the browser or computer – neither of these will have any effect on the container.
  5. Does the failure still occur in a different instance of the container? Copy the data to your container (or, better yet, to your desktop or laptop with the software installed) and run it. If the failure remains, this points to a problem with the material. Review it closely.
  6. If the user brings a fresh copy of the problematic data into their container, does the failure still occur? If so, this points to a problem with the container. Contact T&I.
  7. Does the failure result in any error message or backtrace? If you get reproducible error messages, please include them in your email to the help desk.
Request Help