# Linux installation **URL:** \ **Category:** Ignition\ **Created:** [March 5, 2021, 7:29am UTC](https://forum.inductiveautomation.com/t/linux-installation/44142 "2021-03-05T07:29:20Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![jrd](https://avatars.discourse-cdn.com/v4/letter/j/b9bd4f/32.png) [@jrd](https://forum.inductiveautomation.com/u/jrd)\ **Post date:** [March 5, 2021, 7:29am UTC](https://forum.inductiveautomation.com/t/linux-installation/44142/1 "2021-03-05T07:29:20Z")
First time installing Ignition on linux / raspberry pi using download " [Ignition Edge - Linux AARCH64.zip" Followed all instructions until starting ignition: “WARNING: Ignition-Gateway may have failed to start” Wrapper log, inter alia, states “License error.: A valid license was not found in the Wrapper configuration file. The Java Service Wrapper requires a License Key to activate the software. …” Do I need to install Java? I understood that was no longer required. Any other suggestions please ---
**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 5, 2021, 2:48pm UTC](https://forum.inductiveautomation.com/t/linux-installation/44142/2 "2021-03-05T14:48:51Z")
What hardware version of RPi are you using and what OS do you have installed? ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [March 5, 2021, 3:59pm UTC](https://forum.inductiveautomation.com/t/linux-installation/44142/3 "2021-03-05T15:59:51Z")
More than likely, you’re running the 32-bit version of Raspberry Pi OS (64-bit is still in “beta” so you have to dig a little to find it on their website). In that case, you’d need our 32-bit ARMHF install. If you can post the output of `uname -a` from your terminal along with the info @Kevin.Herron mentioned, it would be useful for helping troubleshoot. ---
**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\ **Post date:** [March 5, 2021, 4:07pm UTC](https://forum.inductiveautomation.com/t/linux-installation/44142/4 "2021-03-05T16:07:47Z")
> [@Ignition 8 and up Raspberry Pi](https://forum.inductiveautomation.com/t/ignition-8-and-up-raspberry-pi/43729/2): > > I’m going to give the 64-bit OS beta a try as well > > [Index of /raspios\_arm64/images (raspberrypi.org)](https://downloads.raspberrypi.org/raspios_arm64/images/) I've got the 64bit beta loaded up on a Pi right now, haven't gotten to test Ignition on it yet, but I am hopeful 🙂 ---
**Author:** ![jrd](https://avatars.discourse-cdn.com/v4/letter/j/b9bd4f/32.png) [@jrd](https://forum.inductiveautomation.com/u/jrd)\ **Post date:** [March 5, 2021, 4:09pm UTC](https://forum.inductiveautomation.com/t/linux-installation/44142/5 "2021-03-05T16:09:30Z")
Hardware: R Pi 4B 8Gb OS: NOOBS Linux raspberrypi 5.10.17-v7L+ #1403 SMP Mon Feb 22 11:33:35 GMT 2021 armv7L GNU/Linux ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [March 5, 2021, 4:14pm UTC](https://forum.inductiveautomation.com/t/linux-installation/44142/6 "2021-03-05T16:14:50Z")
@jrd, `armv7L` indicates a 32-bit host OS… Try giving the [Ignition - Linux ARMHF 32-bit zip (1458MB)](https://files.inductiveautomation.com/release/ia/8.1.3/20210303-0915/Ignition-linux-armhf-8.1.3.zip) install a try! ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [March 5, 2021, 4:16pm UTC](https://forum.inductiveautomation.com/t/linux-installation/44142/7 "2021-03-05T16:16:10Z")
Or, since you’re on an **8GB** Rasp Pi 4 (NICE 🙂 ), unless you’ve got a lot of other things setup on there already, you might try installing the 64-bit beta that @dkhayes117 mentioned above… ---
**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\ **Post date:** [March 5, 2021, 4:39pm UTC](https://forum.inductiveautomation.com/t/linux-installation/44142/8 "2021-03-05T16:39:38Z")
Hmm, I just downloaded the client launcher for Linux on 64bit RPi, and executing the clientlauncher.sh file yields ```auto clientlauncher.sh: 4: clientlauncher.sh: Bad substitution clientlauncher.sh: 7: clientlauncher.sh: [[: not found clientlauncher.sh: 13: clientlauncher.sh: [[: not found ``` ---
**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 5, 2021, 4:41pm UTC](https://forum.inductiveautomation.com/t/linux-installation/44142/10 "2021-03-05T16:41:28Z")
Launchers don’t run _on_ the RPi, only the gateway does. Or a Perspective session in a web browser. You’ll have to launch the Designer or Vision Client elsewhere. (there is a bit of a hack floating around to launch a Vision Client via shell script and your own local Java install, though…) ---
**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\ **Post date:** [March 5, 2021, 4:47pm UTC](https://forum.inductiveautomation.com/t/linux-installation/44142/11 "2021-03-05T16:47:22Z")
I’m still on v7.9 and I’m pretty sure I used the native client launcher on the 32 bit version of RPi. I must be missing Java. ---
**Author:** ![jrd](https://avatars.discourse-cdn.com/v4/letter/j/b9bd4f/32.png) [@jrd](https://forum.inductiveautomation.com/u/jrd)\ **Post date:** [March 5, 2021, 5:16pm UTC](https://forum.inductiveautomation.com/t/linux-installation/44142/12 "2021-03-05T17:16:07Z")
OOPS My first post stated the incorrect Ignition download I actually downloaded “Ignition-linux-armhf-8.1.3.zip”. I only want Gateway on the Pi. The designer will be elsewhere. I prefer to stick with 32bit as there will be other stuff on it and I don’t want beta 64 So the original problem remains: “WARNING: Ignition-Gateway may have failed to start”! … and error log appears to blame Java ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [March 5, 2021, 6:01pm UTC](https://forum.inductiveautomation.com/t/linux-installation/44142/13 "2021-03-05T18:01:45Z")
One thing I have noticed is that on a fresh unzip, if you first attempt to run the gateway in the console with `./ignition.sh console`, it does not decompress the JRE and you’ll end up with some errors related to java. You can force the JRE unpack with `./ignition.sh checkRuntimes`. If you’re installing as a service with systemd (to run on startup), then it takes care of this automatically. Here is a little run-through of an install on a Pi 4 (Raspberry Pi OS, 32-bit) that hopefully can provide you some helpful insights. This includes making the gateway run as the `pi` user instead of root. [![asciicast](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/2/026e44ef3c5cb7589a8de8bbbdada7f1bcaf54d7.svg)](https://asciinema.org/a/9arzWpv8noTegVLDiya9uFrCc) ---
**Author:** ![jrd](https://avatars.discourse-cdn.com/v4/letter/j/b9bd4f/32.png) [@jrd](https://forum.inductiveautomation.com/u/jrd)\ **Post date:** [March 5, 2021, 8:06pm UTC](https://forum.inductiveautomation.com/t/linux-installation/44142/14 "2021-03-05T20:06:44Z")
I tried that. results ![p1](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/7/f744c1158c026f97051b047043ede9ff6fc52812.png) and journalctl contents: ![p2](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/6/a6b71951ffbc19234733cde34e8b3bb426d86bb7.png) ==\> FAILED TO START IGNITION-GATEWAY ---
**Author:** ![Kevin.Collins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.collins/32/13497_2.png) [@Kevin.Collins](https://forum.inductiveautomation.com/u/Kevin.Collins)\ **Post date:** [March 6, 2021, 3:10pm UTC](https://forum.inductiveautomation.com/t/linux-installation/44142/15 "2021-03-06T15:10:25Z")
(Did you also make the adjustment to the systemd definition, `User=` directive?). Let’s also see the tail of the wrapper log: ```auto tail -n 50 ~/ignition/logs/wrapper.log ``` … that should help show us exactly what the Ignition service itself failed with. ---
**Author:** ![jrd](https://avatars.discourse-cdn.com/v4/letter/j/b9bd4f/32.png) [@jrd](https://forum.inductiveautomation.com/u/jrd)\ **Post date:** [March 7, 2021, 1:27am UTC](https://forum.inductiveautomation.com/t/linux-installation/44142/16 "2021-03-07T01:27:08Z")
Hi Kevin No I did not adjust systemd definition I am new to unix, and did some searches but still don’t know what to do Could you provide procedure ---
**Author:** ![adellaci](https://avatars.discourse-cdn.com/v4/letter/a/f1d935/32.png) [@adellaci](https://forum.inductiveautomation.com/u/adellaci)\ **Post date:** [March 7, 2021, 11:46pm UTC](https://forum.inductiveautomation.com/t/linux-installation/44142/17 "2021-03-07T23:46:39Z")
I got mine running on a Raspberry Pi 4 8 GB, w/ Ubuntu Groovy for ARM ---
**Author:** ![jrd](https://avatars.discourse-cdn.com/v4/letter/j/b9bd4f/32.png) [@jrd](https://forum.inductiveautomation.com/u/jrd)\ **Post date:** [March 10, 2021, 12:36am UTC](https://forum.inductiveautomation.com/t/linux-installation/44142/18 "2021-03-10T00:36:15Z")
I reinstalled from scratch on clean system and all worked fine. Not sure what caused the issue …… Thanks for the assistance