core: The operating system does not support network storage Network storage is not supported on this host

OK I got it working now. Need to use slave bind propagation, others wont work!

2 weeks ago there was a patch to the supervisor installer for setting bind propagation of the data mount to slave. Usually re-running the supervisor should do the trick, but for me it did not. I was able to set it manually using the following steps:

SOLUTION

1. Edit /usr/sbin/hassio-supervisor file changing the following line -v ${SUPERVISOR_DATA}:/data:rw \ to -v ${SUPERVISOR_DATA}:/data:rw,slave \
2. Remove the docker container (it should get recreated by systemd automatically with the script you just edited) docker container rm -f hassio_supervisor
3. In case it was not recreated (check docker ps) just run the script manually

Here is a link to the commit with the patch: https://github.com/home-assistant/supervised-installer/pull/293/commits/c49720f3ba4a5fac5781625398c9b14e4556c737

Enjoy 😉

Amazing what can be done with a closed ticket where the team says there isn’t an issue…

I’m having the exact same problem, this is obviously a bug in supervised installs (Debian and everything supported). Last time I checked supervised installation method is still supported and any questions from users should not just be thrown out of the window. Also, if something more should be done by the user before/after updating to 2023.6, I think this should be in the release notes, even for advanced users like those who have supervised installs.

I’m no expert on Linux

Don’t get me wrong, but in that case you are not the target users for the Home Assistant Supervised installation and I would strongly suggest running Home Assistant in a different way that suits you more.

😂😂 having been in this industry for over 20 years, with a very wide & deep technology background, that comment made me LOL - As someone that’s also managed product development commercially and understands customers very well, I was trying to offer you some product advice to actually help your users with a new feature.

Closing bugs like this is one of my pet hates (professionally)… anyway, this feature was more of a ‘nice to have’ for me so I will just ignore it and not spend any more time on it.

I’m having the exact same problem, this is obviously a bug in supervised installs (Debian and everything supported). Last time I checked supervised installation method is still supported and any questions from users should not just be thrown out of the window. Also, if something more should be done by the user before/after updating to 2023.6, I think this should be in the release notes, even for advanced users like those who have supervised installs.

Yes, supervised installer, specifically the /usr/sbin/hassio-supervisor script does setup the docker container with bind propagation rprivate for data directory. Otherwise it seems that changing that does not change anything as mentioned earlier. I wouldnt say that it is definitely a problem with the installer, but it would be great to know what else needs to be done here.

So this actually points to a bug in the new feature in relation to supervised installs (possibly to docker installs too). If changing the bind propagation options as suggested does not resolve the issue, the issue is with the new feature and developers could take a look at that.

I’m no expert on Linux

Don’t get me wrong, but in that case you are not the target users for the Home Assistant Supervised installation and I would strongly suggest running Home Assistant in a different way that suits you more. Home Assistant Supervised is the most complicated installation method we have, and requires (and we assume) deep knowledge of Linux system administrator, networking and things like Docker. (<- that is documented and warned for).

and elaborate on possible fixes?

I did in the previous message? Have you tried running the Supervised installer again? Like with the latest available version?

Home Assistant Supervised

It means you probably haven’t set bind propagation for the Supervisor data folder. You can either add that, or otherwise try running the Supervised installer again.

Closing this issue, as it is a configuration issue on the host system we don’t control.

…/Frenck

worked for me also… did a backup first, then applied the “slave” to the script, ran the script (noticed the prompt didn’t return)… but did see the container recreated, so issued a reboot to ensure everything came up clean.

Yeah Breaking stuff and then claiming nothing can be done because we’re not using their OS bundle is facilitated by simply closing a ticket.

I have a HA supervised installation on Debian 11 followed the install on the HA docs. Same issue “The operating system does not support network storage Network storage is not supported on this host”

Re-run Home Assistant Supervised Debian Package: wget https://github.com/home-assistant/supervised-installer/releases/latest/download/homeassistant-supervised.deb dpkg -i homeassistant-supervised.deb

For the record the latest supervised installer (1.5.0) depends on the package systemd-resolved which does not exist on Debian 11 Bullseye so you might want to use one of the following solutions:

• Re-run 1.4.3 installer instead of 1.5.0 (which also includes the bind propagation fix)
• or install the backport of systemd-resolved and run 1.5.0 installer (that’s what I did)
• or upgrade to Debian 12 Bookworm and run 1.5.0 installer ?

I followed all 3 steps from @freeDom but docker did not come back up. So reset and then followed the first 1 step

"Edit /usr/sbin/hassio-supervisor file changing the following line
        -v ${SUPERVISOR_DATA}:/data:rw \
to
        -v ${SUPERVISOR_DATA}:/data:rw,slave \

Then rebooted the system and all was well.

So many thanks for all your help. 😃