Install Attempt On Trixie - My Bad - Fails on Docker

[skutoroff]

A year ago this month I used your process to install Home Assistant Supervised on Bookworm for a Pi 4, later moved to a Pi 400.
I think I provided a few minor suggestions too.

HA Supervised has been running splendidly ever since. I update Bookworm and HA with no problems. I backup my SD card using SD Card Copy just in case. Rotate SD cards too.

With HA Supervised being deprecated, I'm looking at other options because I don't want to dedicate a Pi to one application. My Pi 400 runs HA Supervised, PiHole, and my expansion of Github project Infinitive for monitoring my Carrier AC system. One Pi, three things. Not one Pi one thing.

Back to the point. Created a new SD card with Trixie and tried to install HA Supervised, first using the HA instructions. Yours is better and theirs didn't work.
Refresh clean the SD with Trixie and tried again with your Bookworm instructions. It failed at the Docker install.
Don't know if using Trixie is the cause, but assume it is. Reporting this as an FYI as Trixie is here.

Here is the output.

docker-compose

Installing dependencies:
docker-buildx docker-cli

Suggested packages:
docker-doc

REMOVING:
docker-ce docker-ce-cli

Summary:
Upgrading: 0, Installing: 3, Removing: 2, Not Upgrading: 0
Download size: 28.7 MB
Space needed: 26.1 MB / 113 GB available

Get:1 http://deb.debian.org/debian trixie/main arm64 docker-buildx arm64 0.13.1+ds1-3 [11.3 MB]
Get:2 http://deb.debian.org/debian trixie/main arm64 docker-cli arm64 26.1.5+dfsg1-9+b9 [6,315 kB]
Get:3 http://deb.debian.org/debian trixie/main arm64 docker-compose arm64 2.26.1-4 [11.1 MB]
Fetched 28.7 MB in 3s (9,195 kB/s)
(Reading database ... 121069 files and directories currently installed.)
Removing docker-ce (5:28.5.2-1debian.13trixie) ...
Removing docker-ce-cli (5:28.5.2-1debian.13trixie) ...
Selecting previously unselected package docker-buildx.
(Reading database ... 120862 files and directories currently installed.)
Preparing to unpack .../docker-buildx_0.13.1+ds1-3_arm64.deb ...
Unpacking docker-buildx (0.13.1+ds1-3) ...
dpkg: error processing archive /var/cache/apt/archives/docker-buildx_0.13.1+ds1-3_arm64.deb (--unpack):
trying to overwrite '/usr/libexec/docker/cli-plugins/docker-buildx', which is also in package docker-buildx-plugin (0.29.1-1debian
.13trixie)
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Selecting previously unselected package docker-cli.
Preparing to unpack .../docker-cli_26.1.5+dfsg1-9+b9_arm64.deb ...
Unpacking docker-cli (26.1.5+dfsg1-9+b9) ...
Selecting previously unselected package docker-compose.
Preparing to unpack .../docker-compose_2.26.1-4_arm64.deb ...
Unpacking docker-compose (2.26.1-4) ...
dpkg: error processing archive /var/cache/apt/archives/docker-compose_2.26.1-4_arm64.deb (--unpack):

trying to overwrite '/usr/libexec/docker/cli-plugins/docker-compose', which is also in package docker-compose-plugin (2.40.3-1debi
an.13trixie)
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/docker-buildx_0.13.1+ds1-3_arm64.deb
/var/cache/apt/archives/docker-compose_2.26.1-4_arm64.deb
Error: Sub-process /usr/bin/dpkg returned an error code (1)

No matter the outcome, thanks the effort.
Cheers,
SK!

[HuckleberryLovesYou]

Hi Steven Kutoroff,

thanks for reaching out to me and for your kind words!

Referring to the issue you're experiencing:

Don't know if using Trixie is the cause, but assume it is. Reporting this as an FYI as Trixie is here.

You are correct. Using Trixie caused the problem. Thanks for reporting it.

The problem is caused by Debian 13 shipping its own docker stack. Basically, it was trying to install docker compose twice, which correctly resulted in an error. The new Debian-managed docker stack isn't officially supported by Homeassistant, but replaced the name for the docker compose package supplied by the docker version. The docker version is now called docker-compose-plugin.

Would it be possible for you to test the installation process further? If the rest works fine, I'm going to add the new dependency installation to the README and make Debian Trixie supported by my instructions.

To resolve your current problem, you should do the following steps to ensure you're using the correct versions:

1. First, remove any docker packages coming from the Debian or Docker repo:

sudo apt remove docker.io docker-buildx docker-buildx-plugin docker-compose

2. Then, fix any broken packages and dependencies

sudo apt -f install

3. Remove unused packages

sudo apt autoremove

4. Then run the Trixie version of the command. This works on Trixie, but not Bookworm.

sudo apt update && sudo apt install -y curl libffi-dev libssl-dev python3-dev python3 python3-pip && curl -fsSL https://get.docker.com -o get-docker.sh && sudo sh get-docker.sh && sudo rm get-docker.sh && sudo apt install -y docker-compose-plugin && sudo systemctl enable docker && sudo usermod -aG docker $(whoami) && sudo mkdir -p $HOME/docker-data

Let me know if that helped and if you would like to test the installation process further.

Best regards,

Tim Matheis

[skutoroff]

Tim, Below I have pasted my notes when attempting to install HA Supervised on Trixie… 11/05 Install Trixie on Samsung 128GB Endurance SD. Install gparted. Unable to install HA Supervised (tried 2x). … 11/09 On Trixie, installed docker using: https://linuxiac.com/how-to-install-docker-on-debian-13-trixie/, resumed HA install process. Failed on HA deb file, permission denied. One go Failed, HA on Trixie is not permitted. Give up installing HA on Trixie. I didm’t know why my first attempts failed, but I gathered on 11/09 that Docker was the problem and found and used the above docker install work around. With that, I was able to get all the way to your step “Installation of Homeassistant-supervised” with no problem. Then problem. The homeassistant-supervised.deb file would not install. Many tries. I noticed one error among many that either said Trixie or Debian 13 was not supported. I wasn’t able to capture the exact message, but I got the message and gave up, as noted. The note about gparted is another experiment I was looking into. I wanted to see if I could run HAOS and Trixie (or even Bookworm) on a Pi5 with some virtualization OS. Could not find a way around the way Raspberry Pi ISO files have two partitions, one MSDOS and one EXT4. Other problems with the idea as well given the state of Pi. I was willing to buy a Raspberry carrier board and a CM5 8/32 to run it on. If it would work and when a CM5 with 8G RAM and 32GB on board SSD becomes available. I don’t have a need for this otherwise. Back to your suggestion. in spite of determining that that the otherwise fine people from HA insist that I should abandon HA Supervised and certainly not use Trixie, I don’t give up easily. I think they’ve put a test for the target OS in the install. I’m not prepared to find a way past that, if true. I could abandon Home Assistant with minor loss of functionality, I use Hubitat and all my Z-Wave and Zigbee devices are on Hubitat. I am using HA as a curiosity and because there are some good things about it. A few things work better on HA than Hubitat. Some things I like too. I like running HA, my Infinitive <https://github.com/skutoroff/Infinitive-Carrier-HVAC-Enhanced>, and PiHole on one Pi400 all with super low loads. So… I’ll try again using your suggestion while fully expecting the HA final install step to fail. Maybe I’ll get lucky. It may be a few days before I try. Thanks. Cheers, SK!

…

On Nov 15, 2025, at 10:15, Tim Matheis ***@***.***> wrote: HuckleberryLovesYou left a comment (HuckleberryLovesYou/Homeassistant-Supervised-on-Raspberry-Pi-5#35) <#35 (comment)> Hi Steven Kutoroff, thanks for reaching out to me and for your kind words! Referring to the issue you're experiencing: Don't know if using Trixie is the cause, but assume it is. Reporting this as an FYI as Trixie is here. You are correct. Using Trixie caused the problem. Thanks for reporting it. The problem is caused by Debian 13 shipping its own docker stack. Basically, it was trying to install docker compose twice, which correctly resulted in an error. The new Debian-managed docker stack isn't officially supported by Homeassistant, but replaced the name for the docker compose package supplied by the docker version. The docker version is now called docker-compose-plugin. Would it be possible for you to test the installation process further? If the rest works fine, I'm going to add the new dependency installation to the README and make Debian Trixie supported by my instructions. To resolve your current problem, you should do the following steps to ensure you're using the correct versions: First, remove any docker packages coming from the Debian or Docker repo: sudo apt remove docker.io docker-buildx docker-buildx-plugin docker-compose Then, fix any broken packages and dependencies sudo apt -f install Remove unused packages sudo apt autoremove Then run the Trixie version of the command. This works on Trixie, but not Bookworm. sudo apt update && sudo apt install -y curl libffi-dev libssl-dev python3-dev python3 python3-pip && curl -fsSL https://get.docker.com -o get-docker.sh && sudo sh get-docker.sh && sudo rm get-docker.sh && sudo apt install -y docker-compose-plugin && sudo systemctl enable docker && sudo usermod -aG docker $(whoami) && sudo mkdir -p $HOME/docker-data Let me know if that helped and if you would like to test the installation process further. Best regards, Tim Matheis — Reply to this email directly, view it on GitHub <#35 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB3PQBWMUU2LFXIBOVJEGTL3447QVAVCNFSM6AAAAACLPM6QYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMZWGU4DANZYHA>. You are receiving this because you authored the thread.

[skutoroff]

Tim, Quiet Sunday AM. I fresh installed Trixie on a 128GB SD card, Fully updated. Note: The target was a Pi 4, not a Pi 5 as your instructions specify, Hope this doesn’t spoil the result. Board was actually a bare Pi400 removed from one with a busted keyboard. I didn’t want to mess with my Pi5 unless it would make a difference. Changing from NVMe boot to SD boot is a bit messy and scary. Plus, my ultimate target remains that Pi400 bare board. I copied your email notes to a text file and moved it to the target so I could work full screen. Then I pasted the final step output to the same file and moved it back for this email. Here is what happened…

…

-->Copied from your email as notes for docker install on a Pi4 class board: To resolve your current problem, you should do the following steps to ensure you're using the correct versions: 1. First, remove any docker packages coming from the Debian or Docker repo: sudo apt remove docker.io docker-buildx docker-buildx-plugin docker-compose 2. Then, fix any broken packages and dependencies sudo apt -f install 3. Remove unused packages sudo apt autoremove 4. Then run the Trixie version of the command. This works on Trixie, but not Bookworm. sudo apt update && sudo apt install -y curl libffi-dev libssl-dev python3-dev python3 python3-pip && curl -fsSL https://get.docker.com -o get-docker.sh && sudo sh get-docker.sh && sudo rm get-docker.sh && sudo apt install -y docker-compose-plugin && sudo systemctl enable docker && sudo usermod -aG docker $(whoami) && sudo mkdir -p $HOME/docker-data Let me know if that helped and if you would like to test the installation process further.

-->Docker install per above and all steps up to Installation of Homeassistant-supervised worked with expected results in all cases. -->Until this step, output pasted below from terminal window... ***@***.***:~# apt install ./homeassistant-supervised.deb -y Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'homeassistant-supervised' instead of './homeassistant-supervised.deb' The following packages will be upgraded: homeassistant-supervised 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/7,492 B of archives. After this operation, 0 B of additional disk space will be used. Get:1 /root/homeassistant-supervised.deb homeassistant-supervised all 3.1.0 [7,492 B] apt-listchanges: Reading changelogs... Preconfiguring packages ... (Reading database ... 239255 files and directories currently installed.) Preparing to unpack .../homeassistant-supervised.deb ... [warn] [warn] If you want more control over your own system, run [warn] Home Assistant as a VM or run Home Assistant Core [warn] via a Docker container. [warn] [warn] ModemManager service is enabled. This might cause issue when using serial devices. [info] Stopping hassio_supervisor service [info] Stopping hassio_apparmor service [info] Removing existing hassio_supervisor container Leaving 'diversion of /etc/NetworkManager/NetworkManager.conf to /etc/NetworkManager/NetworkManager.conf.real by homeassistant-supervised' Leaving 'diversion of /etc/NetworkManager/system-connections/default to /etc/NetworkManager/system-connections/default.real by homeassistant -supervised' Leaving 'diversion of /etc/docker/daemon.json to /etc/docker/daemon.json.real by homeassistant-supervised' Leaving 'diversion of /etc/network/interfaces to /etc/network/interfaces.real by homeassistant-supervised' Leaving 'diversion of /etc/systemd/resolved.conf to /etc/systemd/resolved.conf.real by homeassistant-supervised' Unpacking homeassistant-supervised (3.1.0) over (1.8.0) ... Setting up homeassistant-supervised (3.1.0) ... [info] Reload systemd [info] Restarting NetworkManager [info] Enable systemd-resolved [info] Restarting systemd-resolved [info] Start nfs-utils.service [info] Restarting docker service [info] Install supervisor startup scripts [info] Install AppArmor scripts [info] Start Home Assistant Supervised [info] Installing the 'ha' cli [info] Switching to cgroup v2 [info] Within a few minutes you will be able to reach Home Assistant at: [info] http://homeassistant.local:8123 or using the IP address of your [info] machine: http://192.168.1.220:8123 [warn] A reboot is required to apply changes to grub. N: Download is performed unsandboxed as root as file '/root/homeassistant-supervised.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) ***@***.***:~#

-->Scroll all the way to the right to see error "pkgAcquire::Run (13: Permission denied)" -->As I recall from my previous attempt, if I repeat the install the error gets specific bitching about Trixie. --> So it goes. Leaving the SD card in this state in case you have any ideas. I also researched the env command to if there is a way to fool a script to thinking it was on a different OS. Didn't find anything. Again, so it goes. SK!

On Nov 15, 2025, at 10:15, Tim Matheis ***@***.***> wrote: HuckleberryLovesYou left a comment (HuckleberryLovesYou/Homeassistant-Supervised-on-Raspberry-Pi-5#35) <#35 (comment)> Hi Steven Kutoroff, thanks for reaching out to me and for your kind words! Referring to the issue you're experiencing: Don't know if using Trixie is the cause, but assume it is. Reporting this as an FYI as Trixie is here. You are correct. Using Trixie caused the problem. Thanks for reporting it. The problem is caused by Debian 13 shipping its own docker stack. Basically, it was trying to install docker compose twice, which correctly resulted in an error. The new Debian-managed docker stack isn't officially supported by Homeassistant, but replaced the name for the docker compose package supplied by the docker version. The docker version is now called docker-compose-plugin. Would it be possible for you to test the installation process further? If the rest works fine, I'm going to add the new dependency installation to the README and make Debian Trixie supported by my instructions. To resolve your current problem, you should do the following steps to ensure you're using the correct versions: First, remove any docker packages coming from the Debian or Docker repo: sudo apt remove docker.io docker-buildx docker-buildx-plugin docker-compose Then, fix any broken packages and dependencies sudo apt -f install Remove unused packages sudo apt autoremove Then run the Trixie version of the command. This works on Trixie, but not Bookworm. sudo apt update && sudo apt install -y curl libffi-dev libssl-dev python3-dev python3 python3-pip && curl -fsSL https://get.docker.com -o get-docker.sh && sudo sh get-docker.sh && sudo rm get-docker.sh && sudo apt install -y docker-compose-plugin && sudo systemctl enable docker && sudo usermod -aG docker $(whoami) && sudo mkdir -p $HOME/docker-data Let me know if that helped and if you would like to test the installation process further. Best regards, Tim Matheis — Reply to this email directly, view it on GitHub <#35 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB3PQBWMUU2LFXIBOVJEGTL3447QVAVCNFSM6AAAAACLPM6QYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMZWGU4DANZYHA>. You are receiving this because you authored the thread.

[HuckleberryLovesYou]

Hi SK,

thanks for your fast reply!
You did an amazing job!

N: Download is performed unsandboxed as root as file '/root/homeassistant-supervised.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)

Actually, that is not an error. It's just a notice (specified by the N: at the beginning). This notice just means the _apt user can't access files in your home. You can fix this (if you even need to) by looking at this answer. This doesn't affect the installation and everything installed successfully.

I actually also fell for this to be an error before, since the error (13: Permission denied) is quite common if you're trying to update/install something as a normal user without sudo.

With the output above this notice, it shows that Homeassistant is installed successfully and is running at http://192.168.1.220:8123/. Did you try to connect to it after waiting a few minutes? You may also reboot and try again afterward. This looks like everything is working.

I also researched the env command to if there is a way to fool a script to thinking it was on a different OS. Didn't find anything.

Faking the OS might not be a good solution, since any other program would also think it's a different version of Debian. If there is just a small check for the OS in place, it might work to clone the source, make the changes, and then compile it yourself.

Let me know if it works!

Best regards,

Tim Matheis

[HuckleberryLovesYou]

If there is just a small check for the OS in place, it might work to clone the source, make the changes, and then compile it yourself.

I just checked and found the check in the source. It's actually just a single character change. However, you would have to bundle it afterward to install it. Then I looked into the forks of the repo and found this repo, in which the maintainer made this change and let the CI/CD build the deb for him.
However, the commit the maintainer did, isn't really clean.

To install his version, just download the deb bundle and run it as you already did with the official one.

[skutoroff]

Tim, To my observations, it looks like your alternate DEB file was built to depend on docker as installed for bookworm. When we try to install on Trixie, it fails because the the docker dependencies are different. One Trixie difference was fixed, but the docker dependency on bookworm’s docker remains. Pasted below is my latest docker.txt file with more trials and text. Same result. Hope my annotations make sense. Still have the SD as I left it. I’ve done all I’m going to do for today. I might as well be back at work. I’ve been retired for 8 years. Didn’t feel like that today. SK!

…

-->Copied from your email as notes for docker install on a Pi4 class board: To resolve your current problem, you should do the following steps to ensure you're using the correct versions: 1. First, remove any docker packages coming from the Debian or Docker repo: sudo apt remove docker.io docker-buildx docker-buildx-plugin docker-compose 2. Then, fix any broken packages and dependencies sudo apt -f install 3. Remove unused packages sudo apt autoremove 4. Then run the Trixie version of the command. This works on Trixie, but not Bookworm. sudo apt update && sudo apt install -y curl libffi-dev libssl-dev python3-dev python3 python3-pip && curl -fsSL https://get.docker.com -o get-docker.sh && sudo sh get-docker.sh && sudo rm get-docker.sh && sudo apt install -y docker-compose-plugin && sudo systemctl enable docker && sudo usermod -aG docker $(whoami) && sudo mkdir -p $HOME/docker-data Let me know if that helped and if you would like to test the installation process further.

-->Docker install per above and all steps up to Installation of Homeassistant-supervised worked with expected results in all cases. -->Until this step, output pasted below from terminal window... ***@***.***:~# apt install ./homeassistant-supervised.deb -y Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'homeassistant-supervised' instead of './homeassistant-supervised.deb' The following packages will be upgraded: homeassistant-supervised 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/7,492 B of archives. After this operation, 0 B of additional disk space will be used. Get:1 /root/homeassistant-supervised.deb homeassistant-supervised all 3.1.0 [7,492 B] apt-listchanges: Reading changelogs... Preconfiguring packages ... (Reading database ... 239255 files and directories currently installed.) Preparing to unpack .../homeassistant-supervised.deb ... [warn] [warn] If you want more control over your own system, run [warn] Home Assistant as a VM or run Home Assistant Core [warn] via a Docker container. [warn] [warn] ModemManager service is enabled. This might cause issue when using serial devices. [info] Stopping hassio_supervisor service [info] Stopping hassio_apparmor service [info] Removing existing hassio_supervisor container Leaving 'diversion of /etc/NetworkManager/NetworkManager.conf to /etc/NetworkManager/NetworkManager.conf.real by homeassistant-supervised' Leaving 'diversion of /etc/NetworkManager/system-connections/default to /etc/NetworkManager/system-connections/default.real by homeassistant -supervised' Leaving 'diversion of /etc/docker/daemon.json to /etc/docker/daemon.json.real by homeassistant-supervised' Leaving 'diversion of /etc/network/interfaces to /etc/network/interfaces.real by homeassistant-supervised' Leaving 'diversion of /etc/systemd/resolved.conf to /etc/systemd/resolved.conf.real by homeassistant-supervised' Unpacking homeassistant-supervised (3.1.0) over (1.8.0) ... Setting up homeassistant-supervised (3.1.0) ... [info] Reload systemd [info] Restarting NetworkManager [info] Enable systemd-resolved [info] Restarting systemd-resolved [info] Start nfs-utils.service [info] Restarting docker service [info] Install supervisor startup scripts [info] Install AppArmor scripts [info] Start Home Assistant Supervised [info] Installing the 'ha' cli [info] Switching to cgroup v2 [info] Within a few minutes you will be able to reach Home Assistant at: [info] http://homeassistant.local:8123 or using the IP address of your [info] machine: http://192.168.1.220:8123 [warn] A reboot is required to apply changes to grub. N: Download is performed unsandboxed as root as file '/root/homeassistant-supervised.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) ***@***.***:~#

-->Scroll all the way to the right to see error "pkgAcquire::Run (13: Permission denied)" -->As I recall from my previous attempt, if I repeat the install the error gets specific bitching about Trixie. --> So it goes. Leaving the SD card in this state in case you have any ideas. ... ... ... --> Continued after email reply from Tim. --> 1. Did not test to see if HASSIO was running before shutting the Pi down. --> 2. Did reboot the Pi, no response on port 8123. --> 3. Did variations of "ps -ax | grep has" to look for hassio-supervisor.service or hassio-apparmor.service --> 4. None were running, but so many other processes related to HA were running properly. --> 5. Looking at your email again, http://192.168.1.220:8123/ is the HA instance running on Bookworm. Testing is on 192.168.1.230. Fooled you. --> 6. How did this install script even find that? --> 7. So, the install did not succeed as evidenced.

--> Next Step from the email... --> Ref: https://askubuntu.com/a/908825 --> Going to try: sudo chown -Rv _apt:root /var/cache/apt/archives/partial/ sudo chmod -Rv 700 /var/cache/apt/archives/partial/ sudo chown -R _apt:root /var/lib/apt/lists --> and then try the install script again.

--> (sending this file to the Pi under test to continue to append results.) --> On the target Pi, after "sudo su -", not in same folder as before. --> Had to resume at the same step, repeating previous installs at some risk... --> Repeated: "Update all Packages on your Device" -- Success --> Repeated: "Download os-agent" -- Success --> Repeated: Install os-agent -- Success --> Back in folder with the file: os-agent_linux_aarch64.deb --> Trying: sudo chown -Rv _apt:root /var/cache/apt/archives/partial/ --> ownership of '/var/cache/apt/archives/partial/' retained as _apt:root --> Trying: sudo chmod -Rv 700 /var/cache/apt/archives/partial/ --> mode of '/var/cache/apt/archives/partial/' retained as 0700 (rwx------) --> Trying: sudo chown -R _apt:root /var/lib/apt/lists --> Okay --> Trying the install of Homeassistant-supervised one more time. --> Got: ***@***.***:~# apt install ./homeassistant-supervised.deb -y Note, selecting 'homeassistant-supervised' instead of './homeassistant-supervised.deb' Solving dependencies... Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: Unsatisfied dependencies: homeassistant-supervised : PreDepends: docker-ce but it is not installable Error: Unable to correct problems, you have held broken packages. Error: The following information from --solver 3.0 may provide additional context: Unable to satisfy dependencies. Reached two conflicting decisions: 1. homeassistant-supervised:arm64=3.1.0 is selected for install 2. homeassistant-supervised:arm64 PreDepends docker-ce but none of the choices are installable: [no choices] ***@***.***:~#

--> Now back to other Tim email with alternate source for: homeassistant-supervised.deb --> Download to Mac, send to 220, then to 230 --> Install it. Same messages: ***@***.***:~# ls -l total 2992 -rw-r--r-- 1 pi pi 7484 Nov 16 13:02 homeassistant-supervised.deb -rw-r--r-- 1 root root 7492 May 24 18:18 homeassistant-supervised.debOfficial -rw-r--r-- 1 root root 3043626 Mar 5 2025 os-agent_linux_aarch64.deb ***@***.***:~# apt install ./homeassistant-supervised.deb -y Note, selecting 'homeassistant-supervised' instead of './homeassistant-supervised.deb' Solving dependencies... Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: Unsatisfied dependencies: homeassistant-supervised : PreDepends: docker-ce but it is not installable Error: Unable to correct problems, you have held broken packages. Error: The following information from --solver 3.0 may provide additional context: Unable to satisfy dependencies. Reached two conflicting decisions: 1. homeassistant-supervised:arm64=3.1.1 is selected for install 2. homeassistant-supervised:arm64 PreDepends docker-ce but none of the choices are installable: [no choices] ***@***.***:~#

--> End of test --> Fail.

On Nov 16, 2025, at 10:45, Tim Matheis ***@***.***> wrote: HuckleberryLovesYou left a comment (HuckleberryLovesYou/Homeassistant-Supervised-on-Raspberry-Pi-5#35) <#35 (comment)> If there is just a small check for the OS in place, it might work to clone the source, make the changes, and then compile it yourself. I just checked and found the check in the source. It's actually just a single character change. However, you would have to bundle it afterward to install it. Then I looked into the forks of the repo and found this repo <https://github.com/fliphess/supervised-installer-trixie>, in which the maintainer made this change and let the CI/CD build the deb <https://github.com/fliphess/supervised-installer-trixie/releases/download/3.1.1/homeassistant-supervised.deb> for him. However, the commit the maintainer did, isn't really clean. To install his version, just download the deb <https://github.com/fliphess/supervised-installer-trixie/releases/download/3.1.1/homeassistant-supervised.deb> bundle and run it as you already did with the official one. — Reply to this email directly, view it on GitHub <#35 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB3PQBVWHWR6WXLPRKTTNED35CL2TAVCNFSM6AAAAACLPM6QYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMZYHA4DONBRGI>. You are receiving this because you authored the thread.

[skutoroff]

Summary of where the attempt to install Home Assistant Supervised on Trixie for Raspberry Pi failed.
Final step which should have resulted in HA running.

~# apt install ./homeassistant-supervised.deb -y

Resulted in:

Error: The following information from --solver 3.0 may provide additional context:
Unable to satisfy dependencies. Reached two conflicting decisions:

1. homeassistant-supervised:arm64=3.1.0 is selected for install
2. homeassistant-supervised:arm64 PreDepends docker-ce
   but none of the choices are installable:
   [no choices]

A search with Google in AI Mode (Gemini) for "debian linux edit package dependencies" gave me (trimmed a bit):

Modifying the dependencies of a Debian package typically involves manipulating the .deb package file or its source.
This process requires caution, as incorrect modifications can lead to system instability or broken packages.
To modify the dependencies of an existing .deb package:

Extract the .deb package.

`dpkg-deb -x your-package-name.deb temp_directory`

Extract the control archive.

`dpkg-deb --control your-package-name.deb temp_directory/DEBIAN`

Edit the control file: Open temp_directory/DEBIAN/control using a text editor.
Locate the Depends: line and modify the listed dependencies as needed.

Repackage the control archive:

`dpkg-deb --build temp_directory your-modified-package.deb`

---

1. I've no idea what the control file will look like, other than being text.
2. I'd want to remove docker-ce dependency.
3. Worst case is I still don't have HA Supervised working on Trixie, where I am now anyway.

I don't think I have much to lose by trying this on my Trixie install of Home Assistant Supervised.
I have the DEB file and can make a backup.
If the modified DEB file doesn't I will have lost nothing for trying.

Any comments before I delve into this?

Cheers!
SK!

[skutoroff]

Me again.
Fixed the docker-ce pre-dependency.
Re-installed docker per https://linuxiac.com/how-to-install-docker-on-debian-13-trixie/
Re-installed homeassistant-supervised with the docker-ce issue removed.
Home Assistant now runs on Trixie.
It is in the Preparing Home Assistant phase.