Lately I've been pulling my hair trying to install and start the Home Assistant container on a RB3011, but no success (described in another thread)

So instead of trying to bury myself even deeper into the problems I think I'll rather raise my head, turn around, and ask you guys:

Those of you that have achieved to get HA up and running under ROS, would you care to share your success stories?

-Type of Routerboard
-ROS version
-Type and size of storage device (MicroSD, USB stick, M.2..)
-Disk formatting (FAT32, EXT4)
-Branch of the Home Assistant (Stable, Latest...)
-Method of extracting the container (online or importing offline tarball)
-Config (would be thankful for code)
-"Do's" and "Don'ts"

Thanks in advance!

Have you tried that? search.php?keywords=home+assistant+container

Have you tried that? search.php?keywords=home+assistant+container

Yes of course I have searched the forum.
And I have followed the guide in the MT Docs.
The problem is that there is almost no error messages or log entries generated enabling me to trace down the error. The extraction just stops, that's it. And in between when it finishes, the container is unable to start. Dead as a stone, no debug output.

If the problem is an invalid setting, too little storage or something else, it would be very useful to know.
But it looks like the concept of containers by design is left to the user to be trial and error, and that puzzles me. There is a reason for everything that fails, but it is hard to guess what it is...

Therefore, if someone could tell me "I used this hardware and that config and it worked" it might lead me in the right direction.
Or, if I'm told that "The RB3011 has never worked for containers" I could stop wasting my time on it.

Did you try using the fully qualified remote-image, i.e. including :latest. This worked to create HA on a RB1100AHx4, which 32-bit too.
And I start it, HA comes up :8123. I don't use HA so cannot say it works beyond the web UI working.

Did you try using the fully qualified remote-image, i.e. including :latest. This worked to create HA on a RB1100AHx4, which 32-bit too.

Code: Select all

# SSD is at "raid1/" and layer-dir= and tmpdir= explicitly use the "real" disk
/container/config set layer-dir=raid1/layers registry-url=https://registry-1.docker.io tmpdir=raid1/tmpdir
# had to use :latest - otherwise does error
/container add remote-image=homeassistant/home-assistant:latest root-dir=raid1/ha-root interface=veth-lanbridge-203 logging=yes    

And I start it, HA comes up :8123. I don't use HA so cannot say it works beyond the web UI working.

MT Support suggested that I Netinstalled the RB to "clean things up"
No way I could get the RB3011 visible in Netinstall, despite “ether boot” in display.. so I moved to an RB5009.
Netinstalled 7.17 on it, installed Container package.
After your tip I changed HA from branch “stable” to “latest”, installed HA container and it worked!

Thank you for your kind assistance!

Did you try using the fully qualified remote-image, i.e. including :latest. This worked to create HA on a RB1100AHx4, which 32-bit too.

Code: Select all

# SSD is at "raid1/" and layer-dir= and tmpdir= explicitly use the "real" disk
/container/config set layer-dir=raid1/layers registry-url=https://registry-1.docker.io tmpdir=raid1/tmpdir
# had to use :latest - otherwise does error
/container add remote-image=homeassistant/home-assistant:latest root-dir=raid1/ha-root interface=veth-lanbridge-203 logging=yes    

And I start it, HA comes up :8123. I don't use HA so cannot say it works beyond the web UI working.

Thank you.