Gladys Assistant OS: install Gladys on a mini-PC with a simple USB key 🚀

Hello everyone!

It’s official: Gladys Assistant OS is available! :tada:

This is the new official way to install Gladys on a mini-PC: you write the image to a USB key, you boot the mini-PC from it, you answer a few questions, and Gladys installs itself. No more command line, no more docker run to copy-paste :smiling_face_with_sunglasses:

Everything is explained step by step, with a screenshot of each screen, in the new documentation:

:package: What Gladys Assistant OS does

  • Under the hood, it’s a standard Ubuntu Server 26.04 LTS, prepared for Gladys
  • The installer only asks for the language, the keyboard, and your account. With a single disk, there’s not even a disk to choose
  • On first boot, it installs Docker, downloads the latest version of Gladys, and launches it. You can follow the progress on the mini-PC screen or from your phone
  • Gladys updates itself, and Ubuntu installs its security updates automatically
  • An Internet or power outage during the first boot? It resumes where it left off
  • At the end, Gladys is accessible on http://gladysassistant.local

And it’s not a black box: it remains a classic Ubuntu, accessible via SSH, with no default account or password.

:clipboard: What you need for this first version

  • an Intel or AMD mini-PC (x86-64) that boots in UEFI, which is almost all mini-PCs
  • an Ethernet cable
  • a screen and a keyboard, only during installation

On Raspberry Pi, we keep the Raspberry Pi image, and the Docker installation remains for those who already have a server or a NAS. And if Gladys is already running at your place, nothing changes: no need to reinstall!

:books: All the installation documentation revised

I took the opportunity to revise all the installation documentation (in French, English, German, and Spanish) so that Gladys Assistant OS is the first thing we see:

:blue_heart: A huge thank you

Gladys Assistant OS is a community project from start to finish:

  • @howmationfr started the project and did most of the work
  • @cicoub13 took it over, refined it, and released v0.1.0
  • thanks also to everyone who tested and gave feedback in the original topic :folded_hands:

And as always, everything is open source: GitHub - GladysAssistant/ubuntu-server-gladys: Gladys Assistant OS · GitHub

:test_tube: Now it’s your turn to test!

This is a first version: if you have a mini-PC on hand, install it and tell us how it went in a reply to this post! Every feedback on real hardware (Intel N100/N150, Core, AMD Ryzen, NVMe, SATA
) helps to make the installer more reliable. The test checklist is here: HARDWARE-TEST-CHECKLIST.md

Don’t hesitate to give your feedback on the forum :slight_smile:

I’ll take this opportunity to clarify: if you already have Gladys Assistant installed, this doesn’t concern you. It’s mainly useful for new users :sunglasses:

Gladys Assistant OS is nothing more than Ubuntu Server + Docker + Gladys + Watchtower, so nothing new if you followed the Docker tutorial: you already have the same thing at home, no need to reinstall! The only difference is that everything installs automatically, without command lines.

Awesome!!! Great work everyone! :clap:

This is perfect timing, I ordered a new mini-PC that’s arriving in a few days! So I’m really happy to start with Gladys OS.

Replacing the mini-PC because with the current one, which only has 8GB of RAM and is a 2015 model, it’s becoming borderline to manage my installation: I’m at 200 devices (including virtual MQTT devices and devices from external integrations), 300 scenes most of which are based on a trigger, 35 external integrations installed, and a database that takes up 8GB on the hard drive.
I don’t know if it’s a very large installation, but in any case, it has become too large for my little mini-PC.

I tested it and overall it works very well. I have a few comments:

  • I chose France as the country at the beginning, but then in two places I had a mix of French and English:


  • I know the documentation says in two places that the mini-PC must be connected to the network via Ethernet. But I made a mistake and didn’t do it
 The installation then proceeds completely until this screen appears indicating that the Ethernet connection is missing:

I tried plugging in the cable, but it was too late; a configuration was probably not done correctly. I restarted the entire procedure with the cable plugged in and everything ended well.
Perhaps the absence of an Ethernet network should be detected before starting the installation?

Thanks

Nice mix indeed, I’ll check :france:

It’s planned, but I’ll check if you encountered a specific case.

Thank you again for this detailed feedback, it helped me find the cause of the two issues :slightly_smiling_face:

You were right: it was a real bug. When the mini-PC does not get a network address at the beginning of the installation, the Ubuntu installer does not configure any network card on the installed system. Plugging in the cable afterward was therefore useless, although the « Internet Connection Required Â» screen suggested otherwise.

This is fixed here: Configure wired DHCP when the install ran without Ethernet by cicoub13 · Pull Request #12 · GladysAssistant/ubuntu-server-gladys · GitHub

If the installation is done without a cable, Gladys Assistant OS now activates the network on all Ethernet ports: you can plug in the cable afterward, on any port, and the installation resumes on its own. Rather than blocking the installation without a network, I preferred that it works in this case. The fix will be in the next version; in the meantime, you need to plug in the cable before starting the installation.

These screens come from the Ubuntu installer, not from Gladys, and its French translation is incomplete: about half of the texts are missing. Most are translated on Launchpad, but Canonical has not integrated them since October 2023. We cannot fix them on our side, as they are in the installer signed by Canonical.

I opened a bug report with them: Bug #2173317 “Translations not imported from Launchpad since Oct...” : Bugs : subiquity but I have little hope that it will be fixed and available in a new version of Ubuntu.
The documentation will also specify this.

Thanks for the PR @cicoub13, it’s great! I added a comment on Github because I thought of a scenario: some mini-PCs have 2 Ethernet ports (for example on some Beelink S13), and both ports need to work because you don’t always remember which port you used during installation :smiley:

Claude suggested a fix, but it’s not necessarily the only solution, the main thing is just that both ports can work!

@StephaneB A new image of Gladys Assistant OS was published before the weekend by @cicoub13 with the fixes! :slight_smile:

Great, came just in time when my old Raspberry’s SD card died!
Now Gladys is working on a cheap mini PC.

Yes release available since Friday

  • All ports and the case of installation without a cable plugged in are now supported
  • Added documentation explaining the French/English mix

Thanks to both of you.
Now that my new installation is working, I won’t be able to test this new installer version. But it will help the next ones :wink:

Hello,

I ordered a beelink S12 so I will be able to test the installation when I receive it.

Have a nice day.

Hello,
I’m responding to myself to share my experience installing Gladys OS on a mini PC.
I had a Gladys Assistant installation on a Raspberry Pi 4 that was starting to slow down, but I didn’t want to invest too much, so I limited myself to a Beelink mini s12.
I proceeded to install Gladys OS on it without any issues.

A bit of sweat during the installation because I had connected the mini PC to a powerline adapter, being quite far from the router and not having an Ethernet port nearby.
At one point, I lost the internet connection (powerline adapter issue) while downloading Gladys OS.
I went to look for a long enough Ethernet cable to plug it directly into my router, and the installation resumed without any issues (despite a pause of about a quarter of an hour, the time it took to find the cable).

Reboot after removing the installation key and everything is fine.
SSH access from my laptop operational and access to the Gladys interface without any problems.

Then, a small concern when I wanted to move my mini PC to replace my Raspberry Pi.
No network connection and the LEDs on my Ethernet port were off.
As I was replacing the Raspberry Pi, which was accessible, I did not question the Ethernet cable it was connected to at all.
I then struggled for a while to figure out where this could be coming from, but I still replaced the Ethernet cable (one end was broken so it didn’t hold very well) to realize that was all it was.

In the end, the installation went smoothly.

Then, it was my mistake: I wanted to restore my old Gladys configuration that I had previously saved (or so I thought).
When trying to restore it, there was no way to find this backup. And to top it off, I couldn’t restart my Raspberry Pi, so I started from scratch for the Gladys installation.

Thanks for this feedback and adventure story :mountain:
Do you see anything to improve?