On Feb 1, 2022, at 12:26 PM, bob B via Mailman-users <mailman-users@mailman3.org> wrote:

I am running mailman 3 in docker and trying to figure out -how to upgrade

“tags” are the versions, you pull down container images at a version and re-create the containers using those.

-can you back out.

For example I installed docker with a git pull • git clone https://github.com/maxking/docker-mailman

The only real thing that this gets you is the docker-compose.yaml file, everything else in the repo is only ever useful if you want to re-build the image.

Assuming that your local copy of docker-compose.yaml has your settings and password, you want to keep a copy of it before you do a git pull and delete changes in it.

docker images shows REPOSITORY TAG IMAGE ID CREATED SIZE maxking/mailman-web 0.3 9ba9d3d7084d 4 months ago 487MB maxking/mailman-core 0.3 26c920c0094b 4 months ago 178MB **** database is hosted via external database

I only installed it a few months ago, am I really on 0.3.0 , I assume I am on 3.0 from 2019 and that is what "git clone https://github.com/maxking/docker-mailman" gets????

Whatever is the “TAG” in the above row is the real version, that’s what you get. Tags can be moving though, so 0.3 represents the 0.3.x at the point of docker pull. All you get from “git clone …” is the “docker-compose.yaml” file, which specifies the version of the container images to pull.

Currently, the main branch says 0.41. When you pulled, the value there was probably 0.3.

For a fully re-producible copy, keep a copy of the “IMAGE ID” and you should be able to re-create the old setup and back-out from upgrade. Just put the respective image id for core and web images in the docker-compose.yaml under `”image” section.

looking at the release matrix "https://github.com/maxking/docker-mailman/releases?page=2" It looks like the latest releases are 0.4.1 for core & 0.4.2 for web,

How do I upgrade, is it a "git pull" or "docker update" command?

Here are steps:

• Copy the docker-compose.yaml to safe place, that’s the only thing you really need from the git repo.

• Bump the “image” to the version you want to upgrade to, for both Core and Web. Note that 0.4.2 release notes mentions only changes in web, but both images are tagged with 0.4.2 during the release.

If you are jumping to 0.4.x release, make sure you also follow2.

• Run the following commands wherever you have other changes ready:
  • docker-compose -f docker-compose.yaml down. # Shuts down the current instance.
  • docker-compose -f doker-compose.yaml rm # Deletes the containers with name mailman-core and mailman-web.
  • docker-compose up -d # Starts the new container with the new container image.

If something does not work, is there a way to back out?

Local state on disk isn’t wiped, but do make sure to backup the database because new releases will try to install the database schema changes, which you’ll need to revert to back out.

What version should I go to from 0.3? I am thinking it should be v0.3.12 cause that won't break anything? But how do I do that?

0.3.12 would be safe to try before jumping to 0.4.x. Same steps, except the link pointing to upgrade notes for 0.4.x

-- thanks, Abhilash Raj (maxking)