Stuart P. Bentley

You don't even need a new Dockerfile, just run with `rethinkdb -d /testdata --bind all` instead of the default `rethinkdb --bind all`.

@jfrazelle: > Tbh I wish we could remove the volume command from Dockerfile entirely, but > that's a whole different story. I agree, to a certain extent, but that would...

Revisiting this a year later: per @jfrazelle's sentiment about how the Dockerfile system would be better if there just altogether weren't a VOLUME command, and @danjenkins' point about the volumes...

If you can convince upstream to package for it, sure.

Seeing as how I'm currently [moving the container images to use Alpine Linux](https://github.com/rethinkdb/rethinkdb-dockerfiles/pull/40#issuecomment-350838227), it might also be worth trying to get the upstream maintainer at Alpine [(probably Daniel Treadwell)](https://pkgs.alpinelinux.org/packages?name=rethinkdb) to...

How many *other* official images run as a non-root user/group? My experience has been that, in the Docker world, the containerization itself is generally considered to be "good enough" in...

Looks good enough to me. Covers most of my thoughts from #40 (I added a commit to tag the Alpine release), and while I'm generally no fan of adding foreign-tree...

Not until I can get a satisfactory answer for all the concerns raised in https://github.com/rethinkdb/rethinkdb-dockerfiles/issues/44.

Also, this isn't *strictly* a blocker, but there isn't much motivation for anybody to put together a new release image when there hasn't been a new release of RethinkDB for...

Closing this PR, too - we need a version that does its own build instead of depending on Alpine's packaging. See https://github.com/rethinkdb/rethinkdb-dockerfiles/issues/44#issuecomment-488873308.