Skip to content

Container-based development workflow

Container-based development workflow refers to the practice of establishing a development environment directly inside a software container, rather than relying solely on the local host machine^[400-devops-03-containerization-vscode-devcontainer.md].

Core Implementation

In this workflow, the operating environment (dependencies, tools, and runtimes) is contained within an isolated unit^[400-devops-03-containerization-vscode-devcontainer.md]. Code is typically not stored inside the container permanently; instead, it is managed on the local host and mounted into the container using a volume^[400-devops-03-containerization-vscode-devcontainer.md]. This allows the developer to use their local editor or filesystem while the code executes within the container's context.

Tools and Configuration

Tools like Visual Studio Code facilitate this workflow through extensions such as "Remote - Containers"^[400-devops-03-containerization-vscode-devcontainer.md]. Users can manage the lifecycle of their environment through command palette actions, such as Remote-Containers: Rebuild and Reopen in Container^[400-devops-03-containerization-vscode-devcontainer.md].

Configuration for these environments often relies on base images, such as those provided by community repositories like devcontainers/images on GitHub^[400-devops-03-containerization-vscode-devcontainer.md].

  • DevOps
  • [[Docker]]
  • [[VS Code]]

Sources

^[400-devops-03-containerization-vscode-devcontainer.md]