distroless
dive
distroless | dive | |
---|---|---|
126 | 91 | |
19,806 | 49,314 | |
1.6% | 1.2% | |
9.1 | 4.2 | |
3 days ago | 7 months ago | |
Starlark | Go | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
distroless
-
Revisit base container image for AWS services
Debian slim and UBI are easy to use in the direction of creating a very small image while taking into account the use of a package manager, but on the other hand, they are too large to satisfy the demand to create a minimum image for a specific language environment. If you want to satisfy such a demand, Distroless image may be the right choice for you.
-
Base Images: The Secret to Smaller Docker Images
As Google, the creator of distroless images, puts it, "Distroless images contain only your application and its runtime dependencies." You can read more about them here.
- Distroless: Language focused Docker images, minus the operating system
-
Docker, Linux, Security. Kinda.
That's how we get distroless. Distroless base images follow the same pattern as alpine base docker images, as in, less functionality while still keeping enough functionality to be able to do the job and minimize the attack surface. Minimizing a base image like this means that the base images are very specialized so we have base images for golang, python, java and the like.
-
Chainguard Images now available on Docker Hub
lots of questions here regarding what this product is. I guess i can provide some information for the context, from a perspective of an outside contributor.
Chainguard Images is a set of hardened container images.
They were built by the original team that brought you Google's Distroless (https://github.com/GoogleContainerTools/distroless)
However, there were few problems with Distroless:
1. distroless were based on Debian - which in turn, limited to Debian's release cadence for fixing CVE.
2. distroless is using bazelbuild, which is not exactly easy to contrib, customize, etc...
3. distroless images are hard to extend.
Chainguard built a new "undistro" OS for container workload, named Wolfi, using their OSS projects like melange (for packaging pkgs) and apko (for building images).
The idea is (from my understanding) is that
1. You don't have to rely on upstream to cut a release. Chainguard will be doing that, with lots of automation & guardrails in placed. This allow them to fix vulnerabilties extremely fast.
- Language focused Docker images, minus the operating system
-
Using Alpine can make Python Docker builds 50Ă— slower
> If you have one image based on Ubuntu in your stack, you may as well base them all on Ubuntu, because you only need to download (and store!) the common base image once
This is only true if your infrastructure is static. If your infrastructure is highly elastic, image size has an impact on your time to scale up.
Of course, there are better choices than Alpine to optimize image size. Distroless (https://github.com/GoogleContainerTools/distroless) is a good example.
- Smaller and Safer Clojure Containers: Minimizing the Software Bill of Materials
-
Long Term Ownership of an Event-Driven System
The same as our code dependencies, container updates can include security patches and bug fixes and improvements. However, they can also include breaking changes and it is crucial you test them thoroughly before putting them into production. Wherever possible, I recommend using the distroless base image which will drastically reduce both your image size, your risk vector, and therefore your maintenance version going forward.
-
Minimizing Nuxt 3 Docker Images
# Use a large Node.js base image to build the application and name it "build" FROM node:18-alpine as build WORKDIR /app # Copy the package.json and package-lock.json files into the working directory before copying the rest of the files # This will cache the dependencies and speed up subsequent builds if the dependencies don't change COPY package*.json /app # You might want to use yarn or pnpm instead RUN npm install COPY . /app RUN npm run build # Instead of using a node:18-alpine image, we are using a distroless image. These are provided by google: https://github.com/GoogleContainerTools/distroless FROM gcr.io/distroless/nodejs:18 as prod WORKDIR /app # Copy the built application from the "build" image into the "prod" image COPY --from=build /app/.output /app/.output # Since this image only contains node.js, we do not need to specify the node command and simply pass the path to the index.mjs file! CMD ["/app/.output/server/index.mjs"]
dive
-
Show HN: Docker-phobia: Analyze Docker image size with a treemap
Cool, gonna try this soon. Would be great to use in combination with Dive (https://github.com/wagoodman/dive)
-
Mastering Docker Image Optimization: 6 Key Strategies for building Lighter, Faster, and Safer images
Dive is an open-source tool that allows you to explore the various layers of a Docker image. It shows you the content of each layer and helps you identify voluminous or unnecessary parts.
- Optimisation des images Docker: 6 Stratégies clés pour des images plus légeres et plus performantes
-
I reduced the size of my Docker image by 40% – Dockerizing shell scripts
Dive is a great tool for debugging this. I like image reduction work just because it gives me a chance to play with Dive: https://github.com/wagoodman/dive
One easy low hanging fruit I see a LOT for ballooning image sizes is people including the kitchen sink SDK/CLI for their cloud provider (like AWS or GCP), when they really only need 1/100 of that. The full versions of both of these tools are several hundred mb each
- Dive: A tool for exploring a Docker image, layer contents and more
- Dive – A tool for exploring each layer in a Docker image
- FLaNK Stack Weekly for 12 September 2023
-
Dive Into Docker part 4: Inspecting Docker Image
This post is going to be shorter. I'd like to highlight a tool that I really enjoy working with called "Dive" It is an essential tool when working to build and optimize docker containers.
-
Top 10 CLI Tools for DevOps Teams
Whether you work with Docker regularly or even create your own Docker containers, Dive is a great tool for streamlining image sizes, potentially helping you save storage costs and speed up deployments.
- Dive – exploring a Docker image, layer contents, and shrinking a image size
What are some alternatives?
iron-alpine - Hardened alpine linux baseimage for Docker.
lnav - Log file navigator
jib - 🏗 Build container images for your Java applications.
skopeo - Work with remote images registries - retrieving information, images, signing content
fpm - Effing package management! Build packages for multiple platforms (deb, rpm, etc) with great ease and sanity.
Whaler - Program to reverse Docker images into Dockerfiles
docker-alpine - Official Alpine Linux Docker image. Win at minimalism!
buildkit - concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit
dockerfiles - Various Dockerfiles I use on the desktop and on servers.
Lean and Mean Docker containers - Slim(toolkit): Don't change anything in your container image and minify it by up to 30x (and for compiled languages even more) making it secure too! (free and open source)
spring-boot-jib - This project is about Containerizing a Spring Boot Application With Jib
crun - A fast and lightweight fully featured OCI runtime and C library for running containers