MacOs + VMWare Fusion + Debian 12 + Home Assistant Supervisor - Can't update Home Assistant access token!

1

Hi I have a fresh install of Home assistant supervisor running on Debian 12 that is installed via VMWare fusion on a Mac OS Ventura. Home assistant is working in general, but the supervisor is not starting. I checked the existing posts with similar issues, but no luck. I feel like it has something to do with my vm ip address starting with 172. vs my host machine ip starting with 192.

Here are the logs:

24-01-19 10:22:36 ERROR (SyncWorker_0) [supervisor.docker.network] Can't link container to hassio-net: 500 Server Error for http+docker://localhost/v1.44/networks/0cab060795c263609f1b1d2f2f2c735b551c372d686a8c9d46a8800251011c51/connect: Internal Server Error ("invalid endpoint settings:
no configured subnet or ip-range contain the IP address 172.30.32.4")
24-01-19 10:22:36 WARNING (SyncWorker_0) [supervisor.docker.manager] Can't attach hassio_audio to hassio-network!
24-01-19 10:22:36 INFO (MainThread) [supervisor.docker.audio] Starting Audio ghcr.io/home-assistant/aarch64-hassio-audio with version 2023.12.0 - 172.30.32.4
24-01-19 10:22:41 ERROR (MainThread) [supervisor.store.git] Can't clone https://github.com/hassio-addons/repository repository: Cmd('git') failed due to: exit code(128)
  cmdline: git clone -v --recursive --depth=1 --shallow-submodules -- https://github.com/hassio-addons/repository /data/addons/git/a0d7b954
  stderr: 'Cloning into '/data/addons/git/a0d7b954'...
fatal: unable to access 'https://github.com/hassio-addons/repository/': Could not resolve host: github.com
'.
24-01-19 10:22:41 ERROR (MainThread) [supervisor.store] Can't retrieve data from https://github.com/hassio-addons/repository due to 
24-01-19 10:29:09 INFO (MainThread) [supervisor.docker.observer] Starting Observer ghcr.io/home-assistant/aarch64-hassio-observer with version 2023.06.0 - 172.30.32.6
24-01-19 10:29:12 ERROR (MainThread) [supervisor.homeassistant.api] Can't update Home Assistant access token!
24-01-19 10:29:32 ERROR (MainThread) [supervisor.homeassistant.api] Can't update Home Assistant access token!
24-01-19 10:29:37 ERROR (MainThread) [supervisor.homeassistant.api] Can't update Home Assistant access token!
24-01-19 10:29:42 ERROR (MainThread) [supervisor.homeassistant.api] Can't update Home Assistant access

Much appreciate your help!

2

I’m facing the exact same issue… for some reason the deployment fails to bind the containers to the hassio docker network… so the containers don’t get the expected fixed ip’s and communication fails…

3

I’m on the same boat after update:

24-01-19 15:42:33 INFO (MainThread) [supervisor.bootstrap] Seting up coresys for machine: qemux86-64
24-01-19 15:42:33 INFO (SyncWorker_0) [supervisor.docker.supervisor] Attaching to Supervisor homeassistant/amd64-hassio-supervisor with version 2023.06.dev2301
24-01-19 15:42:33 INFO (SyncWorker_0) [supervisor.docker.supervisor] Connecting Supervisor to hassio-network
24-01-19 15:42:33 ERROR (SyncWorker_0) [supervisor.docker.network] Can't link container to hassio-net: 500 Server Error for http+docker://localhost/v1.44/networks/1db3d3c73b977f6cc7b416c58d8b1fee3560b5d4cf2a4294f64e8feea28007ef/connect: Internal Server Error ("invalid endpoint settings:
no configured subnet or ip-range contain the IP address 172.30.32.2")
24-01-19 15:42:33 CRITICAL (MainThread) [supervisor.supervisor] Can't setup Supervisor Docker container!
24-01-19 15:42:33 WARNING (SyncWorker_1) [supervisor.docker.interface] Can't find homeassistant/amd64-hassio-supervisor for cleanup
24-01-19 15:42:33 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.INITIALIZE
24-01-19 15:42:33 WARNING (MainThread) [supervisor.resolution.evaluations.base] Found unsupported job conditions settings. (more-info: https://www.home-assistant.io/more-info/unsupported/job_conditions)
24-01-19 15:42:33 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
24-01-19 15:42:33 ERROR (MainThread) [supervisor.core] Update '2023.12.1' of Supervisor '2023.06.dev2301' failed!
24-01-19 15:42:33 INFO (MainThread) [supervisor.resolution.module] Create new issue IssueType.UPDATE_ROLLBACK - ContextType.SUPERVISOR / None
24-01-19 15:42:33 INFO (MainThread) [__main__] Setting up Supervisor
24-01-19 15:42:33 INFO (MainThread) [supervisor.api] Starting API on 172.30.32.2
24-01-19 15:42:34 CRITICAL (MainThread) [supervisor.hardware.monitor] Not privileged to run udev monitor!
4

I was able to trace this back to a system update on Debian 10, and there rolling-back docker-ce and pinning the downgraded version like following solved the issue:

prompt: sudo apt install -y --allow-downgrades docker-ce=5:24.0.7-1~debian.10~buster
prompt: sudo apt-mark hold docker-ce

The problematic release is version 5:25.0.0 (the output [installed] resulted prior to the roll-back):

prompt: sudo apt list -a docker-ce 2>/dev/null | grep -E '^docker' | head -n 2
docker-ce/buster,now 5:25.0.0-1~debian.10~buster amd64 [installed]
docker-ce/buster 5:24.0.7-1~debian.10~buster amd64
8 Likes
5

Thank you, the rolling-back was the solution for me as well on Debian 12.
My docker version was “25.0.0-1~debian.12~bookworm”, and reverted back to the earlier one: “24.0.7-1~debian.12~bookworm”. I changed it in your command and it worked well - thankfully.

3 Likes
6

When I run the following command:

sudo apt install -y --allow-downgrades docker-ce=24.0.7-1~debian.12~bookworm”

I get this error:

E: Version '24.0.7-1~debian.12~bookworm”' for 'docker-ce' was not found

:frowning:

7

Hero, this fixed it for me.

In case someone faces the same issue, I had to list the versions for docker with the command:

apt list docker-ce -a

then replace the wanted version in cjxo’s command.

1 Like
8

Awesome! Works for me too! Thanks all!

9

absolutely wonrderful. My supervisor and other are finally starting!

thank you so much!

10

Same problem here, half of my containers running on Portainer were not able to start. I even lost a couple of them, luckily volumes with their states are still there.

I followed your downgrade suggestion and everything is back online now. I guess that should be reported to the Debian upstream.

11

Thank you, worked for me as well!

12

Just came here to say thank you! 24h wasted fixing a working HA instance :frowning:

This is the command I got after looking the version installed with what @kriodoxis said

image
image761Ă—24 1.39 KB

Uploading and restoring backup from the 19th just to see if I’m lucky enough to not having to pair all my zigbees again.

Thank you very much to you all!!

2 Likes
13

perfect, ty and thank everyone. talk about a sweating a little…

to make it easier for those on bookworm…

sudo apt install -y --allow-downgrades docker-ce=5:24.0.7-1~debian.12~bookworm

then…

sudo apt-mark hold docker-ce *this will hold docker-ce at the current version, after there is a fix (hopefully a fix) you would use

sudo apt-mark unhold docker-ce to remove the hold.

5 Likes
14

Thanks a lot! It was the solution for me after a few hours of trying to fix configuration

15

Did anyone reported this somewhere on GitHub? To have a bug tracking…

In my case it also solved the issue by downgrading the docker. Thank you very much.

16

Thank you very much. I shot down my instance yesterday and spent hours looking for a solution. You guys made my day!

17

Same issue here, thank you so much!

18

Same here in Australia, spent hours then found this, saved many more hours, thank-you greatly.

19

A very big thank you to you all. It saved me a lot of pain!

I am running docker/portainer on Ubuntu 22.04.3 LTS.

This is, how I downgraded:

apt list docker-ce -a

from there, I took the latest version and created the following command:

sudo apt install -y --allow-downgrades docker-ce=5:24.0.7-1~ubuntu.22.04~jammy
1 Like
20

Could you please explain, what this command is doing? I assume, it is preventing future updates on docker? Do I need this command? I am updating once a month and I hope, it will be fixed in a future version. :slight_smile: