The eight practices for Containerized Delivery on the Microsoft stack – PRACTICE 8: Environment-as-code pipeline and individual pipeline

This post is originally published as article within SDN Magazine on October 13th, 2017. During the past year I supported several clients in their journey toward Containerized Delivery on the Microsoft stack. In this blogseries I’d like to share eight practices I learned while practicing Containerized Delivery on the Microsoft stack using Docker, both in a Greenfield and in a Brownfield situation. In the last blogpost of this series I want to talk about Environment-as-code pipeline and individual pipelines.

The eight practices for Containerized Delivery on the Microsoft stack – PRACTICE 7: Explicit dependency management

This post is originally published as article within SDN Magazine on October 13th, 2017. During the past year I supported several clients in their journey toward Containerized Delivery on the Microsoft stack. In this blogseries I’d like to share eight practices I learned while practicing Containerized Delivery on the Microsoft stack using Docker, both in a Greenfield and in a Brownfield situation. In the seventh blogpost of this series I want to talk about Explicit Dependency Management.

The eight practices for Containerized Delivery on the Microsoft stack – PRACTICE 6: Dealing with secrets

This post is originally published as article within SDN Magazine on October 13th, 2017. During the past year I supported several clients in their journey toward Containerized Delivery on the Microsoft stack. In this blogseries I’d like to share eight practices I learned while practicing Containerized Delivery on the Microsoft stack using Docker, both in a Greenfield and in a Brownfield situation. In the sixth blogpost of this series I want to talk about Dealing with secrets.

The eight practices for Containerized Delivery on the Microsoft stack – PRACTICE 5: Secure Containerized Delivery

This post is originally published as article within SDN Magazine on October 13th, 2017. During the past year I supported several clients in their journey toward Containerized Delivery on the Microsoft stack. In this blogseries I’d like to share eight practices I learned while practicing Containerized Delivery on the Microsoft stack using Docker, both in a Greenfield and in a Brownfield situation. In the fifth blogpost of this series I want to talk about Secure Containerized Delivery. PRACTICE 5: Secure Containerized Delivery Securing your container infrastructure and deployments is an important aspect of Containerized Delivery. There are a lot of aspects to keep in mind here, so I will highlight the most important ones. Harden your images, containers, daemons and hostsWhen you set up your containerized infrastructure, it is important that you harden your infrastructure elements against threats. To help you with this, the Center for Internet Security has published a Docker benchmark that includes configuration and hardening guidelines for containers,

The eight practices for Containerized Delivery on the Microsoft stack – PRACTICE 4: Group Managed Service Accounts

This post is originally published as article within SDN Magazine on October 13th, 2017. During the past year I supported several clients in their journey toward Containerized Delivery on the Microsoft stack. In this blogseries I’d like to share eight practices I learned while practicing Containerized Delivery on the Microsoft stack using Docker, both in a Greenfield and in a Brownfield situation. In the fourth blogpost of this series I want to talk about Group Managed Service Accounts.

The eight practices for Containerized Delivery on the Microsoft stack – PRACTICE 3: Keep your Windows Containers up-to-date

This post is originally published as article within SDN Magazine on October 13th, 2017. During the past year I supported several clients in their journey toward Containerized Delivery on the Microsoft stack. In this blogseries I’d like to share eight practices I learned while practicing Containerized Delivery on the Microsoft stack using Docker, both in a Greenfield and in a Brownfield situation. In the third blogpost of this series I want to talk about Keeping your Windows Containers up-to-date.

The eight practices for Containerized Delivery on the Microsoft stack – PRACTICE 2: Multi-stage builds

This post is originally published as article within SDN Magazine on October 13th, 2017. During the past year I supported several clients in their journey toward Containerized Delivery on the Microsoft stack. In this blogseries I’d like to share eight practices I learned while practicing Containerized Delivery on the Microsoft stack using Docker, both in a Greenfield and in a Brownfield situation. In the second blogpost of this series I want to talk about Multi-stage builds.

The eight practices for Containerized Delivery on the Microsoft stack – PRACTICE 1: Small, reusable image layers

This post is originally published as article within SDN Magazine on October 13th, 2017. During the past year I supported several clients in their journey toward Containerized Delivery on the Microsoft stack. In this blogseries I’d like to share the eight practices I learned while practicing Containerized Delivery on the Microsoft stack using Docker, both in a Greenfield and in a Brownfield situation. In the first blogpost of this series I want to talk about the first practice: Small and reusable image layers.

Windows Containers – What is it and why should we care?

This post is originally published as article within SDN Magazine on February 28th, 2017. One of the hot topics within the Microsoft development community right now is undoubtedly the “container” topic. Following the success of both Docker and containers on Linux, Microsoft developed a Windows container implementation on Windows Server 2016 and Windows 10. After two and a half years of development plus one year of running this container technology in preview for insiders (Windows Server 2016 TP3 – TP5), September of 2016 finally saw Microsoft’s announcement that it had released Windows Server 2016 to the public. While the container technology and Containerized Delivery have been used by non-Microsoft focused enterprises for a few years now (Linux has had its container technology since August 2008), the Microsoft community is only at the beginning of this new journey. This is, therefore, the perfect moment to ask ourselves whether we should care about Windows containers, and whether we should look

Deep dive into Windows Server Containers and Docker – Part 3 – Underlying implementation of Hyper-V Containers

Last April I visited DockerCon 2017 and while they announced many new great things like the LinuxKit and the Moby Project, one of the most appealing announcements for me definitely was the announcement of John Gossman that Microsoft and Docker made it possible to run Linux containers natively on Windows Hosts by using the same Hyper-V isolation layer as Hyper-V containers. So, time for me to create a blogpost about Hyper-V containers and to explain how this Hyper-V container virtualization layer works. In the previous blogpost of this series, we learned about the difference between containers and VMs and even Windows and Linux containers. Where Linux hosts only support one type of containers: Linux containers, Windows hosts do support multiple container types like Windows Server containers, Hyper-V containers and even Linux containers. Let’s dive into the Hyper-V container technology. Normal Windows Server Containers Even though normal Windows Server Containers have great benefits like instant-startup times