Skip to content

[Verda] Fix provisioning by switching to current OS images - #4507

Merged
peterschmidt85 merged 1 commit into
masterfrom
issue_4506_verda_os_images
Nov 20, 2026
Merged

peterschmidt85 merged 1 commit into
masterfrom
issue_4506_verda_os_images

Conversation

@peterschmidt85

Copy link
Copy Markdown
Contributor

Verda instances failed to provision with NO_OFFERS because Verda removed the two OS images that dstack booted them from.

  • All instances except V100 now boot from Verda's current Ubuntu 24.04 + CUDA 13.0 + Docker image.
  • V100 instances boot from Verda's V100 image (Ubuntu 24.04 + CUDA 12.9, proprietary driver).
  • A6000 instances no longer use a separate image.

Fixes #4506.

🤖 Generated with Claude Code

Verda removed the two OS images hardcoded in `_get_vm_image_id`, so every
instance launch was rejected. Use the current Ubuntu 24.04 + CUDA 13.0 +
Docker image by default and the V100 image for V100. A6000 no longer needs
a separate image.

Fixes #4506

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@peterschmidt85
peterschmidt85 merged commit 78ad042 into master Nov 20, 2026
26 checks passed
@peterschmidt85
peterschmidt85 deleted the issue_4506_verda_os_images branch November 20, 2026 17:43
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.

[Bug]: Verda backend cannot provision any instance (CPU or GPU): both hardcoded OS images were retired

1 participant