3 ms·
I do not know why someone shared this repo, there is nothing special about it other than containing some start templates. I would start here for understanding D
by markphip 3y ago
I do not know why someone shared this repo, there is nothing special about it other than containing some start templates. I would start here for understanding Dev Containers: https://containers.dev https://containers.dev
If you have a scenario where using a container as your development environment makes sense, this is some tooling that can improve the developer experience vs just using plain Docker and Docker Compose.
- politelemon 3y agoIs it possible to debug code inside a 'devcontainer' environment? Does devcontainers actually run VSCode as a server in the container?
- markphip 3y agoYes to both questions. This is essentially how Codespaces works too, fwiw.
- johnchristopher 3y agoI usually put my code into a volume and use bindfs to read/write that volume from the host as a regular user (with vscode, vim, whatever). It prevents ownership conflicts since files in the volumes are owned by root/www-data/whoever. VScode can be configured with a mapping between running code in the container and accessible code in the host so xdebug breakpoints are set on the host in vscode and when xdebug calls back vscode it gets xdebug data and displays it on the host. Would codespace solve that more elegantly ?
- pc86 3y agoI don't know what "run VSCode as a server" is supposed to mean in this context, but there are other comments in this page that suggest the integration between dev containers and vscode is pretty good, e.g. opening a terminal is just scoped to that container by default, etc.