Vultr
This update introduces initial integration with Vultr. This cloud provider offers a diverse range of NVIDIA and AMD accelerators, from cost-effective fractional GPUs to multi-GPU bare-metal hosts.
$ dstack apply -f examples/.dstack.yml
# BACKEND REGION RESOURCES PRICE
1 vultr ewr 2xCPU, 8GB, 1xA16 (2GB), 50.0GB (disk) $0.059
2 vultr ewr 1xCPU, 5GB, 1xA40 (2GB), 90.0GB (disk) $0.075
3 vultr ewr 1xCPU, 6GB, 1xA100 (4GB), 70.0GB (disk) $0.123
...
18 vultr ewr 32xCPU, 375GB, 2xL40S (48GB), 2200.0GB (disk) $3.342
19 vultr ewr 24xCPU, 240GB, 2xA100 (80GB), 1400.0GB (disk) $4.795
20 vultr ewr 96xCPU, 960GB, 16xA16 (16GB), 1700.0GB (disk) $7.534
21 vultr ewr 96xCPU, 1024GB, 4xA100 (80GB), 450.0GB (disk) $9.589See the docs for detailed instructions on configuring the vultr backend.
Note
This release includes all dstack features except support for volumes and clusters. These features will be added in an upcoming update.
Vast.ai
Previously, the vastai backend only allowed using Docker images where root is the default user. This limitation has been removed, so you can now run NVIDIA NIM or any other image regardless of the user.
Backward compatibility
If you are going to configure the vultr backend, make sure you update all your dstack CLI and API clients to the latest version. Clients prior to 0.18.35 will not work when Vultr is configured.
What's changed
- [
dstack-shim] Revamp logging and CLI by @un-def in #2176 - Download
dstack-runnerto a well-known location by @un-def in #2179 - Add Vultr Support by @Bihan in #2132
- Support non-root Docker images in Vast.ai by @jvstme in #2185
- Refactor idle instance termination by @jvstme in #2188
- Retry instance termination in case of errors by @jvstme in #2190
- Update PyPI Development Status classifier by @jvstme in #2192
- Add Vultr to
ConceptsandReferencepages by @Bihan in #2186
Full changelog: 0.18.34...0.18.35
