Skip to content

Latest commit

 

History

History
46 lines (32 loc) · 1.56 KB

README.md

File metadata and controls

46 lines (32 loc) · 1.56 KB
Raw

rethinkdb-dockerfiles

Dockerfiles for past and present versions of RethinkDB.

Documentation

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

Currently supported distributions

The following base images are supported for containerized RethinkDB servers.

  • Ubuntu Xenial, Bionic, Focal, Jammy, ...
  • Debian Bookworm, Bullseye, ...
  • CentOS 7
  • Rocky/Alma 8
  • Rocky/Alma 9

Procedure for updating

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

# (You might want to edit the script to use "sudo docker" or comment
# out the docker lines.)

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

# if package version includes a suffix like "+1",
# pass that suffix as the second argument
# Note: It's unclear if "suffix" actually does what you want -- read cut-new-release.sh
./cut-new-release.sh 2.3.7 +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).