I would be totally into a couple of Docker files for worker and Vespene configurations, or maybe even having a script that generates those Docker files to make it a little easier to customize (not sure if that is needed).
Most likely this could live in something like setup/docker and we could move the other setup stuff into setup/bash or something like that
Even if the Docker files reused those setup scripts to build the image (I think they should), we could also pass them flags to make them act a little differently. like if the environment variable "DOCKER_BUILD" was set, maybe it skips the systemd parts?
This way everybody still uses the same scripts, the Docker setup doesn't drift much and it just skips the systemd parts.
How does that sound?
I'm not super familiar with Docker to be the one that would build this, but I'm all for it and happy to help make it possible. I don't mind if the setup scripts get a little bit more conditional logic, but think it would be good if the Docker scripts can still share them.
Not quite sure how we ask about the best way to bake in database setup so those work the first time on launch?