Vscode-remote-release: Multiple container config
I have two suggestions based on my use-case:
- Running a command after the container is created is possible with
postCreateCommand, it would be nice to have apreCreateCommandto run commands before the container is created. - Support multiple configurations in
devcontainer.jsonand allow the user to pick which one to run. Similar to the request in #2067 but I think it should more generic instead of OS-specific only.
If I missed something and there are solutions to these problems (or workarounds) please share.
davidtvs
All 6 comments
preCreateCommand is tracked with #1045. Let's track the multiple configs here. (It's best to file individual feature requests in separate issues.)
chrmarti
on 4 Feb 2020
Supporting multiple devcontainers would be HUGE. When multiple definitions are found, selecting re-open in container should then prompt you to pick one of the container definitions. This would help with developing/testing/debugging code on different versions of linux (not all products are deployed in docker). If a docker.host field can also be added to the config, it would also be great for developing code for embedded platforms like a tegra. The code can be developed on a desktop, and then you can switch to the aarch64 container and run it in that container over SSH on the actual hardware. Currently to do that you need to replace your devcontainer and enter the IP in settings.json.
ahoenig1
on 12 Mar 2020
A frequent use case for multiple containers Is generally GPU/CPU separate images.
bhack
on 17 Mar 2020
Thanks for opening this thread! It appears to be along the lines of https://github.com/microsoft/vscode-remote-release/issues/1165. While 1165 focuses on different versions of Python in its explanation, I think the overarching point still stands: being able to choose a certain container config from a set of possible configurations when opening your code in a container.
I think it'd make sense to migrate to that thread to consolidate our discussion- if that grouping sounds alright with folks in this thread too, I'll go ahead and close this issue to avoid dupes.
bamurtaugh
on 22 Oct 2020
@bamurtaugh Ok can you summarize this thread there?
bhack
on 22 Oct 2020
@bhack Yes, I'm happy to summarize this thread in #1165! I'll do so now and then close out this issue. Please let me know if you have any other feedback or questions, and also feel free to reply in that thread as well.
bamurtaugh
on 23 Oct 2020
Related issues
grzegorz-silarski
路
3Comments
nphmuller
路
3Comments
gurdevrana
路
3Comments
peterkappelt
路
3Comments
kieferrm
路
3Comments
Most helpful comment
Supporting multiple devcontainers would be HUGE. When multiple definitions are found, selecting re-open in container should then prompt you to pick one of the container definitions. This would help with developing/testing/debugging code on different versions of linux (not all products are deployed in docker). If a docker.host field can also be added to the config, it would also be great for developing code for embedded platforms like a tegra. The code can be developed on a desktop, and then you can switch to the aarch64 container and run it in that container over SSH on the actual hardware. Currently to do that you need to replace your devcontainer and enter the IP in settings.json.