# Ignition 8.3.4 docker image not showing perspective in designer

**URL:** <https://forum.inductiveautomation.com/t/ignition-8-3-4-docker-image-not-showing-perspective-in-designer/114487>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [March 13, 2026, 6:36pm UTC](https://forum.inductiveautomation.com/t/ignition-8-3-4-docker-image-not-showing-perspective-in-designer/114487 "2026-03-13T18:36:43Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![akivabrookler](https://avatars.discourse-cdn.com/v4/letter/a/41988e/32.png) [@akivabrookler](https://forum.inductiveautomation.com/u/akivabrookler)\
**Post date:** [March 13, 2026, 6:36pm UTC](https://forum.inductiveautomation.com/t/ignition-8-3-4-docker-image-not-showing-perspective-in-designer/114487/1 "2026-03-13T18:36:43Z")

</div>

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.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/5/8569880d4082bdaabad2a40cd6dab81256bb915f.png)

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/9/4900d0fd948c5047bc3251616d18b640fd7a86f5.png)

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 13, 2026, 6:49pm UTC](https://forum.inductiveautomation.com/t/ignition-8-3-4-docker-image-not-showing-perspective-in-designer/114487/2 "2026-03-13T18:49:48Z")

</div>

What platform/OS are you trying to launch the Designer on?

---

<div class="post-metadata">

**Author:** ![akivabrookler](https://avatars.discourse-cdn.com/v4/letter/a/41988e/32.png) [@akivabrookler](https://forum.inductiveautomation.com/u/akivabrookler)\
**Post date:** [March 13, 2026, 7:25pm UTC](https://forum.inductiveautomation.com/t/ignition-8-3-4-docker-image-not-showing-perspective-in-designer/114487/3 "2026-03-13T19:25:31Z")

</div>

I am launching the designer in the same container as the gateway, so linux

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 13, 2026, 11:23pm UTC](https://forum.inductiveautomation.com/t/ignition-8-3-4-docker-image-not-showing-perspective-in-designer/114487/4 "2026-03-13T23:23:46Z")

</div>

You're launching the graphical designer application out of Docker? How?

---

<div class="post-metadata">

**Author:** ![akivabrookler](https://avatars.discourse-cdn.com/v4/letter/a/41988e/32.png) [@akivabrookler](https://forum.inductiveautomation.com/u/akivabrookler)\
**Post date:** [March 16, 2026, 1:17pm UTC](https://forum.inductiveautomation.com/t/ignition-8-3-4-docker-image-not-showing-perspective-in-designer/114487/5 "2026-03-16T13:17:18Z")

</div>

Part of my container’s set up steps downloads the Linux version of the Ignition Designer onto my docker container.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [March 16, 2026, 1:20pm UTC](https://forum.inductiveautomation.com/t/ignition-8-3-4-docker-image-not-showing-perspective-in-designer/114487/6 "2026-03-16T13:20:29Z")

</div>

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.)

---

<div class="post-metadata">

**Author:** ![akivabrookler](https://avatars.discourse-cdn.com/v4/letter/a/41988e/32.png) [@akivabrookler](https://forum.inductiveautomation.com/u/akivabrookler)\
**Post date:** [March 16, 2026, 1:35pm UTC](https://forum.inductiveautomation.com/t/ignition-8-3-4-docker-image-not-showing-perspective-in-designer/114487/7 "2026-03-16T13:35:44Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [March 16, 2026, 1:40pm UTC](https://forum.inductiveautomation.com/t/ignition-8-3-4-docker-image-not-showing-perspective-in-designer/114487/8 "2026-03-16T13:40:12Z")

</div>

- 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.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 16, 2026, 1:44pm UTC](https://forum.inductiveautomation.com/t/ignition-8-3-4-docker-image-not-showing-perspective-in-designer/114487/9 "2026-03-16T13:44:39Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![akivabrookler](https://avatars.discourse-cdn.com/v4/letter/a/41988e/32.png) [@akivabrookler](https://forum.inductiveautomation.com/u/akivabrookler)\
**Post date:** [March 16, 2026, 1:45pm UTC](https://forum.inductiveautomation.com/t/ignition-8-3-4-docker-image-not-showing-perspective-in-designer/114487/10 "2026-03-16T13:45:59Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 16, 2026, 1:47pm UTC](https://forum.inductiveautomation.com/t/ignition-8-3-4-docker-image-not-showing-perspective-in-designer/114487/11 "2026-03-16T13:47:29Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 16, 2026, 1:51pm UTC](https://forum.inductiveautomation.com/t/ignition-8-3-4-docker-image-not-showing-perspective-in-designer/114487/12 "2026-03-16T13:51:13Z")

</div>

Some potential leads:

- [https://teamdev.com/jxbrowser/releases/2025/v8-13-0/#sandbox-on-linux](https://teamdev.com/jxbrowser/releases/2025/v8-13-0/#sandbox-on-linux)
- [https://teamdev.com/jxbrowser/docs/guides/chromium/#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`.

---

<div class="post-metadata">

**Author:** ![Vincent\_Buescher](https://avatars.discourse-cdn.com/v4/letter/v/a698b9/32.png) [@Vincent\_Buescher](https://forum.inductiveautomation.com/u/Vincent_Buescher)\
**Post date:** [June 15, 2026, 4:31pm UTC](https://forum.inductiveautomation.com/t/ignition-8-3-4-docker-image-not-showing-perspective-in-designer/114487/13 "2026-06-15T16:31:25Z")

</div>

I had the same problem. The console output was:

```python

[JxBrowserEngine-Init-1] ERROR designer.JXBrowserUtil -- Failed to start Browser Engine with options
 com.teamdev.jxbrowser.engine.EngineOptions:
  autoplayEnabled: false
  chromiumDir: C:\Users\xxxxxx\.ignition\cache\resources\jxbrowser\8.16.0
  chromiumSwitches: []
  diskCacheSize: <unknown>
  fileAccessFromFilesAllowed: false
  isGpuDisabled: false
  isIncognitoEnabled:true
  language:en-us
  passwordStore: <unknown>
  remoteDebugginPort: 9222
  renderingMode: OFF_SCREEN
  isSandboxDisabled: false
  secureOriginWhitelist: []
  isTouchMenuEnabled: false
  userAgent: <unknown user agent value>
  userDataDir:C:\Users\xxxxx\AppData\Local\Temp\JxBrowser-UserData-c7e70f61-25c1-4ae6-87f2-89114f2b0e2c
  webSecurityDisabled: false
.
com.teamdev.jxbrowser.engine.ChromiumProcessStartupFailureException: Process exit code: 0
	at com.teamdev.jxbrowser.engine.internal.EngineImpl.newInstance(EngineImpl.java:238)
	at com.teamdev.jxbrowser.engine.Engine.newInstance(Engine.java:167)
	at com.inductiveautomation.ignition.client.util.JxBrowserUtil.lambda$getOrCreateEngine$2(JxBrowserUtil.java:362)
	at com.inductiveautomation.ignition.client.util.JxBrowserUtil.runResourceLockedAction(JxBrowserUtil.java:580)
	at com.inductiveautomation.ignition.client.util.JxBrowserUtil.getOrCreateEngine(JxBrowserUtil.java:362)
	at com.inductiveautomation.ignition.client.util.JxBrowserUtil.getOrCreateEngine(JxBrowserUtil.java:428)
	at com.inductiveautomation.webbrowser.BrowserInstanceManager.lambda$startup$0(BrowserInstanceManager.java:53)
	at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
18:18:44.809 [JxBrowserEngine-Init-1] ERROR WebBrowser -- Failed to initialize BrowserEngine. Web Browser Component can not start!

```

As I’d updated Designer shortly before, I had to clear the cache in C:\Users\xxxx.ignition\cache. Then I reopened the Designer Launcher and started Designer. The Perspective module was back in Designer too.

Hope this helps.
