Yes, it appears so. I can paste screenshots from dive when I'm back at my workstation.

With a little help from ChatGPT to save time, this is better because:

Ah, yes — this is a classic Docker gotcha 🙂

When you run something like:
COPY file.txt /app/
RUN chown myuser:mygroup /app/file.txt
you often see the image size increase a lot, sometimes surprisingly so.

Here’s why:

1. Docker builds images layer by layer

Each instruction (COPY, RUN, etc.) creates a new layer.

Layers are immutable — a RUN chown does not "change" the previous file, it creates a new layer with a new copy of that file with different ownership.

That means you now have two copies of the file in the image layers:

One owned by root:root from the COPY layer.

Another owned by myuser:mygroup from the chown layer.

Even though at runtime you only see the "topmost" version, both exist in the layer stack → more disk space.

Thanks for the review, @GiedriusS! The Thanos binary is still huge and contributes to 99% of the image size. Any idea why? Anything we can do to reduce the size of the binary while not breaking stuff?