Given that this is an experimental feature, I think it's reasonable to link to the PR itself as documentation (I've marked as "resolved" several distracting discussions there so the discussion and examples are easy to follow).
* Added more specific info about initializing db.
Added .sql.gz to supported files and explanation to what database it will be imported.
* Fix docker docs urls for mariadb
* Fix docker docs urls for the rest of the repos
* Sync mariadb, mysql, and percona content.md
I'm not even a newcomer to DinD and I found the READEME, coupled
with Jérôme's blog post, confusing.
Firstly, the README doesn't make explicit the oddity of having a
Docker image of Docker - I think that Elephant In The Room
needs to be acknowledged straight away.
Secondly, Jérôme's blog post concludes with a single, unambiguous
solution - simply mount the host's Docker socket inside.
Personally, I feel that strongly imlpies that that is in fact
what DinD has now officially become - a means to create sibling
contianers, rather than child containers. However, that is not
what the DinD image here does and despite the warnigns in the blog
post DinD is actively maintained.
I have attempted to make the README more obvious and explicit for
first time readers. I'd also argue that the blog post could
benefit similarly.
I would also like to see a clarification of the differences
between the vanilla, git and dind flavours.
wglambert