The updates are performe container-way: through the image version updates.
So, you have to specify qweritos/haos-one:latest and run docker pull qweritos/haos-one:latest (then re-create container) or specify image qweritos/haos-one:18.2 explicitly.
I thinking on how to add support for auto-updates, but it either require introducing another level of docker supervision (like watchtower/WUD does) OR to completely change the runtime preparation approach (and I don’t like this idea, because it introduces more resources overhead and complexity).
Probably, to those wanting to keep HAOS OS image up-to-date to use Watchtower/WUD/??? to update the container image automatically.
Just as a guy running ha in docker i just want to point out one thing.
There is no reason to run haos in docker. You can run just ha in its own docker container and add everyting else as you please.
Why? Well because you can avoid all haos problems like frigate killing your system due high cpu usage.
Downside is that you will have to put some effort in it, but it is doable.
And everything like auto upgrades and backups of all containers can be set up.
And there is a lot of info out there on how to do it.
It’s a good point, actually. Initially, I made this project long ago to run HAOS in my home k8s cluster. And after Supervised installation method became deprecated, I decided to share the project with a public.
It is primarily intended for those who explicitly want the OS experience, including the Addon Store (Apps) or to migrate existing Supervised installation.
Why? It’s just because I got used to work with some apps right from the HASS
I know that you put your time and effort in doing this. And it is obvoius.
But basically when you run haos in docker container you are running docker containers inside docker container.
And there is no need to do so.
Haos is made for people runing windows to get started with linux aka haos.
But if you are alredy using linux then obvoius migration will be to docker and do it yourself.
That is what i just want to point out.
But basically when you run haos in docker container you are running docker containers inside docker container.
Correct, and the only alternative - to run HAOS in VM, which obviously comes with relatively significant resource overhead. And this project is made to eliminate this drawback while keeping the original “Operating System” flavour.
@famewolf , I added some fixes (fake udev interceptor) that makes it work on LXC (running unpriviliged in proxmox). For both rootfull and rootles.
Verified on:
hello,
I was running haos on an old pc just dedicated to that because on my ugreen dh4300 nas there is no VM to be able to install it and via docker it wasn’t great. so I tried installing haos-one on my nas like this “docker run --name haos -ti --privileged --network host -v./data:/mnt/data qweritos/haos-one” then integrated the latest haos backup from my old pc and it seems to work. it’s been working pretty well for two days, even my sonof matter key works. bravo and thank you for this version
