Support for JetBrains IDEs in Dev Container #1514
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, support for Dev Containers in the project is exclusively oriented towards users of the vscode editor, which does not allow for development in an IDE.
Specifically, the devcontainer metadata contains proprietary commands that are only compatible with VSCode.
The devcontainer.json also uses bind, which is not compatible with using the project on remote Docker servers (in this case, docker volumes should be used, as one cannot assume that the host is always exclusively owned by the user).
To address this, subfolders for jetbrains and vscode were created (fully in accordance with the containers.dev specification). In the jetbrains folder, all specified scenarios have been corrected.
The vscode folder retains the original configuration.
When building a devcontainer, both IntelliJ IDEA 2024.1 and vscode can, in the case of multiple devcontainer.json files in the project, ask the user which metadata file to use, thus editor users will choose VSCode, while IDE users will opt for IntelliJ IDEA.