Good catch, @andreyrogojin! I'll check it out in the next few days.

P.S.: PRs are welcome, if you are interested. 😉

Sorry, guys. I'm stepping back from this one, for now.

The added complexities of maintaining both AMD64 and ARM64 scripts have proven too much to juggle right now.

I'm closing this case for the time being. If anyone else wants to take a crack at it, feel free to reopen and jump in.

And exclude ADD in the dockerfiles, using instead:
RUN --mount=type=bind,from=<path for all>/tmp,dst=/tmp,rw set -eux; cd /tmp; tar --extract ...
You won't need to download the installer for each tag and the size of the containers will decrease.

If I understand, you said to use wget before docker build.

Why not just use wget in the RUN command?

If I understand, you said to use wget before docker build.

Why not just use wget in the RUN command?

Because that would end up downloading the files inside the container again? 😉

The main challenge here is ensuring the bundle files are available when install.sh is executed, without occupying additional layer space. For this I tried two different strategies:

1. Multi-stage builds

Initially, I tried to avoid downloading files on the host and instead keep everything self-contained within the container image. To do this, I turned to multi-stage builds.

Unfortunately, this approach quickly hit a roadblock: Docker doesn't support "mounting" a folder from one build stage into another (you can only COPY files between stages). And that brings us right back to the original problem.

2. Download the files on host (@andreyrogojin OP idea)

Downloading all bundles in docker host first, and then using RUN --mount=type=bind on Dockerfile was the next attempt.

But this ended up causing additional build issues, while also complicating the build scripts and polluting the Docker host.

Ultimately, I decided that the ~10% increase in image size wasn't significant enough to justify the hassle.😅

Because that would end up downloading the files inside the container again?

If you download the file, extract, install and delete inside the same RUN command, it will not be stored as a layer.

If you download the file, extract, install and delete inside the same RUN command, it will not be stored as a layer.

Damn... why didn’t anyone ever tell me that before? 😂

Alright, I’ll give it another shot tonight. Appreciate the insight!

I gave it an initial try, but the image has actually increased in size. 😕

Let’s continue the discussion on #23.