部署Solace Docker镜像时出现错误，请求技术支持

Hey there, let's work through this Solace Docker container issue you're facing. First, let's recap what you did and the partial error you saw:

Your Run Command #

docker run -p 8080:8880 -p 55555:55555 --shm-size=2g --env 'username_admin_globalaccesslevel=admin' --env 'username_admin_password=admin' --name=solace solace-app:8.9.0.1008-community

Partial Error Output #

Host Boot ID: 0e071b66-a316-465f-9adb-bc088d8edffe；启动VMR Docker容器：Wed Apr 4 12:34:20 UTC 2018；SolOS版本：soltr_8.9.0.1008；2018-04-04T12:35:16.271+00:00 <syslog.warning> 1898a041b742 rsyslogd: environ...

The key issue here is that the rsyslogd warning is truncated—it cuts off after environ...—so we need to get the full log first to pinpoint the problem. Here's what to do next:

1. Grab the Full Container Logs #

Run this command to see the complete output from your Solace container:

docker logs solace

Look for the full text of that rsyslogd warning—this will tell us exactly what's triggering the alert. For example, it might be a missing environment variable or a configuration issue with rsyslog inside the container.

2. Check Common Solace Docker Startup Issues #

Even without the full log, let's rule out some frequent culprits:

• Shared Memory Availability
  You've set --shm-size=2g (the minimum for Solace Community Edition), but double-check your host machine has enough free shared memory. Run this on your host:

  df -h /dev/shm
  

  If available space is less than 2GB, free up resources or increase the host's shared memory allocation.

• Port Conflicts
  Verify the ports you're mapping aren't already in use on your host:

  netstat -tulpn | grep 8080
  netstat -tulpn | grep 55555
  

  If either port is occupied, stop the conflicting process or adjust your docker run command to use different host ports (e.g., -p 8081:8880).

• Container Status
  Check if the container is actually running or failed to start:

  docker ps -a
  

  • If status shows Exited, the container didn't boot successfully—focus on the early logs for startup failures.
  • If status shows Up, try accessing the Solace admin UI at http://localhost:8080 with credentials admin/admin. If you can log in, the rsyslog warning might be a non-critical cosmetic issue.

• Image Integrity
  Corrupted or incomplete images can cause startup problems. Try resetting:

  # Stop and remove the existing container
  docker rm -f solace
  # Re-pull the image (if it's hosted remotely)
  docker pull solace-app:8.9.0.1008-community
  # Re-run your original command
  docker run -p 8080:8880 -p 55555:55555 --shm-size=2g --env 'username_admin_globalaccesslevel=admin' --env 'username_admin_password=admin' --name=solace solace-app:8.9.0.1008-community
  

Quick Note on Version #

SolOS 8.9 is a pretty old release—if possible, consider upgrading to a newer community edition version. Newer releases fix bugs, improve stability, and have better Docker compatibility.

Once you have the full rsyslogd error message, we can narrow down the exact fix. Let me know what you find!

内容的提问来源于stack exchange，提问作者user7365288