Skip to content

Fix pep-ppp-prod Java feature: switch JDK distro from ms to tem - #475

Closed
applegath-verily wants to merge 27 commits into
verily-src:masterfrom
applegath-verily:feature/applegath/pep-ppp-prod
Closed

Fix pep-ppp-prod Java feature: switch JDK distro from ms to tem#475
applegath-verily wants to merge 27 commits into
verily-src:masterfrom
applegath-verily:feature/applegath/pep-ppp-prod

Conversation

@applegath-verily

Copy link
Copy Markdown

Problem

The pep-ppp-prod devcontainer build fails during startup on every prod instance, so the app container is never produced and the app never reaches RUNNING. Observed across all three prod recreation attempts (06/10 → 06/11 → 08/25) in workspace ppp-prepep-consolidated-ws.

Startup log excerpt:

Check if OpenJDK is available for version 17 for ms Distro
JDK version 17 is available in ms...
JDK_DISTRO: ms
Version 17 not found. Available versions:

ERROR: Feature "Java (via SDKMAN!)" (Unknown) failed to install!

Root cause

The Java (via SDKMAN!) feature was pinned to version: "17" with the default jdkDistro: "ms" (Microsoft Build of OpenJDK). SDKMAN no longer resolves a bare 17 for the ms distro (Microsoft has wound down that build), so the feature install exits 1, docker-compose build app fails, and the devcontainer build aborts. Resource metrics during the build were clean (no OOM/disk pressure), and WSM/control-plane provisioned the VM successfully every time — the failure is entirely in the in-VM devcontainer build step.

Fix

Pin jdkDistro to Temurin (tem), the maintained Eclipse Adoptium LTS build, which resolves version 17 reliably.

     "ghcr.io/devcontainers/features/java:1.6.3": {
-      "version": "17"
+      "version": "17",
+      "jdkDistro": "tem"
     },

🤖 Generated with Claude Code

Drew Applegath and others added 27 commits May 14, 2026 12:29
…M and PyTorch pull their CUDA 12.8 compatible wheels together, ensuring the compiled vLLM extensions match the CUDA runtime
Based on the vllm/ollama E4B template, configured for the larger
Gemma 4 26B MoE model (4B active params, 18GB) targeting A100 GPUs.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Moved start-ollama.sh into postStartCommand so the model
auto-starts after VM stop/start cycles.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
… 8080, login default true)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…eatures)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The Java (via SDKMAN!) feature defaulted to the Microsoft Build of
OpenJDK (jdkDistro "ms"). SDKMAN no longer resolves a bare version
"17" for the "ms" distro (Microsoft has wound down that build), so
the feature install failed with "Version 17 not found", aborting the
devcontainer build on every prod instance.

Pin jdkDistro to Temurin ("tem"), the maintained Eclipse Adoptium
LTS build, which resolves version 17 reliably.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@applegath-verily
applegath-verily deleted the feature/applegath/pep-ppp-prod branch August 28, 2026 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant