Docker 2.2.4 Release with MarkLogic 11.3.4

This release includes the following updates

• MarkLogic ARM images for Docker are now available for development purposes only and are not certified for production use.
• This Docker image release aligns with the MarkLogic 11.3.4 server release.
• Upgraded the Red Hat 8 and 9 Universal Base Image (UBI), aligning with modern container standards and improving security and maintainability.

Known Issues and Limitations

1. The root image must be run in privileged mode. If the image isn't run as privileged, the calls that use sudo in the startup script will fail due to lack of required permissions as the image will not be able to create a user with the required permissions. To run in non-privileged mode, use one of the “rootless” image options.
2. Using the "leave" button in the Admin interface to remove a node from a cluster may not succeed, depending on your network configuration. Use the Management API to remove a node from a cluster. See: https://docs.marklogic.com/REST/DELETE/admin/v1/host-config.
3. Rejoining a node to a cluster, that had previously left that cluster, may not succeed.
4. MarkLogic Server will default to the UTC timezone.
5. As part of the hardening process, the following packages are removed from the image: vim-minimal, cups-client, cups-libs, tar, python3-pip-wheel, platform-python, python3-libs, platform-python-setuptools, avahi-libs, binutils, expat, libarchive, python3, python3-libs, python-unversioned-command. These packages are not required for the operation of MarkLogic Server and are removed to reduce the attack surface of the image. If you require any of these packages, you can install them in your own Dockerfile.
6. The cryptographic modules of RHEL 9 are not yet certified for the FIPS 140-3 requirements.