Replies: 1 comment 1 reply
-
Hey @hellt, we've fixed the multi devcontainer detection and it'll be working again with the next release. It's opt-in because we need to clone the repository before we can start looking for devcontainer.jsons and this might take a couple of seconds. Specifying the devcontainer.json through |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all,
first of all, thanks for a great product/project.
I wonder, is there a nice way to give a user a choice of which dev container file to use when they build a workspace from a folder/repo?
We keep several devcontainer files under nested dirs, in the following layout:
I was hoping that this setting would work
but it does not probably look into the nested directories.
Mayb if it is a lot of work to have a dialog to open up a certain devcontainer file, then maybe we could have an option added to the URL interceptor so that we can encode which path to use for the devcontainer like this:
(codespaces does it
https://codespaces.new/srl-labs/srl-snmp-framework-lab?quickstart=1&devcontainer_path=.devcontainer%2Fdocker-in-docker%2Fdevcontainer.json
)Beta Was this translation helpful? Give feedback.
All reactions