Init output is missing when running on Podman v4

Issue

When running run.sh init or run.sh trainer, the command completes halfway without producing any failure or success message. In the case of misconfiguration (e.g., wrong credentials, inaccessible OS path, etc.), the actual error message is not visible, preventing corrective actions.

Affected versions

• v33.1.0 - v33.1.18

• v34.0.0 - v34.0.2

Affected configurations

On-premise configurations running RHEL with Podman

Fixed versions

• v33.1.19 and later

• v34.0.3 and later

• v35.0.0 and later

Cause

Docker-compose output is suppressed when the system path is missing a binary named docker. 

Solution / Workaround

1. To check whether the command succeeded or failed, run this command in the same terminal:

   echo $?

2. If the exit code is non-zero, then the command has failed, and we need to extract the error message. To do so while executing the run.sh command in one terminal, open another terminal, find most recently created container by running the following command:

   podman ps -a
   and follow its logs:
   podman logs -f

3. Examine the logs in the second terminal for the actual error message.