docs: clarify GPU detection uses separate container in journal

Updated journal entry #16 to specify nvidia/cuda container spawning.
Version bump: 3.3.2 -> 3.3.3
This commit is contained in:
stellarshenson
2025-12-04 19:10:37 +01:00
parent dea9e75fbb
commit 25efd91bb6
2 changed files with 2 additions and 2 deletions

View File

@@ -50,4 +50,4 @@ This journal tracks substantive work on documents, diagrams, and documentation c
**Result**: Changed watchtower image from containrrr/watchtower:latest to nickfedor/watchtower:latest in compose.yml, new image is actively maintained and compatible with latest Docker versions, bumped version to 3.3.1
16. **Task - Cleanup startup scripts**: Removed obsolete nvidia-smi script and renumbered ensure_groups<br>
**Result**: Deleted 01_nvidia-smi.sh (GPU detection handled in jupyterhub_config.py), renamed 02_ensure_groups.py to 01_ensure_groups.py for sequential ordering, bumped version to 3.3.2
**Result**: Deleted 01_nvidia-smi.sh (GPU detection now uses separate nvidia/cuda container spawned by jupyterhub_config.py), renamed 02_ensure_groups.py to 01_ensure_groups.py for sequential ordering, bumped version to 3.3.2

View File

@@ -3,7 +3,7 @@ PROJECT_NAME="stellars-jupyterhub-ds"
PROJECT_DESCRIPTION="Multi-user JupyterHub 4 deployment platform with data science stack, GPU auto-detection, NativeAuthenticator, and isolated per-user environments spawned via DockerSpawner"
# Version
VERSION="3.3.2_cuda-12.9.1_jh-5.4.2"
VERSION="3.3.3_cuda-12.9.1_jh-5.4.2"
VERSION_COMMENT="Updated watchtower to maintained fork (nickfedor/watchtower), configuration-agnostic volume management, admin notification broadcast, privileged user docker.sock access"
RELEASE_TAG="RELEASE_3.2.11"
RELEASE_DATE="2025-11-09"