Jerome Petazzoni on

Docker Images : Part III - Going Farther To Reduce Image Size

Fri, 03 Apr 2020 00:00:00 +0000

Series Index

Reducing Image Size
Details Specific To Different Languages
Going Farther To Reduce Image Size

Introduction

In the first two parts of this series, we covered the most common methods to optimize Docker image size. We saw how multi-stage builds, combined with Alpine-based images, and sometimes static builds, would generally give us the most dramatic savings. In this last part, we will see how to go even farther. We will talk about standardizing base images, stripping binaries, assets optimization, and other build systems or add-ons like DockerSlim or Bazel, as well as the NixOS distribution.

Docker Images : Part II - Details Specific To Different Languages

Mon, 24 Feb 2020 00:00:00 +0000

Series Index

Reducing Image Size
Details Specific To Different Languages
Going Farther To Reduce Image Size

Introduction

In the first part, we introduced multi-stage builds, static and dynamic linking, and briefly mentioned Alpine. In this second part, we are going to dive into some details specific to Go. Then we will talk more about Alpine, because it’s worth it; and finally we will see how things play out with other languages like Java, Node, Python, Ruby, and Rust.

Docker Images : Part I - Reducing Image Size

Tue, 04 Feb 2020 00:00:00 +0000

Series Index

Reducing Image Size
Details Specific To Different Languages
Going Farther To Reduce Image Size

Introduction

When getting started with containers, it’s pretty easy to be shocked by the size of the images that we build. We’re going to review a number of techniques to reduce image size, without sacrificing developers’ and ops’ convenience. In this first part, we will talk about multi-stage builds, because that’s where anyone should start if they want to reduce the size of their images. We will also explain the differences between static and dynamic linking, as well as why we should care about that. This will be the occasion to introduce Alpine.

Why is DevOps Important?

Mon, 26 Aug 2019 00:00:00 +0000

1. What are four keys for great DevOps?

Collaboration: DevOps requires collaboration, both within teams and between teams. Good communication between teams implies to break down silos, which can be harder than it sounds in organizations where a leader and their team are rewarded for individual achievements, discouraging them from collaborating and sharing information with others, and often encouraging politics at the expense of the company’s success.

Blameless Culture: It also requires to internalize that we learn from our failures. Instead of promoting a culture where mistakes can seriously hinder one’s career and are therefore often shoved under the rug, we need to embrace a blameless culture where each failure becomes an opportunity to improve, and improve continuously.