Building container-based development environment with Visual Studio Code
tl;dr: You can use Docker and VS Code’s Remote Containers to containerize your local dev environment, speed up the onboarding process, use the same base image across all environments, provide the same editor tools to all developers, implement standards more easily, might not work for all.
One of the challenges when setting up the local develop ment environment for your team is ensuring that all developers have a setup that is either same or meets the requirements. The traditional approach to this problem is to lay down onboarding guidelines and expect developers to follow them. However, from version compatibility issues to individual’s experience to not using the right tools, there are varying hurdles to achieve uniformity in setting up the environment.
An alternative solution is a development environment pre-configured with all the required libraries and dependencies that developers can spin-off in a container. Developers can then work inside the isolated environment the container offers. This drastically minimizes the time a developer spends between cloning the codebase to begin working on it.
