Create devcontainer.json manually by selecting a language

[shanehughes1990]

Is your feature request related to a problem?
Yes

Which solution do you suggest?
We have many many repos at this point, all of which don't have devcontainer.json file in it. it would be nice once you pick your local repo as the workspace dir, if you were also able to pick from the templates to create the devcontainer.json file in the existing repo if one is not present. Currently nothing happens you have to look through logs to find out that the workspace is erroring due to missing json file.

Which alternative solutions exist?

Additional context

[pascalbreuninger]

Hi @shanehughes1990, thanks for opening an issue. Not sure I completely understand what you're trying to do. DevPod usually falls back to a generic image if it can't detect a devcontainer.json

[shanehughes1990]

For reference my repo is a README at the root and folders of terraform files under it.

When I attempt to create a devpod using that directory as the workspace path I get this

Been spinning now for 10+ minutes, I can't remember for the life of me where I found the logs file (windows 11), but the workspace never actually gets created here, I can fix it if I put a devcontainer json in the root with nothing more than an image to pull but I would want to to default to a basic container like you imply.

[shanehughes1990]

What I hope to accomplish is to be able to open the repo without any devcontainer config in it. and update the spec in the workspace itself right now I have to open my repo outside of devpod do the json config then add the workspace.

[pascalbreuninger]

Oh, I just saw you're using version 0.4.0-14 but that's incompatible with 0.3.7 because of internal DevPod <-> Agent communication changes. Could you try to use 0.3.7 and see if that solves your issue?

[shanehughes1990]

I was on latest pre-release because I wanted the open in vscode button to work 😆, the results
of 3.0.7, same thing you can see no devcontainer json gets created and devpod just spins.

[pascalbreuninger]

@shanehughes1990 should be fixed by #813 , will be included in next release