Is this the right place to file bug reports?
I was able to get ignition 8.3beta-2 running on my ARM Mac with a direct install, but when pulling the docker image and running it, it hangs on the Ignition Gateway is Starting
page.
Repro steps:
docker pull inductiveautomation/ignition:8.3.0-beta2
docker run -d -p 9088:8088 --name ignition-test inductiveautomation/ignition:8.3.0-beta2
-n docker-test -a localhost -h 9088 -s 9043
Can you share the gateway logs?
Did a fresh attempt this morning. Here’s the result of docker logs ignition-test
. Not seeing any obvious errors, but it the whole thing ran for 20+ mins and is still “Starting”
ignition-test-logs.txt (54.5 KB)
Is there another place I can look at for more detailed logs?
You’ll need to get a terminal in the container as root, then install a JDK and use jps/jstack to get a thread dump of the “WrapperSimpleApp” pid:
kevin@DV-55J5DY3-LT:~$ docker exec -it -u root aa38ff98785470f33833d798dba0d13dec471cd653e6eaaba58c294e19ac8569 /bin/bash
root@aa38ff987854:/usr/local/bin/ignition# apt-get update && apt-get install openjdk-17-jdk
root@aa38ff987854:/usr/local/bin/ignition# jps
6135 Jps
91 WrapperSimpleApp
root@aa38ff987854:/usr/local/bin/ignition# jstack 91
(while it’s stuck at this spot in the logs)
Also, can you provide the output from docker version
?
Client: Docker Engine - Community
Version: 28.0.4
API version: 1.43 (downgraded from 1.48)
Go version: go1.24.1
Git commit: b8034c0ed7
Built: Tue Mar 25 15:03:35 2025
OS/Arch: darwin/arm64
Context: colima
Server: Docker Engine - Community
Engine:
Version: 24.0.9
API version: 1.43 (minimum version 1.12)
Go version: go1.20.13
Git commit: fca702d
Built: Thu Feb 1 00:48:55 2024
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: 1.6.28
GitCommit: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
runc:
Version: 1.1.12
GitCommit: v1.1.12-0-g51d5e94
docker-init:
Version: 0.19.0
GitCommit: de40ad0
It eventually started, but only somewhat. Got me to the main gateway page, Perspective and some other stuff didn’t load. After a little while it went back to the Gateway is Starting page.
The direct install of 8.3-beta2 is running with no issues on the same machine.
Thank you for providing this. It looks like you’re using colima for Docker on macOS. Admittedly, I hadn’t used colima before but I took it for a quick spin on my M2 Max MBP here and everything seems to work as expected, with the gateway starting up in ~12 seconds.
Just one more piece of information gathering if you wouldn’t mind:
colima status && colima list
Even with the fairly minimal defaults of 2 vCPUs and 2GiB of RAM, a single gateway container seems to launch alright. I captured a brief snippet of my testing with Colima, fwiw:
You’d definitely need to adjust those defaults if you’re running multiple containers to avoid slowdowns.
2 Likes
Oh man
. It didn’t even occur to me that colima itself might be the bottleneck. I’m running a small k8s cluster on the same machine too.
Increased to 4cpu and 8gb memory, and the gateway started instantly with no issues.
I should have realized when the docker commands were taking so long. Thanks a lot!
3 Likes