I installed Docker using the convenience script. Now, when I run Aptitude to keep (the rest of) my system up to date, it suggests to remove docker-ce, docker-ce-cli, and containerd.io with the remark “packages being removed because they are no longer used”. I guess this happens since the installed versions have been superseeded by an upgraded version, but the convenience script did install the packages without marking the correct dependencies.
What should I do?
mark the package docker-ce as manualy selected in aptitude (the other two depend on this one) so they are kept
just upgrade, let aptitude remove them, and suppose that they are kept because they were not installed through apt anyway
The 1st option seems most safe.
Update: I did the first, and upgraded all with aptitude, after manually selecting the “docker-ce” package. At first, HASS did fail. But after a reboot, and some patience, everything is working again, and now it’s all running fine.
So maybe, as an additional step in the installation process, after running the ‘convenience script’, one should select docker-ce via apt, apt-get, or aptitude, or whatever package maintenance utility is being used.
But that is for the first install. Then you get the latest version. But upgrading Docker means the host version of Docker, not Docker in a Docker container. And the Docker installation on the host is managed by the host’s package management system, like apt or aptitude. And (at least on my system) aptitude was thinking Docker was no longer needed, when it started checking and noticed the version was outdated.
That is what I’d like to solve.
Hi there! Thanks for writing these instructions. I just followed all the steps and everything looks good except that wifi is not working anymore. I really wanna connect PI to wifi and I understand the risks and that LAN is more stable. During setup wifi was working fine, looks like HA’s installation script has blocked wifi interface or smth. Could anybody help me please?
Actually I was trying to connect via SSH previously with no success via wifi (for LAN it’s working). I connected monitor and keyboard to the board now and tried to ping. Network is unreachable. Attached the output.
I configured manually wifi connection via network manager. Restarted the interface and it got ip address. I didn’t try ssh though. Restarted the board and wifi is gone again. It’s super strange for me…
Indeed, I use Raspbian. And aptitude, which was going to remove Docker. So I marked it manually as ‘keep’. But I did not pin the version, so apt(itude) upgraded the Docker version.
Everything works now, except that HomeAssistant does not start by itself anymore. hassio_observer starts upon reboot, but I have to manually start the homeassistant container (or was it hassio_supervisor?). I try to understand how Docker works, and how the different containers that depend on each other do start each other.
It did work, before upgrading Docker, so I would like to use the original startup mechanism, but I cannot find much documentation about how this convenience scripts sets-up things. On https://www.home-assistant.io/installation/raspberrypi I read about using Docker-compose. Is that also what the convenience script uses?
Your help is very much appreciated.