# Ignition Edge 8.3.4 on ARM64

**URL:** <https://forum.inductiveautomation.com/t/ignition-edge-8-3-4-on-arm64/115388>\
**Category:** Ignition\
**Created:** [May 5, 2026, 8:44pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-8-3-4-on-arm64/115388 "2026-05-05T20:44:54Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![steve.rbo](https://avatars.discourse-cdn.com/v4/letter/s/df788c/32.png) [@steve.rbo](https://forum.inductiveautomation.com/u/steve.rbo)\
**Post date:** [May 5, 2026, 8:44pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-8-3-4-on-arm64/115388/1 "2026-05-05T20:44:54Z")

</div>

I am currently using a Asus IOT Tinker System 3N, installing and running Ignition Edge 8.1.53 worked fine, on other AARCH64 devices (such as raspberry Pi) Ignition Edge 8.3.4 worked fine. However for 8.3.4 it does not want to start and the wrapper log does not generate anything.

---

<div class="post-metadata">

**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\
**Post date:** [May 6, 2026, 4:03am UTC](https://forum.inductiveautomation.com/t/ignition-edge-8-3-4-on-arm64/115388/2 "2026-05-06T04:03:22Z")

</div>

What OS are you running?  
What command (or process) are you using to start Ignition?  
Was 8.3.4 installed on top of the working 8.1 install (as an upgrade)?

---

<div class="post-metadata">

**Author:** ![steve.rbo](https://avatars.discourse-cdn.com/v4/letter/s/df788c/32.png) [@steve.rbo](https://forum.inductiveautomation.com/u/steve.rbo)\
**Post date:** [May 6, 2026, 1:35pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-8-3-4-on-arm64/115388/3 "2026-05-06T13:35:29Z")

</div>

I am running Tinker OS Bookworm with Kernel 6.1 V1.0.4. At one point I had it running but messed up my OS and had to re-start the whole process. As part of a test I went back to 8.1.53. Unfortunately the wrapper log is pretty much empty.

---

<div class="post-metadata">

**Author:** ![steve.rbo](https://avatars.discourse-cdn.com/v4/letter/s/df788c/32.png) [@steve.rbo](https://forum.inductiveautomation.com/u/steve.rbo)\
**Post date:** [May 6, 2026, 8:37pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-8-3-4-on-arm64/115388/4 "2026-05-06T20:37:39Z")

</div>

I was able to start the gateway with

/usr/local/ignition$ sudo ./ignition-gateway /usr/local/ignition/data/ignition.conf

but not using ./ignition.sh start (even when made executable)

---

<div class="post-metadata">

**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\
**Post date:** [May 6, 2026, 9:25pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-8-3-4-on-arm64/115388/5 "2026-05-06T21:25:55Z")

</div>

Can you try running the following command?

```python
uname -s

```

I'm hopeful it returns `Linux` but would like to verify.

Any other outcome if you execute the wrapper script elevated: `sudo ./ignition.sh start`?

That script does suppress many Standard Error outputs...I wish there were an argument to permit verbose / console logging for issues like this.

You could try running `bash -x ./ignition.sh start` to print each command that is executed _before_ executing them. Hopefully the last several lines that are printed will give you some insight as to where the problem is.

Another (more invasive) option would be temporarily edit that ignition.sh file (take a backup first) and replace all instances of `2>/dev/null` with `2>/dev/tty`.

---

<div class="post-metadata">

**Author:** ![steve.rbo](https://avatars.discourse-cdn.com/v4/letter/s/df788c/32.png) [@steve.rbo](https://forum.inductiveautomation.com/u/steve.rbo)\
**Post date:** [May 6, 2026, 10:09pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-8-3-4-on-arm64/115388/6 "2026-05-06T22:09:23Z")

</div>

Yes it does say Linux, I was able to run it but not from the ignition.sh , i ended up creating a service going straight to ignition-gateway and pointing it to the config file.

Example:

[Unit]  
Description=Ignition Gateway  
After=network.target  
Wants=network.target

[Service]  
Type=simple  
User=root  
WorkingDirectory=/usr/local/ignition  
ExecStart=/usr/local/ignition/ignition-gateway /usr/local/ignition/data/ignition.conf  
Restart=on-failure  
RestartSec=10  
StandardOutput=journal  
StandardError=journal

[Install]  
WantedBy=multi-user.target