Unable to execute Docker image using Podman

[cloojure]

Running Marklogic using Docker Desktop (on Mac OSX) works find. However, it crashes when I try to use Podman:

> podman logs -f intelligent_lewin
2025-07-08 05:47:55.368 Info: Starting container with MarkLogic Server.
2025-07-08 05:47:55.389 Info: | server ver: 11.3.1 | scripts ver: 2.1.3 | image type: ubi9-rootless | branch: release-2.1.3 |
2025-07-08 05:47:55.578 Info: /etc/marklogic.conf will be appended with provided environment variables.
2025-07-08 05:47:55.599 Info: Appended MARKLOGIC_PID_FILE to /etc/marklogic.conf
2025-07-08 05:47:55.619 Info: Appended MARKLOGIC_UMASK to /etc/marklogic.conf
2025-07-08 05:47:55.637 Info: Appended TZ to /etc/marklogic.conf
2025-07-08 05:47:55.657 Info: Appended MARKLOGIC_USER to /etc/marklogic.conf
2025-07-08 05:47:55.678 Info: Appended MARKLOGIC_EC2_HOST to /etc/marklogic.conf
2025-07-08 05:47:55.698 Info: INSTALL_CONVERTERS is false, not installing converters.
/opt/MarkLogic/mlcmd/bin/is-ec2.sh: line 6: sudo: command not found
MarkLogic - user override of EC2 detection
Starting MarkLogic: 2025-07-08 05:48:01.218 Info: MARKLOGIC_ADMIN_PASSWORD is set, using ENV for admin password.
2025-07-08 05:48:01.244 Info: MARKLOGIC_ADMIN_USERNAME is set, using ENV for admin username.
2025-07-08 05:48:01.266 Info: MARKLOGIC_WALLET_PASSWORD is set, using ENV for wallet-password.
2025-07-08 05:48:01.286 Info: MARKLOGIC_INIT is true, initializing the MarkLogic server.
2025-07-08 05:48:01.305 Info: Initializing MarkLogic on aa33618daee8
2025-07-08 05:48:03.331 Info: Waiting for MarkLogic to restart.
2025-07-08 05:48:14.255 Info: MarkLogic has restarted.
2025-07-08 05:48:14.275 Info: Installing admin username and password, and initialize the security database and objects.

2025-07-08 05:49:35.817 Error: Expected response code 202, got 000 from http://aa33618daee8:8001/admin/v1/instance-admin.

This occurs with both the default image and progressofficial/marklogic-db:11.3.1-ubi9-rootless-2.1.3.

Is there a workaround to this problem?

[vitalykorolev]

@cloojure could you share more details about your environment and the command you used to run the container? This might not be podman specific issue.