You do something like this:
./launcher bootstrap myimage
# the command that pushes that image to your preferred place to launch images
./launcher start-cmd
and that gives you the ENV variables you need to set to launch your image.
It’s really not that hard. You can even get it integrated into a github action so that it will build your image and push it to your docker-repo thingy. Looking at the commits to docker_compose, it looks like there are moves afoot to produce an image that doesn’t need to be bootstrapped, or at least make it easier to have it do some of the required stuff (migrate the database, precompile assets and push to s3 and so on). I’ve done this for clients who wanted to use k8s or AWS image-launcher-thingy (I can’t remember its name).
A few times I’ve considered offering such pre-built images as a service, but never found anyone who wanted to pay for such.
But there are a bunch of little pieces. Best I can tell CDCK uses launcher to build images, but they launch and manage them with other tools, just like you want to. And when they started, docker-compose wasn’t yet a decent way to do that and by the time it was, they had already made launcher work, so finding a way to migrate everyone from launcher to something else wasn’t really an option.
If the bitnami images work for you, then use them, but if they don’t, you’ll need to get help from someone who uses them, which is mostly nobody here.