I install the solace/solace-pubsub-standard:latest Image successfully in docker desktop. Then I can see it in the Docker desktop as show below.
After successful Image installation in Docker Dektop
Then when I try to start it it gives me following error.
2025-05-16 18:56:41.381 | Host Boot ID: f93747cc-7b7c-4fd0-9808-6ff44f81d950
2025-05-16 18:56:41.383 | Starting PubSub+ Software Event Broker Container: Fri May 16 10:56:41 UTC 2025
2025-05-16 18:56:43.396 | Setting umask to 077
2025-05-16 18:56:43.402 | SolOS Version: soltr_10.11.1.167
2025-05-16 18:56:44.153 | 2025-05-16T10:56:44.153+00:00 <syslog.info> 704ac444c59f rsyslogd: [origin software="rsyslogd" swVersion="8.2310.0-4.el9" x-pid="157" x-info="https://www.rsyslog.com"] start
2025-05-16 18:56:45.153 | 2025-05-16T10:56:45.153+00:00 <local6.info> 704ac444c59f appuser[155]: rsyslog startup
2025-05-16 18:56:46.162 | 2025-05-16T10:56:46.162+00:00 <local0.info> 704ac444c59f appuser: EXTERN_SCRIPT INFO: Log redirection enabled, beginning playback of startup log buffer
2025-05-16 18:56:46.168 | 2025-05-16T10:56:46.168+00:00 <local0.info> 704ac444c59f appuser: EXTERN_SCRIPT INFO: /usr/sw/var/soltr_10.11.1.167/db/dbBaseline does not exist, generating from confd template
2025-05-16 18:56:46.178 | 2025-05-16T10:56:46.177+00:00 <local0.info> 704ac444c59f appuser: EXTERN_SCRIPT INFO: repairDatabase.py: no database to process
2025-05-16 18:56:46.186 | 2025-05-16T10:56:46.185+00:00 <local0.info> 704ac444c59f appuser: EXTERN_SCRIPT INFO: Finished playback of log buffer
2025-05-16 18:56:46.194 | 2025-05-16T10:56:46.193+00:00 <local0.info> 704ac444c59f appuser: EXTERN_SCRIPT INFO: Updating dbBaseline with dynamic instance metadata
2025-05-16 18:56:46.344 | 2025-05-16T10:56:46.344+00:00 <local0.info> 704ac444c59f appuser: EXTERN_SCRIPT INFO: Generating SSH key
2025-05-16 18:56:46.651 | ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519
2025-05-16 18:56:46.661 | 2025-05-16T10:56:46.661+00:00 <local0.info> 704ac444c59f appuser: EXTERN_SCRIPT INFO: Starting solace process
2025-05-16 18:56:47.374 | 2025-05-16T10:56:47.374+00:00 <local0.info> 704ac444c59f appuser: EXTERN_SCRIPT INFO: Launching solacedaemon: /usr/sw/loads/soltr_10.11.1.167/bin/solacedaemon --vmr -z -f /var/lib/solace/config/SolaceStartup.txt -r -1
2025-05-16 18:56:48.083 | 2025-05-16T10:56:48.083+00:00 <local0.info> 704ac444c59f appuser[240]: unknownDir commonLogging.py:127 (EXTERN_SCRIP - 0x00000001) unknownThread WARN Unable to read /sys/class/dmi/id/bios_date
2025-05-16 18:56:48.083 | 2025-05-16T10:56:48.083+00:00 <local0.info> 704ac444c59f appuser[240]: unknownDir commonLogging.py:127 (EXTERN_SCRIP - 0x00000001) unknownThread WARN Unable to read /sys/class/dmi/id/bios_version
2025-05-16 18:56:48.083 | 2025-05-16T10:56:48.083+00:00 <local0.info> 704ac444c59f appuser[240]: unknownDir commonLogging.py:127 (EXTERN_SCRIP - 0x00000001) unknownThread WARN Unable to read /sys/class/dmi/id/bios_vendor
2025-05-16 18:56:48.083 | 2025-05-16T10:56:48.083+00:00 <local0.info> 704ac444c59f appuser[240]: unknownDir commonLogging.py:127 (EXTERN_SCRIP - 0x00000001) unknownThread WARN Unable to read /sys/class/dmi/id/sys_vendor
2025-05-16 18:56:48.084 | 2025-05-16T10:56:48.083+00:00 <local0.info> 704ac444c59f appuser[240]: unknownDir commonLogging.py:127 (EXTERN_SCRIP - 0x00000001) unknownThread WARN Unable to read /sys/class/dmi/id/product_name
2025-05-16 18:56:51.186 | 2025-05-16T10:56:51.186+00:00 <local0.info> 704ac444c59f appuser[240]: unknownDir commonLogging.py:127 (EXTERN_SCRIP - 0x00000001) unknownThread ERROR POST Violation [022]:Required system resource missing, 1000.0 MB shared memory required at mount /dev/shm, 67.1 MB detected
2025-05-16 18:56:57.540 | File: /
2025-05-16 18:56:57.540 | Size: 4096 Blocks: 8 IO Block: 4096 directory
2025-05-16 18:56:57.540 | Device: 67h/103d Inode: 23057 Links: 1
2025-05-16 18:56:57.540 | Access: (0755/drwxr-xr-x) Uid: ( 0/ appuser) Gid: ( 0/ root)
2025-05-16 18:56:57.540 | Access: 2025-05-16 10:56:51.450961602 +0000
2025-05-16 18:56:57.540 | Modify: 2025-05-16 10:56:41.051625565 +0000
2025-05-16 18:56:57.540 | Change: 2025-05-16 10:56:43.471734140 +0000
2025-05-16 18:56:57.540 | Birth: 2025-05-16 10:56:41.051625565 +0000
2025-05-16 18:56:57.551 | Script failed: $SOLENV_ORIG_CURRENTLOAD_REALPATH/scripts/post -a -f /var/lib/solace/config/sol-platform-audit.json, line: 11
2025-05-16 18:56:57.551 | 2025-05-16T10:56:57.551+00:00 <local0.warning> 704ac444c59f appuser[1]: /usr/sw main.cpp:1113 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Child terminated with failure status: command: '$SOLENV_ORIG_CURRENTLOAD_REALPATH/scripts/post -a -f /var/lib/solace/config/sol-platform-audit.json' PID: 240 status: 512 sigRxd: 0
2025-05-16 18:56:57.551 | 2025-05-16T10:56:57.551+00:00 <local0.warning> 704ac444c59f appuser[1]: /usr/sw main.cpp:767 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Determining platform type: [ FAIL ]
2025-05-16 18:56:57.599 | 2025-05-16T10:56:57.598+00:00 <local0.info> 704ac444c59f appuser[305]: unknownDir commonLogging.py:127 (EXTERN_SCRIP - 0x00000001) unknownThread WARN Running vmr-solredswitch
2025-05-16 18:56:57.600 | consul: no process found
2025-05-16 18:56:57.607 | 2025-05-16T10:56:57.607+00:00 <local0.warning> 704ac444c59f appuser[1]: /usr/sw main.cpp:767 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Monitoring SolOS processes: [ OK ]
2025-05-16 18:56:57.613 | 2025-05-16T10:56:57.612+00:00 <local0.warning> 704ac444c59f appuser[1]: /usr/sw Generated_commonReturnCodes.cpp:137 (BASE - 0x00000000) main(0)@solacedaemon WARN Unknown exit value 1, defaulting it to 'fail'.
2025-05-16 18:56:57.613 | 2025-05-16T10:56:57.612+00:00 <local0.warning> 704ac444c59f appuser[1]: /usr/sw main.cpp:1200 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Child terminated with failure status: command: 'pkill -P $PPID dataplane-linux' PID: 308 rc: fail status: 256 sigRxd: 0
2025-05-16 18:56:57.620 | 2025-05-16T10:56:57.619+00:00 <local0.warning> 704ac444c59f appuser[1]: /usr/sw main.cpp:3937 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Syncing filesystem before shutdown ...
2025-05-16 18:56:57.635 | 2025-05-16T10:56:57.634+00:00 <local0.warning> 704ac444c59f appuser[1]: /usr/sw main.cpp:3942 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Shutting down router
2025-05-16 18:56:57.635 | 2025-05-16T10:56:57.634+00:00 <local0.err> 704ac444c59f appuser[1]: /usr/sw main.cpp:3921 (SOLDAEMON - 0x00000001) main(0)@solacedaemon ERROR ######## System shutdown complete (Version 10.11.1.167) ########
Based on the Logs I can understand its due to not enough space in "/dev/shm". But since im running this in Windows how can I increase this space.
I attempted to install the image using the --shm-size=3g parameter to allocate 3GB of shared memory, but the issue still persists. I would greatly appreciate it if anyone could share their experience or insights on resolving this problem.
For my case the error gave in supporting container. So once I come to the Container section I can see the Solace instance is running. Then can access the Solace web poral using port as show below.
Solace Instance is running and need to click on the correct port to access the portal
