# Umbrel 1.1 installation tracking

**URL:** <https://community.gladysassistant.com/t/suivi-installation-umbrel-1-1/8853>\
**Category:** Développement\
**Created:** [April 23, 2024, 1:27pm UTC](https://community.gladysassistant.com/t/suivi-installation-umbrel-1-1/8853 "2024-04-23T13:27:31Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\
**Post date:** [April 23, 2024, 1:27pm UTC](https://community.gladysassistant.com/t/suivi-installation-umbrel-1-1/8853/1 "2024-04-23T13:27:31Z")

</div>

Hello

Context: Installation on a Raspberry Pi 4 (RPI4) with an SSD running Umbrel OS 1.1 (released a month ago).  
The integration is under review [here](https://github.com/getumbrel/umbrel-apps/pull/1044), but I wanted to test on a real RPI (not in a VM).

I recently restored a Gladys Plus backup on a brand new Umbrel installation (to test the behavior on this OS).

I get the following error at the end of the restore and had to start the gladys container manually (everything has been working fine since).

```auto
2024-04-23T15:14:36+0200 \u003cinfo\u003e gateway.restoreBackup.js:39 (Gateway.restoreBackup) Backup restored. Need reboot now.
2024-04-23T15:14:36+0200 \u003cinfo\u003e system.shutdown.js:13 (System.shutdown) Database is probably already closed
2024-04-23T15:14:36+0200 \u003cwarn\u003e system.shutdown.js:14 (System.shutdown) Error: SQLITE_MISUSE: Database is closed
    at /src/server/node_modules/sequelize/src/dialects/sqlite/connection-manager.js:31:79
    at node:internal/util:441:7
    at new Promise (\u003canonymous\u003e)
    at node:internal/util:427:12
    at /src/server/node_modules/sequelize/src/dialects/sqlite/connection-manager.js:31:85
    at Array.map (\u003canonymous\u003e)
    at ConnectionManager._onProcessExit (/src/server/node_modules/sequelize/src/dialects/sqlite/connection-manager.js:31:10)
    at ConnectionManager.close (/src/server/node_modules/sequelize/src/dialects/abstract/connection-manager.js:116:23)
    at Sequelize.close (/src/server/node_modules/sequelize/src/sequelize.js:1292:35)
    at System.shutdown (/src/server/lib/system/system.shutdown.js:11:26)
    at Gateway.restoreBackupEvent (/src/server/lib/gateway/gateway.restoreBackupEvent.js:18:23)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at EventEmitter.\u003canonymous\u003e (/src/server/utils/functionsWrapper.js:13:7) {
  errno: 21,
  code: 'SQLITE_MISUSE'
}

```

---

<div class="post-metadata">

**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\
**Post date:** [April 23, 2024, 1:59pm UTC](https://community.gladysassistant.com/t/suivi-installation-umbrel-1-1/8853/2 "2024-04-23T13:59:55Z")

</div>

Ah, it might be due to the option in the **docker-compose**

> restart: on-failure

---

<div class="post-metadata">

**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\
**Post date:** [April 23, 2024, 2:54pm UTC](https://community.gladysassistant.com/t/suivi-installation-umbrel-1-1/8853/3 "2024-04-23T14:54:06Z")

</div>

> [@cicoub13](#):
>
> everything has been working fine since

So I have a strange behavior. The Gladys container cannot contact `localhost` (which is a problem for contacting MQTT).

The `ping localhost` returns `ping: bad address 'localhost'`

The `ping 127.0.0.1` works.

I’ve checked everything (/etc/hosts, DNS, loopback interface, container in network mode: host). I’m stumped

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [April 23, 2024, 3:54pm UTC](https://community.gladysassistant.com/t/suivi-installation-umbrel-1-1/8853/4 "2024-04-23T15:54:30Z")

</div>

> [@cicoub13](#):
>
> Ah, it might be due to the option in the **docker-compose**

Hi @cicoub13 🙂

Indeed, the restore mechanism relies on Gladys being automatically restarted if it «&nbsp;self-kills&nbsp;». If you’re on restart: on-failure, it no longer works. You need to be on restart: always!

[quote=«&nbsp;cicoub13, post:3, topic:8853&nbsp;»]  
So I’m seeing

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [April 24, 2024, 4:24pm UTC](https://community.gladysassistant.com/t/suivi-installation-umbrel-1-1/8853/5 "2024-04-24T16:24:29Z")

</div>

A message has been split into a new topic: [Docker : restart=always vs unless-stopped dans le cas de Gladys?](https://community.gladysassistant.com/t/docker-restart-always-vs-unless-stopped-dans-le-cas-de-gladys/8859)

---

<div class="post-metadata">

**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\
**Post date:** [May 15, 2024, 8:45am UTC](https://community.gladysassistant.com/t/suivi-installation-umbrel-1-1/8853/6 "2024-05-15T08:45:38Z")

</div>

I had managed to get everything working and made the PR here [Add gladys assistant by cicoub13 · Pull Request #1044 · getumbrel/umbrel-apps · GitHub](https://github.com/getumbrel/umbrel-apps/pull/1044)

But they’re asking lots of questions about our fairly extensive access. I’ll reply trying to explain why we need them (like Home Assistant…).

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [May 15, 2024, 3:55pm UTC](https://community.gladysassistant.com/t/suivi-installation-umbrel-1-1/8853/7 "2024-05-15T15:55:41Z")

</div>

Cool, great @cicoub13🙂

I saw the questions; indeed, it’s quite surprising that they’re asking those questions given that they give the same permissions to Home Assistant: [umbrel-apps/home-assistant/docker-compose.yml at master · getumbrel/umbrel-apps · GitHub](https://github.com/getumbrel/umbrel-apps/blob/master/home-assistant/docker-compose.yml)

Let me know if you need help answering

---

<div class="post-metadata">

**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\
**Post date:** [May 20, 2024, 8:21am UTC](https://community.gladysassistant.com/t/suivi-installation-umbrel-1-1/8853/8 "2024-05-20T08:21:03Z")

</div>

[nmfretz (Nathan Fretz) · GitHub](https://github.com/nmfretz) seems to have more expertise and understands a large part of the parameters.

I commented, adding details about our need.

I’m a bit stuck on the `cgroup: host` and `privileged: true`. Could you tell me the reason for these parameters?

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [May 20, 2024, 8:29am UTC](https://community.gladysassistant.com/t/suivi-installation-umbrel-1-1/8853/9 "2024-05-20T08:29:22Z")

</div>

Thanks @cicoub13 for the answers, I’ve added my answers for cgroup and privileged

---

<div class="post-metadata">

**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\
**Post date:** [May 27, 2024, 2:38pm UTC](https://community.gladysassistant.com/t/suivi-installation-umbrel-1-1/8853/10 "2024-05-27T14:38:17Z")

</div>

A **negative** response regarding exposing the Docker daemon (too risky). They propose several solutions here [Add gladys assistant by cicoub13 · Pull Request #1044 · getumbrel/umbrel-apps · GitHub](https://github.com/getumbrel/umbrel-apps/pull/1044#issuecomment-2133467901)

Docker-in-Docker seems interesting to me (even for us), but it seems complex and I wonder about the usefulness for Gladys outside Umb

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [May 27, 2024, 2:54pm UTC](https://community.gladysassistant.com/t/suivi-installation-umbrel-1-1/8853/11 "2024-05-27T14:54:46Z")

</div>

Hello @cicoub13 !

I saw the reply — needs testing, but for me Docker in Docker doesn’t work and it’s actually very shaky.

Running a Zigbee2mqtt container inside another container, will it have access to the system (Privileged? USB port?)

From what I understand, the Umbrel project wants to retain control of the host and not allow containers to launch other containers, whereas that’s exactly what we’re trying to do ^^

If their project doesn’t accept this behavior, rather than implementing hacks, it’s probably better not to allow this behavior in those installations and the user can simply use Z2M in remote mode, same for MQTT…

But it should be tested!

I wonder if these applications (Portainer, Home Assistant) are really used within Umbrel?

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [August 29, 2024, 2:37pm UTC](https://community.gladysassistant.com/t/suivi-installation-umbrel-1-1/8853/12 "2024-08-29T14:37:02Z")

</div>

Hi @cicoub13 🙂 I’m checking in on this topic!

---

<div class="post-metadata">

**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\
**Post date:** [August 30, 2024, 9:15am UTC](https://community.gladysassistant.com/t/suivi-installation-umbrel-1-1/8853/13 "2024-08-30T09:15:28Z")

</div>

In light of their last reply, I gave up. I think the dev/time investment isn’t worth it today.

What I don’t understand is why it’s a yes for HA and not for us. Well, they’re trying to do better, and so we’re a bit late 😐

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [August 30, 2024, 9:34am UTC](https://community.gladysassistant.com/t/suivi-installation-umbrel-1-1/8853/14 "2024-08-30T09:34:40Z")

</div>

What if we just drop the «&nbsp;container launch&nbsp;» part? Since we can now connect to an existing Zigbee2mqtt container, that’s fine 🙂

Given that Gladys detects when the Docker daemon isn’t available, there should normally be no change to the product?

It’s just a single line to change on the Umbrel PR