Versioning of DigitalOcean 1-Click Docker Marketplace Image (Recipes)

I like to use the 1-Click Docker image provided by DO, however it is very important to me that I be able to programmatically reproduce infrastructure.

For example, the current version configures a default UFW firewall and installs Docker Compose 1.22.0.

I noticed for example the current version can barely run docker compose on a standard DO droplet because the entropy is too low. Docker has an 8 year old article on this problem here.

It seems like haveged should to be installed by default, or that the documentation on the marketplace item should include a note about why docker-compose might hang on a smaller VPS instance.

There doesn’t seem to be a way to provide feedback on documentation or the current image. The link takes you over to the docker forums in general, which don’t have a meaningful thread about the Digital Ocean image that I can see.

It would be great to use the same recipe offered by DO right now in the image but add the haveged line or any other items. Really, to be explicit about the configuration people should know exactly what the 1-click image is made up of procedurally.

I saw this previous answer from DO Staff recommending the cloning of marketplace images in order to keep a copy of something, but that doesn’t seem like a reasonable way to conduct devops.

Where does DO provide the script used for building these images? How is DO managing versions managed between the scripts? Would you consider making these scripts public and versioned so that people can create issues and pull requests and otherwise understand decisions about what went into them?