Installing Home Assistant Supervised using Debian 12

nickrout · January 25, 2024, 12:12am

LTS means they provide updates Long Term, not that you shouldn’t use them!

Tamsy · January 25, 2024, 12:23am

But neither you should use them. I have not read something about a security flaw or therelike with Docker CE 24.x.x which would make it wise to upgrade to 25.0.x.

But here again it seems to be a matter of the point of view: While some prefer to stay on the “bleeding edge” when it comes to upgrades (even these are not mandatory security updates), others prefer to stay on the more conservative side and wait a while to let the latest releases “mature” before installing them.

To each his own.

nickrout · January 25, 2024, 9:19am

Yeah take your point. Then again many make the legit comment that there are never enough testers.

euntdomus · January 25, 2024, 11:43am

The release of docker-ce 25.0.x appears to have introduced multiple issues for Supervised HA.

docker-ce 25.0.0 introduced a change in networking behavior the prevented Supervisor from starting. That issue was resolved with the release of docker-ce 25.0.1.
Once HA Supervised was operable on docker-ce 25.0.1 it became apparent there is an issue with the HA InfluxDB integration that may be caused by a change in docker file system mounting behavior introduced in moby v25.

In line with the cautionary approach advised by @Tamsy , it may be advisable to not use docker-ce 25.0.x until more is understood about the impact of the docker file system mounting behavior change.

See

github.com/home-assistant/core

HA InfluxDB integration fails with Read-only file system error following upgrade to Docker 25.0.x

opened 09:16PM - 24 Jan 24 UTC

davecoutts

integration: influxdb

### The problem Following an upgrade from docker-ce 24.0.7 to 25.0.1 the [Influ…xDB](https://www.home-assistant.io/integrations/influxdb/) integration fails with the error message, `ERROR (influxdb) [homeassistant.components.influxdb] Cannot connect to InfluxDB due to '[Errno 30] Read-only file system'. Please check that the provided connection details (host, port, etc.) are correct and that your InfluxDB server is running and accessible.` No data is received in InfluxDB from HA after the upgrade from docker-ce 24.0.7 to 25.0.1. The '[Errno 30] Read-only file system' error message appears to be coming from a influx.write_api call in [this](https://github.com/home-assistant/core/blob/909e58066d202df9f599dcedeabbac59cf9336af/homeassistant/components/influxdb/__init__.py#L365) code block of the [InfluxDB](https://www.home-assistant.io/integrations/influxdb/) integration. The error may be caused by a change in mounting behavior introduced in moby v25.0.x that prevents multiprocessing from creating a /dev/shm file, as reported in this [moby/issues/47158](https://github.com/moby/moby/issues/47158) issue. The influxdb python client [uses](https://github.com/influxdata/influxdb-client-python/blob/d7181fab9612dd0558822fc40e5d9ccf5a15d56b/influxdb_client/configuration.py#L17) multiprocessing. If the issue is python multiprocessing and docker-ce 25.0.x related, other HA integrations that use multiprocessing may be impacted Downgrading from docker-ce 25.0.1 to 24.0.7 restores the HA InfluxDB integration functionality, suggesting it is an issue brought about by a change introduced in docker-ce 25.0.x. ### What version of Home Assistant Core has the issue? core-2024.1.5 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant Supervised ### Integration causing the issue InfluxDB ### Link to integration documentation on our website https://www.home-assistant.io/integrations/influxdb/ ### Diagnostics information _No response_ ### Example YAML snippet ```yaml # influxdb section from configuration.yaml influxdb: api_version: 2 host: 192.168.1.2 port: 8086 ssl: false token: REDACTED organization: REDACTED bucket: home_assistant override_measurement: sensor default_measurement: state ``` ### Anything in the logs that might be useful for us? ```txt grep -i influxdb /usr/share/hassio/homeassistant/home-assistant.log.* /usr/share/hassio/homeassistant/home-assistant.log.1:2024-01-24 17:46:44.641 ERROR (influxdb) [homeassistant.components.influxdb] Cannot connect to InfluxDB due to '[Errno 30] Read-only file system'. Please check that the provided connection details (host, port, etc.) are correct and that your InfluxDB server is running and accessible. ``` ### Additional information The commands used to downgrade and upgrade docker-ce on debian 12 bookworm. #### Install docker-ce v24.0.7 ``` sudo apt install \ docker-ce=5:24.0.7-1~debian.12~bookworm \ docker-ce-cli=5:24.0.7-1~debian.12~bookworm \ docker-buildx-plugin=0.11.2-1~debian.12~bookworm \ docker-compose-plugin=2.21.0-1~debian.12~bookworm \ docker-ce-rootless-extras=5:24.0.7-1~debian.12~bookworm ``` #### Install docker-ce v25.0.1 ``` sudo apt install \ docker-ce=5:25.0.1-1~debian.12~bookworm \ docker-ce-cli=5:25.0.1-1~debian.12~bookworm \ docker-buildx-plugin=0.12.1-1~debian.12~bookworm \ docker-compose-plugin=2.24.2-1~debian.12~bookworm \ docker-ce-rootless-extras=5:25.0.1-1~debian.12~bookworm ``` #### InfluxDB host The InfluxDB instance used during testing is on a separate server to the one that hosts HA. No changes were made to the InfluxDB host environment. The InfluxDB version is v2.7.5

github.com/moby/moby

Mounting read-only /dev behaviour changed in v25

opened 11:58AM - 22 Jan 24 UTC

aigarius

kind/question status/0-triage version/25.0

### Description Since Docker upgrade to v25 the sub-filesystems in /dev (in p…articular /dev/shm) get mounted read-only if the Docker container has a volume specified that mounts /dev as read-only, which is a change from behaviour in v24. Upgrading from docker-ce version `5:24.0.7-1~ubuntu.22.04~jammy` to `5:25.0.0-1~ubuntu.22.04~jammy` (and containerd.io version `1.6.15-1` to `1.6.27-1`) causes the change in permissions of /dev/shm that breaks a lot of software, in out case Python multiprocessing module fails to create a new instance of https://docs.python.org/3.10/library/multiprocessing.html#multiprocessing.Value as it is unable to create a file in /dev/shm ### Reproduce 1. docker run --rm -d -v /dev:/dev:ro --name test123 ubuntu:jammy sleep 3600 2. docker exec -it test123 mount | grep /dev/shm 3. `tmpfs on /dev/shm type tmpfs (ro,nosuid,nodev,inode64)` Other file systems are also affected: ``` devpts on /dev/pts type devpts (ro,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /dev/shm type tmpfs (ro,nosuid,nodev,inode64) mqueue on /dev/mqueue type mqueue (ro,nosuid,nodev,noexec,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (ro,relatime,pagesize=2M) ``` ### Expected behavior docker exec -it test123 mount | grep /dev/shm `tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)` ``` devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64) mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) ``` ### docker version ```bash Client: Docker Engine - Community Version: 25.0.0 API version: 1.44 Go version: go1.21.6 Git commit: e758fe5 Built: Thu Jan 18 17:09:49 2024 OS/Arch: linux/amd64 Context: default Server: Docker Engine - Community Engine: Version: 25.0.0 API version: 1.44 (minimum version 1.24) Go version: go1.21.6 Git commit: 615dfdf Built: Thu Jan 18 17:09:49 2024 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.27 GitCommit: a1496014c916f9e62104b33d1bb5bd03b0858e59 runc: Version: 1.1.11 GitCommit: v1.1.11-0-g4bccb38 docker-init: Version: 0.19.0 GitCommit: de40ad0 ``` ### docker info ```bash Client: Docker Engine - Community Version: 25.0.0 Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.11.2 Path: /usr/libexec/docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: v2.24.1 Path: /usr/libexec/docker/cli-plugins/docker-compose scan: Docker Scan (Docker Inc.) Version: v0.23.0 Path: /usr/libexec/docker/cli-plugins/docker-scan Server: Containers: 23 Running: 22 Paused: 0 Stopped: 1 Images: 45 Server Version: 25.0.0 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Using metacopy: false Native Overlay Diff: true userxattr: false Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 2 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog Swarm: inactive Runtimes: runc io.containerd.runc.v2 Default Runtime: runc Init Binary: docker-init containerd version: a1496014c916f9e62104b33d1bb5bd03b0858e59 runc version: v1.1.11-0-g4bccb38 init version: de40ad0 Security Options: apparmor seccomp Profile: builtin cgroupns Kernel Version: 5.15.0-79-generic Operating System: Ubuntu 22.04.3 LTS OSType: linux Architecture: x86_64 CPUs: 12 Total Memory: 7.532GiB Name: xxx ID: WJDD:VNV2:5UUD:M5GY:AVR6:4GFI:WFDT:V66E:OPBY:CGB5:DQ3A:DTPM Docker Root Dir: /var/lib/docker Debug Mode: false Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false ``` ### Additional Info _No response_

kanga_who · January 25, 2024, 11:45am

It’s already been discussed in this thread, read above.

nickrout · March 2, 2024, 8:25pm

Simply because the pi isn’t x86_64. You wanted this thread Installing Home Assistant Supervised on a Raspberry Pi using Debian 12

As it says in post 1

This guide will help you to install Home Assistant Supervised, on almost any machine type you choose. This guide has been tested on machines including a Lenovo m72e, Dell Optiplex SFF 990, Dell Optiplex USFF 780 and a HP T520 thin client. If you are using a Raspberry Pi , follow this guide.

Guggu · March 2, 2024, 11:15pm

thanks,

I’ve learnt my lesson: if anything else fails, read the instructions

idesignzone · March 13, 2024, 11:55pm

I am facing the sam issue while installing on Debian 12 VPS.
Editing /etc/network/interfaces won’t help and I get name resolution errors.
This also kicks me off the bash and I can’t reconnect to the server after a reboot.

I have followed This article and I am already running an instance on Vultr.
For some reason when I install network-manager on another VPS (Same config as Vultr) I get the The

following network interfaces were found in /etc/network/interfaces which means they are currently configured by ifupdown:

Never had this ifupdown problem on Vultur VPS!

As I see there are 2 main problems here:
1: ifupdown editing the /etc/network/interfaces and messing things up
2: systemd-resolved breaking the network interface

I was able to solve number 2 on Vultr, but it just won’t work on this server with the same config.

PHalstead · March 22, 2024, 11:16pm

In step 2.2 when I type the first command (wget https://github.com/home-assistant/os-agent/releases/download/1.6.0/os-agent_1.6.0_linux_x86_64.deb) the connection times out. It tries 20 times and then gives up. … I’m up to 60. Is there a problem with the command, with my patience, or what? Advice?

THX

Tamsy · March 23, 2024, 12:52am

Welcome to the forum, Paul

Have you checked whether DNS on the Debian installation can still resolve hostnames? What does the logfile show when running wget https://… ?

Check whether systemd-resolved is correctly installed:

dpkg -s  systemd-resolved

The output should contain similar to:

Version: 252.17-1~deb12u1
Replaces: resolvconf, systemd (<< 251.3-2~)
Provides: resolvconf

In case systemd-resolved is not installed run:

sudo apt-get install systemd-resolved

If DNS is still unable to resolve hostnames after making sure that systemd-resolved is installed and correctly running do further readings about the issue here and here.

PHalstead · March 23, 2024, 5:21am

Thx for the welcome! I feel like I’m over my head as I am just starting out. I’ve tried several things and it looks like my root problem is this message: The package os-agent needs to be reinstalled, but I can’t find an archive for it." I’ve done several searches and can’t find an answer to that one!

kanga_who · March 23, 2024, 5:34am

It’s part of the installation instructions

PHalstead · March 30, 2024, 12:02am

I am really frustrated! I have restarted, retried and keep running into different roadblocks. I now have a stable dual boot system with Windows 11 and the latest Debian install GUI. I opened the Terminal and started following these instructions carefully. (Of course, using Terminal in the GUI, the very first command line is just “su” to get to the root rather than the longer “sudo -i”.

This time when I got to:

curl -fsSL get.docker.com | sh

I get:

curl: (6) Could not resolve host: get.docker.com

I’ve seen this question before and the answers were above my head. Can someone give me simple step-by-step commands to run in the terminal to get through this step/command??

kanga_who · March 30, 2024, 12:16am

This guide covers installing HA Supervised on a Debian 12 based system, no GUI and no dual booting.

If you are installing in some way that is outside of the scope of the guide, please don’t ask for support as you have not followed the guide.

PHalstead · March 30, 2024, 1:26am

Where can I get help. Certainly I’m not the only one hot using a Rasberry Pi.

Tamsy · March 30, 2024, 1:43am

As for installing Home Assistant Supervised on a Raspberry Pi using Debian 12 there is even a dedicated guide for doing so.

Nevertheless same with this guide: No GUI and no dual booting!

Is there any special reason why you want to install HA Supervised? I recommend you to stay away from HA Supervised since this kind of installation makes solid Linux knowledge mandatory.

Home Assistant Operating System (HA OS) might be more suitable for you and you dont need much Linux knowledge to install and run Home Assistant:

For an in-depth reading about the latter look HERE.

BTW, the Search-function of this forum works pretty well

nickrout · March 30, 2024, 8:59am

You have a dns issue.

nickrout · March 30, 2024, 9:19am

It will not make a difference if the computer is dual booted.

kanga_who · March 30, 2024, 9:43am

I’d suggest trying to dual boot Windows 11 and desktop Debian on a Pi while using the x86/64 guide will almost certainly make a difference.

nickrout · March 30, 2024, 9:48am

Are you saying this because of the desktop on debian?