Domino 14.5 EA2 Community Image patch for fixing December 2024 issue
Daniel Nashed – 15 January 2025 14:46:50
HCL published a new Notes & Domino Windows DLL and Linux Lib for the problem occurred December 13 in the Early Access Program forum (EAP) --> https://hclsw.co/domino-14-5-eap-forum
This isn't a IF. Just a replacement of the main Notes/Domino DLL/Lib to address the problem also for the early access release.
The fix was on hold because the focus was on production and customer environments first.
Daily builds don't have support for IF/HF. Therefore there is a simple "sidepack" with just the affected files to replace.
You just stop your server or client and replace the files.
For a container image patching a container image isn't the right way.
But the container project supports custom add-ons. Usually this is intended to add software from 3rd parties, like a server task or extension manager.
The same process can also be used to patch Domino in the container at container build time.
Here is the official documentation --> https://opensource.hcltechsw.com/domino-container/concept_custom_addons/.
Let me share the steps I just took to patch my server.
I can't make the tar file available for download to just include it in our build options referenced via a HTTPS link.
But this process should be pretty straightforward and you can share this tar file for all internal servers you are building an image for.
Building the add-on to patch Domino 14.5 EA2
The first steps it to create a new directory to hold your file structure for the software you and to distribute
In the next step you create sub directory for the Domino binary directory.
The -p options allows you to create the whole directory path a once:
mkdir -p /tmp/patch/domino-bin
cd /tmp/patch/domino-bin
Then you add the two files into that directory and package them up into a tar file.
tar -cvf /local/software/domino145ea2patchx.tar *
The directory structure look like this:
tree
.
└── domino-bin
├── libnotes.so
└── libnotes.so.sym
Because the data needs to be verified to be added to the container, you have to provide the SHA256 of the tar file when getting it installed.
Linux provides the a command-line tool to generate the SHA256 checksum like this:
sha256sum /local/software/domino145ea2patch.tar
d088983544651940f71b8b7d9d942aaad84ecbe9fdbd24464178c858b9daff3b /mnt/storagebox/software/domino145ea2patch.tar
Once you have the file in place and the checksum, you just add the custom add-on to your container build command-line.
The build script will take care for patching the binaries for your during the build process.
Custom add-ons are installed at the end of the build processes and therefore allow to patch also Domino binaries if needed.
The same process works for all kind of business partner applications.
-custom-addon=domino145ea2patch.tar#d088983544651940f71b8b7d9d942aaad84ecbe9fdbd24464178c858b9daff3b
- 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}