Classroom: dedicate first session to setup + troubleshooting FAQ

[cuihtlauac]

Parent issue: #24

Problem (from UCSD study, Valstar et al., ITiCSE 2020)

The instructional team recommended "we should have devoted more attention to helping students set up their DevContainer in the beginning of the term in order to prevent questions." 64% of TAs reported helping many students with setup.

Students also reported a recurring issue: "the DevContainer constantly gives a popup saying 'reconnecting' and VSCode freezes until it disappears." This kind of issue is hard to debug without a FAQ.

Despite the initial barrier, Piazza forum analysis showed fewer DevContainer-related posts (98) than Linux server posts (108), even though more students used DevContainers. Setup help front-loaded in week 1 reduces ongoing support load.

Proposed changes

• Add a docs/troubleshooting.md covering:
  • Docker not starting (daemon not running, WSL2 issues on Windows)
  • VS Code "reconnecting" popup (increase Docker memory allocation)
  • Container runs slowly (check Docker resource limits in Docker Desktop settings)
  • "No space left on device" (Docker disk image full, prune unused images)
  • Permission issues (user mismatch between host and container)
• Add instructor guidance in classroom setup docs (Document classroom management tools for training sessions #23): dedicate the first 30-60 minutes of the first session to Docker + devcontainer setup with TAs available for troubleshooting
• Consider a test/test-health.sh script students can run to verify their environment is working