Domino 14.5.1 AutoUpdate and container update
Daniel Nashed – 20 March 2026 20:48:51
For Linux my clear preference is a container deployment wherever possible.
A container only adds a very thin layer on a server and makes updates and consistent installations possible.
The container image has a lot of customization options.
I have a couple of customers who are really happy with their container deployment. OK they have me around to add any new option they might need on the fly -- which goes to the open source project as a feature immediately.
Haha I am my best customer for the container deployment. I add new functionality mostly for me. And some features go hand in hand with functionality in the Domino start script.
But you don't always want or can use containers.
Domino Autoupdate is pretty cool. I just ran it again for 14.5.1 to update all my Windows servers and a coupe of Linux servers.
In my case the Linux servers are mainly native to test autoupdate.
But AutoUpdate itself has also some helpful information. AutoUpdate provides more detailed information about your servers in one single spot.
It also knows about if the servers run in a container and which container platform is used.
And It also knows for example the account the server runs on.
On Linux it also provides the glibc version for example.
None of this information is there by co-incident. I added all those details because they play an important role in the deployment process.
Another small difference is that Domino servers report their version using a push. Each server is responsible for their own AutoUpdate server document on the central replica.
-- Daniel
- Comments [0]
![[HCL Domino]](../lotus-domino.gif){kind=small}
![[Domino on Linux]](../domino-linux.gif){kind=small}
![[Nash!Com]](../nashcom.gif){kind=small}
![[Daniel Nashed]](../daniel-nsh.gif){kind=small}