Explore >> Select a destination
|
You are here 
|
enix.io | ||
| | | | |
www.ardanlabs.com
|
|
| | | | | 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. | |
| | | | |
testdriven.io
|
|
| | | | | This article looks at several best practices to make your Dockerfiles and images cleaner, leaner, and more secure. | |
| | | | |
www.augmentedmind.de
|
|
| | | | | Learn to optimize the Docker image size, e.g. via small base images, multi-stage builds, consolidation of RUN statements, or using docker-slim. | |
| | | | |
ylan.segal-family.com
|
|
| | | I maintain a series of small unix scripts to make my daily usage more effective. I approach the development of these utilities like I do my other software: Use Outside-In Test-Driven Development. I use rspec to write my tests, even if the code itself is written in bash, zsh, or ruby. Let's see a few examples. Testing Output Some of my utilities are similar to pure functions: They always return the same output given for the same input, and they don't have side-effects (i.e. they don't change anything else... | ||
