Problem
Currently, Devboxes only allows configuring custom workspace images globally via Helm values.yaml or through GPU Profiles.
When developers want to quickly test or run an open-source project that already has a pre-built Docker image, they cannot easily pass --image <third-party-image> during devbox create. Running Docker-in-Docker (DinD) inside a devbox is not supported or recommended due to security/privilege risks and missing Docker daemon.
Proposed outcome
Allow developers to specify a custom workspace image when creating a devbox via CLI:
devbox create my-tryout --image ubuntu/nginx:latest
### Alternatives and tradeoffs
_No response_
### Project boundaries
- [x] I considered persistence, security, and Kubernetes portability.
Problem
Currently, Devboxes only allows configuring custom workspace images globally via Helm
values.yamlor through GPU Profiles.When developers want to quickly test or run an open-source project that already has a pre-built Docker image, they cannot easily pass
--image <third-party-image>duringdevbox create. Running Docker-in-Docker (DinD) inside a devbox is not supported or recommended due to security/privilege risks and missing Docker daemon.Proposed outcome
Allow developers to specify a custom workspace image when creating a devbox via CLI: