Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does not properly launch container with image from devcontainer.json #5

Open
briancain opened this issue Apr 16, 2024 · 0 comments
Open
Labels
bug Something isn't working

Comments

@briancain
Copy link
Owner

briancain commented Apr 16, 2024

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?

@briancain briancain added the bug Something isn't working label Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant