Skip to content
Dockerfiles for past and present versions of RethinkDB.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
jessie
stretch
trusty
utopic
vivid
wheezy
wily
xenial
yakkety/2.3.6
zesty/2.3.6
README.md Note that all tags should be updated Nov 17, 2015
cut-new-release.sh

README.md

rethinkdb-dockerfiles

Dockerfiles for past and present versions of RethinkDB.

Documentation

https://github.com/docker-library/docs/blob/master/rethinkdb/README.md

Procedure for updating

After creating a commit for the new release package using ./cut-new-release.sh:

# example
./cut-new-release.sh 1.16.1

# if package version includes a suffix like "+1",
# pass that suffix as the second argument
./cut-new-release.sh 1.16.2 +1 

Note the hash of the commit and push it to GitHub.

Once the commit is pushed, go to https://github.com/docker-library/official-images/edit/master/library/rethinkdb and put together a pull request, replacing the old tip-commit hash with the new tip-commit hash for all images, and adding new tags for the new version (using the jessie dockerfiles). The new point release should be added as a tag, and tags for the minor and major versions should be either created or updated to point to the new Dockerfile, as well as the "latest" tag.

Once the pull request for the new image is accepted by the upstream Docker library, this should be announced in Slack and/or IRC (and maybe Twitter).

You can’t perform that action at this time.