[BUG] 4.4.2 not stating Please define INSTALL4J_JAVA_HOME

[matthiasantierens]

Describe the bug
A clear and concise description of what the bug is. Is this consistently reproducible?

To Reproduce
Setup steps (if required). Example:

1. We had nextgen_connect running with version 3.10.1
2. Change container version to 4.4.2
3. Check logs for error

docker logs example_mirth_1
No suitable Java Virtual Machine could be found on your system.
The version of the JVM must be at least 1.8.
Please define INSTALL4J_JAVA_HOME to point to a suitable JVM.
No suitable Java Virtual Machine could be found on your system.
The version of the JVM must be at least 1.8.
Please define INSTALL4J_JAVA_HOME to point to a suitable JVM.
No suitable Java Virtual Machine could be found on your system.
The version of the JVM must be at least 1.8.
Please define INSTALL4J_JAVA_HOME to point to a suitable JVM.
No suitable Java Virtual Machine could be found on your system.
The version of the JVM must be at least 1.8.
Please define INSTALL4J_JAVA_HOME to point to a suitable JVM.
No suitable Java Virtual Machine could be found on your system.
The version of the JVM must be at least 1.8.
Please define INSTALL4J_JAVA_HOME to point to a suitable JVM.
No suitable Java Virtual Machine could be found on your system.
The version of the JVM must be at least 1.8.
Please define INSTALL4J_JAVA_HOME to point to a suitable JVM.
No suitable Java Virtual Machine could be found on your system.
The version of the JVM must be at least 1.8.
Please define INSTALL4J_JAVA_HOME to point to a suitable JVM.
No suitable Java Virtual Machine could be found on your system.
The version of the JVM must be at least 1.8.
Please define INSTALL4J_JAVA_HOME to point to a suitable JVM.
No suitable Java Virtual Machine could be found on your system.
The version of the JVM must be at least 1.8.
Please define INSTALL4J_JAVA_HOME to point to a suitable JVM.

Expected behavior
We expected mirth to migrate to the latest version.

Actual behavior
Crashlooping with unexpected error

Environment (please complete the following information):

• OS: Ubuntu 18.04.6 LTS with docker 20.10.7
• Connect Version 3.10.1 -> 4.4.2

Additional context
We are using a docker-compose setup.
In other environments, this was working fine.