Daniel Nashed's Blog

How to update Domino when running in a container?

Today I just updated my production environment to Domino 14.0 FP4.
Let me show you how it works if you have everything setup.

If you are using the Domino container project you can add two additional components from the start script repository (https://nashcom.github.io/domino-startscript/).

1. Domino Container Control

https://nashcom.github.io/domino-startscript/dominoctl/

2. Domino Download Script

https://nashcom.github.io/domino-startscript/domdownload/


The container project and the start script functionality works hand in hand.
The build script leverages the Domino Download script if present and automatically downloads software for you if you have an internet connection an a MHS download token.

The update drills down to those 4 commands:


cd /local/github/domino-container
git pull
./build.sh
dominoctl update

1. Switch to the right directory
2. Pull changes for the project (which brings software.txt and current_version.txt to the latest state so that the build script knows what the latest version is)
3. Run the build script to prompt you for software to install when building the image
4. Update a container with a new image by throwing away the old container and creating a new one with the new image

The build menu below has options to store the current selected components and will remember those settings, which you can just confirm when building.

Depending on your build performance this this can take from like 5 to 10 minutes on modern machines.
The update (down-time) is only the time it takes to shutdown and restart the server.


If you are running the same image on multiple servers, you could push the image to a private registry.
Then the update on a server would be just a "docker pull" and "dominoctl update"
In my environment I usually build on all machines, because all of them run different configurations and platforms.

-- Daniel

• Comments [0]