Hello, same issue of @PedromDimas here.
@uherbst do you have the chance to have a look?
You can find my report below.
Command:
% docker run -d -p 8080:8080 -p 55554:55555 -p 8008:8008 -p 1883:1883 -p 8000:8000 -p 5672:5672 -p 9000:9000 -p 2222:2222 --shm-size=4g --env username_admin_globalaccesslevel=admin --env username_admin_password=admin --memory=“3g” --name=solace solace/solace-pubsub-standard
macOS 10.15.7 (Intel architecture)
Docker version 20.10.9, build c2ea9bc
To run Docker I (have to) use Rancher Desktop. It doesn’t give any particular problems though.
% docker info Client: Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc., v0.7.1) compose: Docker Compose (Docker Inc., v2.2.3) Server: Containers: 18 Running: 1 Paused: 0 Stopped: 17 Images: 19 Server Version: 20.10.14 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Native Overlay Diff: true userxattr: false Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 1 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc Default Runtime: runc Init Binary: docker-init containerd version: 3df54a852345ae127d1fa3092b95168e4a88e2f8 runc version: 52b36a2dd837e8462de8e01458bf02cf9eea47dd init version: Security Options: seccomp Profile: default Kernel Version: 5.15.32-0-virt Operating System: Alpine Linux v3.15 OSType: linux Architecture: x86_64 CPUs: 2 Total Memory: 5.809GiB Name: lima-rancher-desktop ID: 6BS3:6H5Y:TCXZ:JCRC:3Y4Q:76EZ:XX5X:R4AT:FCSZ:CY34:BXWO:YLYV Docker Root Dir: /var/lib/docker Debug Mode: false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false
When the container is started the solace cli has not effect (see below)
% docker exec -it solace cli SolOS startup in progress, status: ‘Finishing pre-startup actions’ Please try again later… % docker exec -it solace cli %
When I try to log in using the web interface I get the timeout message
Timeout of 30000ms exceeded
and the container dies. After that I get the logs below:
% docker logs solace Host Boot ID: ffbd1abc-f121-4a1d-846f-eac3e7452658 Starting PubSub+ Software Event Broker Container: Tue May 24 10:18:40 UTC 2022 Setting umask to 077 SolOS Version: soltr_9.13.1.38 2022-05-24T10:18:41.434+00:00 <syslog.info> 0f7cda9acb01 rsyslogd: [origin software=“rsyslogd” swVersion=“8.2102.0-5.el8” x-pid=“115” x-info=" https://www.rsyslog.com"] start 2022-05-24T10:18:42.433+00:00 <local6.info> 0f7cda9acb01 appuser[113]: rsyslog startup 2022-05-24T10:18:43.457+00:00 <local0.info> 0f7cda9acb01 appuser: EXTERN_SCRIPT INFO: Log redirection enabled, beginning playback of startup log buffer 2022-05-24T10:18:43.470+00:00 <local0.info> 0f7cda9acb01 appuser: EXTERN_SCRIPT INFO: /usr/sw/var/soltr_9.13.1.38/db/dbBaseline does not exist, generating from confd template 2022-05-24T10:18:43.510+00:00 <local0.info> 0f7cda9acb01 appuser: EXTERN_SCRIPT INFO: repairDatabase.py: no database to process 2022-05-24T10:18:43.534+00:00 <local0.info> 0f7cda9acb01 appuser: EXTERN_SCRIPT INFO: Finished playback of log buffer 2022-05-24T10:18:43.555+00:00 <local0.info> 0f7cda9acb01 appuser: EXTERN_SCRIPT INFO: Updating dbBaseline with dynamic instance metadata 2022-05-24T10:18:43.861+00:00 <local0.info> 0f7cda9acb01 appuser: EXTERN_SCRIPT INFO: Generating SSH key ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519 2022-05-24T10:18:44.257+00:00 <local0.info> 0f7cda9acb01 appuser: EXTERN_SCRIPT INFO: Starting solace process 2022-05-24T10:18:46.490+00:00 <local0.info> 0f7cda9acb01 appuser: EXTERN_SCRIPT INFO: Launching solacedaemon: /usr/sw/loads/soltr_9.13.1.38/bin/solacedaemon --vmr -z -f /var/lib/solace/config/SolaceStartup.txt -r -1 2022-05-24T10:18:50.584+00:00 <local0.info> 0f7cda9acb01 appuser[200]: unknownDir post:262 (EXTERN_SCRIP - 0x00000000) unknownThread WARN POST Violation [023]:Recommended system resource missing, System CPUs do not support invariant TSC (nonstop_tsc) File: / Size: 4096 Blocks: 8 IO Block: 4096 directory Device: 3bh/59d Inode: 4328695 Links: 1 Access: (0755/drwxr-xr-x) Uid: ( 0/ appuser) Gid: ( 0/ root) Access: 2022-05-24 10:18:50.880007748 +0000 Modify: 2022-05-24 10:18:40.190007682 +0000 Change: 2022-05-24 10:18:43.460007702 +0000 Birth: 2022-05-24 10:18:40.190007682 +0000 2022-05-24T10:18:53.183+00:00 <local0.warning> 0f7cda9acb01 appuser[1]: /usr/sw main.cpp:752 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Determining platform type: [ OK ] 2022-05-24T10:18:53.221+00:00 <local0.warning> 0f7cda9acb01 appuser[1]: /usr/sw main.cpp:752 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Generating license file: [ OK ] 2022-05-24T10:18:53.409+00:00 <local0.warning> 0f7cda9acb01 appuser[1]: /usr/sw main.cpp:752 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Running pre-startup checks: [ OK ] 2022-05-24T10:18:53.459+00:00 <local0.warning> 0f7cda9acb01 appuser[271]: /usr/sw ipcCommon.cpp:447 (BASE_IPC - 0x00000000) main(0)@cli(?) WARN SolOS is not currently up - aborting attempt to start cli process Unable to raise event; rc(would block)
Obviously this is a show stopper because not being able to use PubSub+ in a containerized environment means no automatic tests.
Thank you
Daniele