I'm building a custom devcontainers file and need to add a couple of homebrew packages. In the features list, there's a homebrew-package that does the job. The only problem is, this only accepts one More on stackoverflow.com

For your devcontainers your Dockerfile shouldn't typically execute anything. If you need running processes in your environment (example: a database), then you should consider using devcontainer with a docker-compose file. Otherwise, your goal is simply to build/install your dev environment dependencies. You also likely won't have to copy anything in your Dockerfile as your current directory will automatically be mounted by your devcontainer. In your case, I believe all you need is to install scala and spark (although I'm not familiar spark so not sure if more is required. You can either install them normally via the Dockerfile, or use devcontainer features (my prefferred method!). With devcontainer features, your Dockerfile could actually be empty aside from one single line: FROM whatever:whatever 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

Do you clone the repository into the windows file system? If you do, try cloning it inside wsl, to use the linux file system directly. More on reddit.com