Support (or document) starting from official Docker images about tugboat-registry HOT 4 CLOSED

Resolved by:

• https://github.com/Lullabot/tugboat/pull/2416
• https://github.com/TugboatQA/images
• https://hub.docker.com/u/tugboatqa/

from tugboat-registry.

Here is one idea for a workaround: moby/moby#3465 (comment)

It'd be interesting to see what would happen with some of them that start from CentOS or other Linux flavors.

from tugboat-registry.

This actually came up while I was just demo'ing Tugboat to a client.
We use Docker for our local and we have been maintaining our own images. When they saw Tugboat was using apache-php7-drupal and mysql they asked if those were the public images, and if so then we can just use those for our local docker builds. This would make our locals as close to Tugboat if any odd errors were to pop up.

Sounds like using public docker images would be a nice feature to have.

from tugboat-registry.

This could be a possibility:

https://github.com/gdraheim/docker-copyedit

We could use it to programmatically remove the VOLUME declarations from a Docker hosted image.

Does this text from the README sound familiar?

The wish to REMOVE ALL VOLUMES came from the fact that I did want to download a tested image for local tests where the data part should be committed to the history as well in order to turn back both program and data to a defined state so that another test run will start off the exact same checkpoint.

from tugboat-registry.