Troubleshooting
Problem
A compatibility issue has been identified in environments where the Docker server requires a minimum API version higher than the value configured by the product.
During the installation process, the script
/path/of/installation/start_IBM-Z_SW_Asset_Mgmt-UI.sh is generated with the parameter docker_api_version set to 1.39. If the Docker server running on the target system requires a higher minimum API version, communication with the Docker backend fails and the application cannot properly load its containerized services.
When this condition occurs, backend containers fail to load correctly and several application functions become unavailable. Users may experience generic error messages such as:

"We are unable to process your request. Please try again later."
Additionally, the Information screen may fail to load and remain indefinitely in the loading state.
Environment
This issue can affect any installation where the Docker server requires a minimum API version higher than the value configured in the startup script (docker_api_version=1.39).
Environments where the configured API version is already supported by the Docker server are not affected.
Resolving The Problem
As a temporary workaround, the Docker API version configured in the startup script must be updated to match the minimum API version supported by the Docker server.
Step 1 – Determine the Minimum Supported API Version
Run the following command:
docker version
In the output, locate the Server section and identify the value reported as Minimum API version (or the minimum version supported by the server).
Example:
Server:
Engine:
Version: 29.1.3
API version: 1.52 (minimum version 1.44)
In this example, the minimum supported API version is 1.44.
Step 2 – Update the Startup Script
Edit the following file:
/path/of/installation/start_IBM-Z_SW_Asset_Mgmt-UI.sh
Locate the docker_api_version parameter and replace the default value:
docker_api_version=1.39
The parameter is in the docker run line (like in this example):
$docker run -e USER_ID=$USER_ID -e GUID=$GUID -e ZAO_IMPORT_VERSION="ibm_z_sw_asset_mgmt-import:09.01-OAGAPTF-ZS833-IBM" -e ExecOS=$ExecOS -e docker_api_version=1.39 -e ehostname=$Hostnm -e enableHttps=true -v /var/run/docker.sock:/var/run/docker.sock -e ehostIP=$HostIP -e TZ=Australia/Perth -e DOCKER_PORT=2376 -v zswam_database-91-IBM:/usr/src/app/database -v zswam_uploads-91-IBM:/usr/src/app/upload -v zswam_logs-91-IBM:/usr/src/app/logs -v zswam_tls-91-IBM:/usr/src/app/tls -v zswam_backup-91-IBM:/usr/src/app/backup --name ibm-z-sw-asset-mgmt-ui-prod-91-IBM -p 8443:8443 -d -it --rm ibm-z-sw-asset-mgmt-ui:prod-91-IBM
with the minimum API version reported by the Docker server.
Example:
$docker run -e USER_ID=$USER_ID -e GUID=$GUID -e ZAO_IMPORT_VERSION="ibm_z_sw_asset_mgmt-import:09.01-OAGAPTF-ZS833-IBM" -e ExecOS=$ExecOS -e docker_api_version=1.44 -e ehostname=$Hostnm -e enableHttps=true -v /var/run/docker.sock:/var/run/docker.sock -e ehostIP=$HostIP -e TZ=Australia/Perth -e DOCKER_PORT=2376 -v zswam_database-91-IBM:/usr/src/app/database -v zswam_uploads-91-IBM:/usr/src/app/upload -v zswam_logs-91-IBM:/usr/src/app/logs -v zswam_tls-91-IBM:/usr/src/app/tls -v zswam_backup-91-IBM:/usr/src/app/backup --name ibm-z-sw-asset-mgmt-ui-prod-91-IBM -p 8443:8443 -d -it --rm ibm-z-sw-asset-mgmt-ui:prod-91-IBM
Step 3 – Restart the Application
After saving the modification, restart the application using the standard startup procedure.
Once restarted, the application should be able to communicate correctly with the Docker backend, allowing containers to load successfully and restoring the affected functionality.
-----------------------------------------------------------------------------------------------------------------------------------------------
A fix is planned to enhance the installation process so that the docker_api_version parameter is automatically aligned with the Docker server capabilities, eliminating the need for manual intervention and preventing future compatibility issues.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
05 June 2026
UID
ibm17275260