Diese Website verwendet Cookies und ähnliche Technologien für Analyse- und Marketingzwecke. Durch Auswahl von Akzeptieren stimmen Sie der Nutzung zu, alternativ können Sie die Nutzung auch ablehnen. Details zur Verwendung Ihrer Daten finden Sie in unseren Datenschutz­hinweisen, dort können Sie Ihre Einstellungen auch jederzeit anpassen.


Dev Containers – The Future of Software Development Environments
Minuten Lesezeit
Dev Containers – The Future of Software Development Environments
Christoph Grothaus

Understanding Development Containers

In an industry driven by innovation and efficiency, Visual Studio Code Development Containers, or "Dev Containers" for short, have emerged as a key tool for modern software development. They are essentially isolated development environments housed within a container. They use the power of containerization technology, such as Docker, to create a consistent, reproducible, and portable development environment.

To enable a Dev Container setup for a given project, you need to add a few configuration files. Then any developer can launch the Dev Container on any machine or in the cloud and start developing, without having to perform manual setup steps such as getting dependencies or setting up a database. This works the same regardless of the programming language or tools used.

How They Work
  • Isolation: Each Dev Container operates independently, meaning the software, dependencies, and environment settings are isolated from the host system and other containers.
  • Consistency: By defining the development environment in code (e.g., Dockerfile or a configuration file), Dev Containers ensure that every team member works in an identical setup, regardless of their local machine. This also reduces the need for extensive setup documentation.
  • Flexibility: These containers can be customized to include necessary development tools, extensions, and dependencies, tailored to specific project needs.

Example: This diagram shows a developer working on three different projects, each using a different technology. Visual Studio Code and Docker are installed on the development machine. Inside Docker, the Dev Containers tooling creates an isolated container for each project.

Structure of a Dev Container setup
  • Streamlined Onboarding: New team members can get up and running quickly, without lengthy setup processes.
  • Cross-Platform Compatibility: Dev Containers can run on various operating systems, reducing OS-specific bugs.
  • Enhanced Collaboration: Teams can share and collaborate on environments easily, ensuring everyone is on the same page.
  • Cloud Development with GitHub Codespaces: Github offers a service called “Codespaces” that allows you to launch Dev Containers in the cloud. This enables developers to code from anywhere, on any device, without the need to set up and maintain a local development environment.
Dev Containers in the Software Development Industry

The adoption of Dev Containers is gaining momentum in the software development world. They are increasingly viewed as a solution to common development challenges like 'works on my machine' syndrome. Major tech companies and open-source projects are beginning to embrace Dev Containers for their benefits in collaboration, efficiency, and consistency.

Our Adoption of Dev Containers

At Zweitag, our journey with Dev Containers began as an exploration into enhancing our development process. We quickly recognized their potential in improving project setup times, fostering better collaboration, and ensuring consistency across our teams.

Our Experiences and Challenges

  • Early Adoption: Implementing Dev Containers in various projects using technologies such as Ruby, Elixir, Python, and Node.js, we noticed improvements in setup efficiency and a reduction in environment-related issues.
  • Overcoming Technical Hurdles: One of our notable challenges was integrating automated browser testing. This task tested the adaptability of Dev Containers but ultimately demonstrated their capability to handle diverse project requirements effectively.
  • Performance Considerations: We observed performance variations depending on the hardware. This observation led us to implement a dual approach, allowing the use of Dev Containers alongside traditional local setups. This strategy ensures that engineers using older hardware (such as Intel-based MacBooks) can develop efficiently and without hindrance.
Embracing Change for Future Success

Our journey with Dev Containers at Zweitag extends beyond mere adoption; it's a continuous process of learning, refining, and evolving. As we apply Dev Containers across various projects, we're actively gathering insights and feedback from our team members. This hands-on experience is crucial for fine-tuning our setup to meet the diverse needs of our projects and teams.

As we move forward, we're committed to initiating new projects with Dev Containers from the outset, while gradually transitioning existing projects during maintenance or updates. This approach is not just about streamlining current projects but is a strategic move towards future-proofing our development practices.

Embracing Dev Containers is a key part of our commitment to staying at the forefront of technology and process innovation. This approach ensures we remain agile and prepared for the evolving landscape of software development, continuously advancing towards efficiency and excellence.

You can soon read more on the technical aspects of our Dev Container setup, our principles in setting them up, and how we overcame the browser testing problem.

Are you looking for the right partner for your digital projects?

Let's talk.