I hadn’t thought of that, great point!
if you ever do want to remove it, then it is literally as easy as just using itself (Portainer) to delete the Portainer container. It’s the beauty of docker - no need to “uninstall” anything - just delete the individual containers and, poof, it’s gone.
Or you can do it via the command line.
Is this something that only happens when using HassOS?
IOW, does a system update when installed on a Linux Host where docker was installed separately prior to installing HA also update Docker then, too?
Exactly. It’s the same reason why I also chose to install the ssh server and samba directly in Ubuntu as opposed to using the equivalent Home Assistant add-ons. In the event docker containers fail to start, or even if the entire docker infrastructure were to fail, I still have access to the headless system via ssh and samba.
Question based on the install procedures.
My setup is similar, Ubuntu 18.04 in docker etc. I do have portainer in both HA and outside of Ha just if one fails I can use it as a fail safe.
Never thought of samba on the outside of Ha as well.
Just installed it outside of HA and works well. My PC that I use to log into HA is running Ubuntu.
How can I make samba show up automatically in my file manager program when I boot up.
I have tried cfis, fuse and a few other internet tutorials about adding to /etc/fastab, but can not get it working.
Can any one point me in a direction.
mount -t cifs //hamachine/share /nountpount
Yes. A system update will also update docker. Then if you had used say docker-compose and set the container to always run unless stopped it will start up again automatically. The HassOS containers are a PITA in that they seem to not restart unless you reboot.
But won’t update the containers
Correct it won’t. I use a shell script to pull new images and start them but I also use watchtower that always keeps them up-to-date.
That’s good to know.
Install in an Ubuntu image under windows , you can then have a raid , system shots , backups every once in a while , to external disk , flash or whatever , if it dies just restore backup , whatever windows machine will work , wife will be happy !!
I had some serious issues with RPi 3b+ with a lot of hangups. From what I could read from Glances it was related to I/Owait.
Found this definiton of it:
For a given CPU, the I/O wait time is the time during which that CPU was idle (i.e. didn’t execute any tasks) and there was at least one outstanding disk I/O operation requested by a task scheduled on that CPU (at the time it generated that I/O request).
Moved to an RPi 4 and all my issues was gone instantly
So, I have tried everything to get Ubuntu Server on this Lenovo ThinkCentre M72e with no luck. UEFI enabled or disabled, Drive mode set to IDE or AHCI, Fast Boot/QuickBoot enabled/disabled, it all makes no difference. Additionally, switching to Ubuntu Desktop gives the same results. While the Live CD will boot and the install will complete successfully, “No operating system found” is returned upon first boot after installation. GParted shows the boot volume is flagged properly, yet the system apparently is biased against everything but Windows. I really didn’t want to have to lose the drive space and resources Windows will take just to run this as a VM, but that’s looking like what I’m going to need to do.
The problem does not appear to be limited to Ubuntu. Someone tried to instal libreELEC on the M72e and encountered exactly the same problem you did.
Ultimately they had to alter the BIOS in order to correct the problem. It’s a long thread describing the many things that failed to work and culminates in a post where they altered the BIOS. A subsequent post explained that the problem was in the latest BIOS (at the time) and the solution was to simply revert to an older version.
Ok, through trial and error and a BUNCH on help here and a number of DMs from @kanga_who, I’m finally up and running on the ThinkCentre M72e with Ubuntu Desktop 20.04 LTS 64-bit.
Here are the BIOS settings I had to get in just the right combination in order to get this working:
CMS - No entry in BIOS
Boot Mode: Legacy
Boot Priority: Legacy
Boot Order: HDD first, everything else disabled.
Quick Boot: Disabled
Drive Mode: IDE
Drive Native Mode: Disabled
Compared to my old RPi 3B+, this [email protected]/16GB/500GB tiny system SCREAMS! This was a refurbished unit I picked up from Newegg.com for about $120USD. Thinking back it’s actually less than I’ve put into my RPi 3B+ running a 64GB MicroSD card (and other crashed cards), case, case fan, and upgraded power supply. All headaches aside, it was totally worth it to get this thing going.
All I need to do now is get my Z-wave devices paired with my new Z stick and rebuild my all of my old yaml automations in NodeRed and I’ll be all set to pull the plug on the old RPi 3B+! I can’t wait!
I don’t get it. Those are all fairly vanilla BIOS settings. What were they set to when it failed to boot?
Did you have to re-install ubuntu after making those changes?
I did, but after the reinstall it came up properly.
Thank you so much for providing those guides! I had difficulty with 20.04 and spent several hours banging my head against the wall yesterday. Started fresh with your guide and mostly working within an hour. I do have one roadblock and not sure if you or someone else here can help. My particular install is using VirtualBox on windows. I have the network adapter in bridged mode and a private reservation on my router. I can SSH, get to files via SAMBA, verify docker containers are running in Portainer web ui, and get to HomeAssistant.local and completed several initial integrations/devices and can even connect with the mobile app on android.
The issue I have is that in the HomeAssistant.Local web interface clicking on the Supervisor menu item results in the web interface freezing. A chrome trace shows that calls to these three URLs get stuck in pending and never return a result.
http: // homeassistant.local:8123/api/hassio/supervisor/info
http: // homeassistant.local:8123/api/hassio/host/info
http: // homeassistant.local:8123/api/hassio/core/info
I’m not exactly sure where to look for logs and the logs I have seen aren’t showing errors. Docker is showing Supervisor as running and SSH ha cli shows supervisor as on.
I am new to docker, virtualbox, ubuntu, and home assistant and appreciate any pointers. Since Wink is attempting their extortion scheme it’s time to move to something better just need a little assistance bridging the gap.
The suggestions in this thread need revision.