Would you kindly share how to do it?

Wait... this whole time reading this thread, I'm racking my brain for what bitnami provided (I used to use them before docker came around. I never would have got Redmine up and going without them -- the install seemed so foreign.) that building a docker image couldn't, because surely everyone knows how to build one from scratch, right?... right?

Is all the panic because everyone is trying to avoid learning how to actually install the pieces of software (once), and their magic (free) black boxes are going away?

I recommend VS Code remote connections and docker builds via the docker extension to do rapid build-run-redo. Remember to make sure it works from scratch each time. You can automate them with Jenkins... (which came first, the Jenkins or the Jenkins Docker image?) I also recommend Platform One. (you'll need a smart card) I also recommend reading the particular software's documentation ;)

To add, it's really satisfying to build your own, push it and host it on your own internal repo that anyone in your group can use.

"Just go get the DEV image, Josh."

Not OP, but in general the process goes like this:

  - you pick a base image you want to use, like Alpine (small size, good security, sometimes compatibility issues) or Debian or Ubuntu LTS (medium size, okay security, good compatibility) or whatever you please
  - if you want a common base image for whatever you're building, you can add some tools on top of it, configuration, CAs or maybe use a specific shell; not a must but can be nice to have and leads to layer reuse
  - you build the image like you would any other, upload it wherever you please (be it Docker Hub, another registry, possibly something self-hosted like Sonatype Nexus): docker build -t "my-registry.com/base/ubuntu" -f "ubuntu.Dockerfile" . && docker push "my-registry.com/base/ubuntu"
  - then, when you're building something more specific, like a Python or JDK image or whatever, you base it on the common image, like: FROM my-registry.com/base/ubuntu
  - the same applies not just for language tooling and runtimes, but also for software like databases and key value stores and so on, albeit you'll need to figure out how to configure them better
  - as for any software you want to build, you also base it on your common images then

  FROM ubuntu:noble
  
  ... (your custom configuration here, default time zones, shells etc.)
  
  RUN apt-get update \
      && apt-get upgrade -y \
      && apt-get install -y \
          curl \
          wget \
          net-tools \
          traceroute \
          iputils-ping \
          zip \
          unzip \
      && apt-get clean \
      && apt-get autoremove -y --purge \
      && rm -rf /var/lib/apt/lists/*

  upstream image --> your own common base image --> your own PostgreSQL image
  upstream image --> your own common base image --> your own OpenJDK image --> your own Java application image