What happened?
brian@brian-LNQ0KYW6HD:devpod-provider-nomad λ docker ps -a ±[main]
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
15b1ef470ea1 alpine "sleep infinity" 3 minutes ago Up 3 minutes devpod-258d6de8-12e9-3064-a81f-c92fb7dc9cd6
brian@brian-LNQ0KYW6HD:devpod-provider-nomad λ cat .devcontainer.json ±[main]
{"image":"mcr.microsoft.com/devcontainers/go","build":{}}
The create command doesn't seem to be able to load the driver configuration from Devpod, so it launches with the default command and image rather than reading from devcontainer.json
What did you expect to happen instead?
Use the image defined in the devcontainer.
How can we reproduce the bug? (as minimally and precisely as possible)
My devcontainer.json:
{"image":"mcr.microsoft.com/devcontainers/go","build":{}}
Local Environment:
- DevPod Version: [use
devpod version]
- Operating System: windows | linux | mac
- ARCH of the OS: AMD64 | ARM64 | i386
- Nomad version [use
nomad version]
DevPod Provider:
- Custom provider: provide imported
provider.yaml config file
Anything else we need to know?
What happened?
The create command doesn't seem to be able to load the driver configuration from Devpod, so it launches with the default command and image rather than reading from devcontainer.json
What did you expect to happen instead?
Use the image defined in the devcontainer.
How can we reproduce the bug? (as minimally and precisely as possible)
My
devcontainer.json:Local Environment:
devpod version]nomad version]DevPod Provider:
provider.yamlconfig fileAnything else we need to know?