Podman run error

General Discussions
1

I am running a solace container by
podman run -d -u 0 -p 8080:8080 -p 55555:55555 -p 8008:8008 --shm-size=2g --env username_admin_globalaccesslevel=admin --env username_admin_password=admin --env system_scaling_maxconnectioncount=100 --name=XX1 solace-pubsub-standard:10.11.1.147

but podman return
podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b2e9dc9e00b9 localhost/solace-pubsub-standard:10.11.1.147 /usr/sbin/boot.sh 3 minutes ago Exited (2) 3 minutes ago 0.0.0.0:8008->8008/tcp, 0.0.0.0:8080->8080/tcp, 0.0.0.0:55555->55555/tcp XX1

podman logs b2e9dc9e00b9
Host Boot ID: 2e819140-a7b6-4a79-8997-1146e3f1b382
Starting PubSub+ Software Event Broker Container: Wed Oct 29 05:37:45 UTC 2025
Setting umask to 077
SolOS Version: soltr_10.11.1.147
ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519
File: /
Size: 50 Blocks: 0 IO Block: 4096 directory
Device: 33h/51d Inode: 9955 Links: 1
Access: (0555/dr-xr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2025-10-29 05:37:55.541022534 +0000
Modify: 2025-10-29 05:37:45.092041694 +0000
Change: 2025-10-29 05:37:47.491037294 +0000
Birth: 2025-10-29 05:37:45.092041694 +0000
Script failed: $SOLENV_ORIG_CURRENTLOAD_REALPATH/scripts/post -a -f /var/lib/solace/config/sol-platform-audit.json, line: 11
consul: no process found

Memory : 64 GB

MemAvailable (62434796 kB)

Disk
Filesystem Size Used Avail Use% Mounted on

devtmpfs 32G 4.0K 32G 1% /dev

tmpfs 32G 168K 32G 1% /dev/shm

tmpfs 32G 820K 32G 1% /run

tmpfs 32G 0 32G 0% /sys/fs/cgroup

/dev/mapper/vg_root-lv_root 8.0G 2.9G 5.2G 36% /

tmpfs 32G 776K 32G 1% /tmp

/dev/sda2 974M 188M 719M 21% /boot

/dev/mapper/vg_root-lv_opt 8.0G 1.1G 7.0G 13% /opt

/dev/sda1 200M 5.8M 194M 3% /boot/efi

/dev/mapper/vg_root-lv_home 8.0G 1.9G 6.2G 23% /home

/dev/mapper/vg_root-lv_app 14G 1.8G 12G 13% /app

/dev/mapper/vg_root-lv_var 8.0G 1.9G 6.2G 24% /var

/dev/mapper/vg_root-lv_kdump 2.0G 47M 2.0G 3% /var/crash

/dev/mapper/vg_root-lv_var_log 6.0G 887M 5.2G 15% /var/log

/dev/mapper/vg_root-lv_var_tmp 1014M 40M 975M 4% /var/tmp

/dev/mapper/vg_root-lv_var_log_audit 2.0G 97M 1.9G 5% /var/log/audit

tmpfs 6.3G 0 6.3G 0% /run/user/918965957

I think the resource is enough for solace Message container.

Memory 4GB

Disk : 6.2 GB

How can I debug this issue?

2

Hi there, I’m Solly AI, I generate responses to your questions using the power of the Solace Agent Mesh:

Please remember that AI technology can make mistakes so ensure that you read our Disclaimer.

AI Generated responses are a work in progress, your help in evaluating my response would be awesome! If my response makes sense, please mark it as a solution or give a :+1:. If my response doesn’t make sense for your topic, please react to it with a :shaking_face:.

Looking at the documentation and community discussions, here are the key points to resolve issues when running a Solace software event broker container using podman:

  1. Storage Group Permissions:
  • Create a storage directory for the event broker
  • Give the container user proper access permissions using:
mkdir storage-group
podman unshare chown 1000:0 -R storage-group
  1. Container Mount Configuration:
  • Use the proper mount syntax with bind mount and appropriate permissions:
--mount type=bind,source=/path/to/storage-group,destination=/var/lib/solace,relabel=private,ro=false
  1. Network Configuration:
  • For rootless containers, use the slirp4netns network mode:
--net slirp4netns:port_handler=slirp4netns
  1. Port Mapping:
  • Map the required ports for management and messaging:
  • Port 8080 for HTTP management access instead of 1943 (HTTPS) unless you have configured certificates
  • Port 55555 for messaging
  1. Container User:
  • Run the container with the appropriate user ID (typically 1000 for rootless):
-u 1000
  1. System Resources:
  • Ensure adequate shared memory allocation:
--shm-size=1g

Relevant documentation:

3

Hi Shjhyu,

It looks like the AI has provided some useful suggestions here. Note, that you are using rootless podman in this case (podman create vs. sudo podmand create); that comes with a few extra steps. The relevant page in the documentation is Rootless Podman for Ubuntu. Even if you are not using Ubuntu, you should be able to get it going with the information on that page.

Best Regards,

Paul

4

@pkondrat Thanks for your timely reply.
I can start solace container service now.

Thanks,

Richard