Hi @Aaron ,
Thanks for your time keep investigate this issue.
Here is the docker compose file I am using.
# https://github.com/SolaceLabs/solace-single-docker-compose/blob/master/template/PubSubStandard_singleNode.yml
version: '3.3'
services:
solace:
container_name: solaceMessageBorker
image: solace/solace-pubsub-standard:9.12.1.17
ulimits:
core: 1
nofile:
soft: 2448
hard: 6592
deploy:
restart_policy:
condition: on-failure
max_attempts: 1
shm_size: 2g
networks:
- solace_net
environment:
username_admin_globalaccesslevel: "admin"
username_admin_password: "admin"
ports:
# Web transport
- "${SOLACE_WEB_TRANSPORT:-20060}:8080"
# Solace APIs to connect to the message broker on this port
- "${SOLACE_API_MSG_BROKER:-20061}:55555"
# Solace APIs to connect to the message broker on this port secured
- "${SOLACE_API_MSG_BROKER_SECURED:-20066}:55443"
# Solace APIs to connect to the message broker on this port compressed
- "${SOLACE_API_MSG_BROKER_COMPRESSED:-20067}:55003"
# JavaScript sample applications pass Web Messaging traffic through
# - "8008:8008"
# MQTT connectitvity
- "${SOLACE_MQTT_1:-20062}:1883"
- "${SOLACE_MQTT_2:-20063}:8000"
# AMQP 1.0 application using Apache QPID APIs
- "${SOLACE_AMQP:-20064}:5672"
# Use REST to send messaging and event data with Solace's RESTful API port
- "${SOLACE_REST:-20065}:9000"
# SSH Command Line Interface for advanced configuration
- "${SOLACE_SSH:-2222}:2222"
networks:
solace_net:
driver: bridge