I am running Ignition 8.3.4 docker image. My gateway shows that perspective is enabled, but perspective does not show up in my designer. I checked both my designer and gateway logs and did not see anything indicative of the problem. I tried restarting my gateway, restarting my designer, disabling and re-enabling the perspective module. This same gateway backup will load completely fine on Windows.
What platform/OS are you trying to launch the Designer on?
I am launching the designer in the same container as the gateway, so linux
You're launching the graphical designer application out of Docker? How?
3 Likes
Part of my container’s set up steps downloads the Linux version of the Ignition Designer onto my docker container.
Are you also loading all of the Xserver kit necessary to remote operate a GUI application?
(Rhetorical question. Designers should not be run on the same machine as a gateway.)
They are running on the same machine, just for development, this isn’t a production gateway. What’s the issue with having designer and gateway on the same machine?
- Different memory and CPU use patterns,
- Requires allocating extra memory to the gateway VM/container
- Deludes users about comms configurations because everything is going through
localhost. - Remote desktop and similar tech is less efficient than actual designer comms to a gateway.
It's fine for dev, whatever, but trying to run GUI apps in Docker is extremely uncommon, you have to get all the display env variables and libraries and whatever else GUI apps might expect set up and working yourself, and even then you end up "viewing" the apps via X11 forwarding or VNC/RDP.
You probably don't have a Perspective module in the Designer because Chromium isn't loading in this weird environment for some reason. You might get a clue in the Designer log or the designerlauncher.log file, but you're on your own in this unsupported setup.
2 Likes
Is there any reason you can think why this works fine for 8.3.3 but once I upgrade to 8.3.4 perspective in the designer stops working?
JXBrowser (Chromium) was upgraded from 8.12.1 to 8.16.0 in 8.3.4.
I don't know why exactly that would break it, but it's the most likely candidate.
Some potential leads:
- https://teamdev.com/jxbrowser/releases/2025/v8-13-0/#sandbox-on-linux
- https://teamdev.com/jxbrowser/docs/guides/chromium/#linux
would need to check the log files to see if it's failing to initialize with SandboxNotSupportedException.