From 6bf0c1d2c3fd120e05e022fce40908501813b141 Mon Sep 17 00:00:00 2001 From: Jeb Rosen Date: Mon, 3 May 2021 15:58:24 -0700 Subject: [PATCH] docs: explain why Debian 9 is used as the base image; add some command details to releasing.md --- Dockerfile | 5 +++++ releasing.md | 2 ++ 2 files changed, 7 insertions(+) diff --git a/Dockerfile b/Dockerfile index 29f0cb8..0335759 100644 --- a/Dockerfile +++ b/Dockerfile @@ -1,5 +1,10 @@ # Dfam TE Tools container including RepeatMasker, RepeatModeler, coseg +# Why debian:9? glibc, and probably other libraries, occasionally take +# advantage of new kernel syscalls. Docker containers normally run with the +# host machine's kernel. Debian 9 has an old enough glibc to not have many +# features that would only work on newer machines, and the other packages are +# new enough to compile all of these dependencies. FROM debian:9 AS builder RUN apt-get -y update && apt-get -y install \ diff --git a/releasing.md b/releasing.md index e4a8033..2c12f1a 100644 --- a/releasing.md +++ b/releasing.md @@ -16,5 +16,7 @@ 4. Test the container 5. Commit and tag in git as x.y 6. Tag the container (in docker) as `:x`, `:x.y`, and `:latest` + * For each version, run: `docker image tag dfam/tetools:dev dfam/tetools:version` 7. Push these tags to docker hub + * For each tag made before: `docker push dfam/tetools:version` 8. Push the commit and tag to github