I just set this up so hopefully this solves my docker issues. Thank you!
Now just to figure out why my board is randomly restarting.
Posts by jkindred
-
-
Temporary solution:
Go to OMV-Extras tab. Click Docker tab and then restart. Now Portainer and all other containers should be working. Will have to do this manually after restart though until fixed.
-
Recently updated and now seeing random reboots and portainer and other containers are not starting at boot. Docker shows running under omv-extras but not portainer. Not sure what is causing the random reboots.
System changes made before issues started:
Followed the instructions to fix not mounting hard drives
https://github.com/openmediava…42#issuecomment-723968263
followed by a system update > upgrade > dist-upgrade
Any guidance would be appreciated as to what logs to start looking into.
Setup:
Rock64 board with Armbian 20.08.17 Buster & Linux 5.8.17-rockchip64.
4 external hard drives connected via USB3.0 hub.
-
Not sure if related or not but now I'm seeing random restarts. Occasionally on restart my docker containers are not starting up on their own but Docker shows running.
What steps do I need to take / logs do I need to look over to pinpoint the issue?
-
The following link fixed my issue. Updating to 5.5.16 did not fix the issue by itself.
-
Looks like I got the same issues on my hc1. See: RE: After Update Disks Not Mounting Properly
Ehm can someone explain what steps are exactly needed to fix it? I cannot find my devices under /by-Id/
Yes I am also looking for a solution to this. Spent so many hours adding back my drives to fstab manually.
-
Rather confused what to do here. Spent about 4 hours going through articles online and this forum but can't figure it out.
I did update & upgrade & dist-upgrade. After rebooting 2 out of my 4 drives were not connecting on boot. OMV5 was showing these drives as "missing".
I've checked /etc/fstab and it appears to be configured properly.
I can manually edit /etc/fstab to get the drives to work temporarily but of course this is reset on reboot.
-
I'm getting the same issue. I installed OMV-Extras via root like instructed. Whenever I install Docker it installs but then my DNS is messed up and I can't ping google.com. I have to uninstall Docker via omv-extras in order to do anything that would require outside connections (like pinging).
QuoteWhat is the output of: /usr/bin/host hub.docker.com
QuoteWhat is the output of:
getent hosts hub.docker.com && echo $?
getent hosts omv-extras.org && echo $?
Again. I uninstall Docker and reboot and then I can ping and use apt update, etc.
Possibly related to the issue. After running OMV-Extras script whenever I toggle any of the options (Backports, Extras Repo, Testing Repo) and click save there is a long wait time and then ends with a communication error.
Running Armbian 20.8.1 Buster on Rock64
Version 5.5.12-1 (Usul)
Kernel Linux 5.8.16-rockchip64
UPDATE: I started poking around on the dashboard and was going to report back how my system was setup as far as network connections go. However, when I checked there were no longer any network connections under the network tab. I manually setup eth0 again and now seems like we are back in business. It appears Docker install via OMV-Extras is killing network connections for some odd reason.
UPDATE: Appears to be stable. Docker and Portainer both running and able to add other containers.
