Reply to a comment from Daniel Nashed

Personally I am not a big fan of Ubuntu or Debian for Domino. But it meets the basic support requirements.
Still it is a bit different and needs special care.
You found the right post in my blog already -- which I already forgot. Do you know that blog some of those also to have a good reference to search afterwards? And others might run into similar issues and will find the error message, which I always add to make it easy to find :-)

In your case it looks like the installer did create a res/en_US.UTF-8 link instead of /res/C.
I still did not find out in which case the installer will create the language specific link. But the link is problematic!

What I always do when installing Domino and this is also valid for the container image:

- switch to the POSIX locale "C" before running the install
- Always create a symbolic link for all the main languages to avoid that the fallback to /res/C is needed.

The resource file mismatch is the number 1 question I get for my start script.
And it has it's own documentation --> https://nashcom.github.io/domino-startscript/startscript/known-issues/#hex-messages-instead-of-log-messages

Thanks for your great blog post to raise the awareness for this issue!

By the way I tested with Ubuntu and Debian as the base image of the Domino container.
But they introduced a change and the installer causes issues. And I don't see that we really have to support Domino on a Ubuntu or Debian container.

And for your it would be also easier to use the container image, than the native install.
But for the native install I would also have an automated script.