compiling-containers VS dive

A cool thing about Buildkits LLB is that you can write your own front end to BuildKit. At Earthly, this is sort of a starter task for everyone who joins the team.

My frontend was based on intercal and I don't recommend anyone use it[1].

Buildkit functions a bit like a compiler. I wrote an article once about how it all works. [2]

[1]: https://github.com/adamgordonbell/compiling-containers/tree/...

[2]: https://www.docker.com/blog/compiling-containers-dockerfiles...

Earthly is great (disclosure: work on it)

But also checkout out IckFiles, an Intercal frontend for moby buildkit:

https://github.com/adamgordonbell/compiling-containers/tree/...

Hi, I wrote this, thank you for submitting it. I was trying to teach a bit about compilers and container images at the same time and share some working code examples. The code samples are here and here.

Cool, gonna try this soon. Would be great to use in combination with Dive (https://github.com/wagoodman/dive)

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.

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

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.

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.