-1. Regarding tools/features, the official docs link is correct. https://code.visualstudio.com/docs/devcontainers/create-dev-container#_install-additional-software They should be in the 'customizations' section of the Dockerfile. That way, when you share your devcontainer (and Dockerfile), everything gets shared correctly. -2. When using multiple softwares (e.g. Deno, PostgreSQL), you can use a single container, or multiple. However, single containers with everything in them is ideal as it maintains consistency across the application stack. In the case of multiple containers, you'll need to share each of the 'devcontainer' setups as well. The one advantage I see here is that if I want to use a single PostgreSQL instance across multiple applications, this is better, since my backups etc. contain the data of all applications. However, this requires extra fiddling to get everything working across containers. Have a look at the Microsoft DevContainers Templates at their Github repository - https://github.com/devcontainers/templates You will see examples of single as well as multiple containers. -3. The setup with the 'devcontainers' directory ideally should contain everything for a another developer to have an identical environment as yours. The application code doesn't need to be shared. Hope all this helps. All the best. More on reddit.com

Heyo! I've been using devcontainers and remote-containers for VS code since early beta, it is amazing and worth it. Here are a few tips: The Dockerfile for your devcontainer isn't your production Dockerfile if you have / need one. They could be similar, but they serve very different purposes. If you expect developers to be building and using docker images, consider having your devcontainer use docker-in-docker so people can attach to your devcontainer and run docker commands or docker-compose commands from there. The Dockerfile for your devcontainer specifies the static portions of the environment, the devcontainer.json is used for the more dynamic or VSCode specific parts like environment variables, post-creation actions (I use this to install do a pip install of my project dev-deps), and commonly used extensions. Treat devcontainers as the common starting point for every developer in your company. Don't try to cram everything you could ever want to need into the dev container, use it to only handle that parts that suit everybody, or at least the parts your company is willing to standardize. Leave room for your developers to each individually extend it to meet their own requirements such as using the extensions they want, choosing the theme they want, or installing their own tools in it. Don't require that everyone on your team use the devcontainer. A devcontainer shouldn't be a replacement for a local development environment, it is a replacement for not knowing how to build your own local development environment or not wanting to. And now to answer your more specific questions: I recommend using the Microsoft built-in images as base images. Just use the vscode command to create a new template and customize it as needed. Put your environment variables, commonly used extensions (ansible?), and to install any tools that are likely to change throughout your project such as development dependencies. You can also set up mount-points for developer-specific configurations such as secrets, keys, and tokens. Here is a template for a new python project I started where I'm making very heavy use of devcontainers, vscode extensions and various configurations, and a few other things that I think you could use for inspiration: https://github.com/tclasen/template-python Note that the standard / specification for "VSCode DevContainers" is also mostly compatible with "GitHub CodeSpaces". But there is also a completely different standard / specification that isn't compatible for "Docker-Desktop Dev Environments" that might also be worth looking into. Both are basically the same thing as were designed to make it so you could just pick up your development environment and ship it as a reproducible artifact to hand to any new developer to your team and reduce on-board from weeks long with a set of instructions to minutes long with the requirement they have docker and vscode installed. Huge win in my book. More on reddit.com

More sources with the same issue: https://github.com/devcontainers/cli/issues/281 More on reddit.com

Nice Work! I am super excited to see how things like this progress once Neovim truly gets into a Client-Server model :)

More on reddit.com