Portainer/Docker issues

AustinML · 21. Februar 2020

I've been running OMV5 for a few weeks now and had almost everything I wanted running in docker (sabnzbd, radarr, sonarr, jellyfin, etc.) through Portainer. One last thing I was trying to get working was a bittorrent client running through a vpn. I tried several different options but was never able to get one working. I was trying again tonight and again failed but something seeming horrible happened - in deleting the images from my failed attempts, I somehow have broken Portainer. I've rebooted my server but portainer does not load. I tried to install from OMV-extras again but it errors out. And worse, none of my containers seem to be running. There is nothing in the logs for the past 30 min or so. When I do try to install Portainer again I get this message:
Docker storage :: /srv/dev-disk-by-label-work/docker/
Opt-out :: 1
arch :: amd64
option :: portainer
state :: install
extras :: 5.2.4
DNS OK.
No portainer containers or images to remove.
Pulling and starting portainer ...
Something went wrong trying to pull and start portainer ...
Done.

when I look in my docker and container config folders it looks like everything is there but none of it is running. I'm hoping this is an easy thing to fix?

Please let me know if there is any further information I can provide and thank you in advance for your help!

KM0201 · 21. Februar 2020

All you really need to do is reinstall Portainer from the sounds of it. This won't hurt anything, the new install will pick up your current docker containers (assuming you didn't do something to them as well). As long as you haven't customized ports, etc. for Portainer, just log into the OMV webUI, click on omv-extras and then the docker tab. Click the Portainer button and click "remove Portainer".. when it's done, click it again, and click Install Portainer (you might be able to just click Install from the beginning, but I'm not sure if it will error out if Portainer is currently running, but just not accessible). Then just go back to Portainer and create your username/password again, and all will be good.

When you go to the Portainer URL.. you might have a browser cache issue... most browsers just hold Cntrl and click Refresh to resolve this... then log in.

Huberer · 21. Februar 2020

Do you use the proxmox-kernel? If yes, portainer is not working under this kernel. I’ve installed on three different machines the proxmox kernel and couldn‘t get portainer to run. On the standard Debian kernel everything runs fine.

Gesendet von iPhone mit Tapatalk

AustinML · 21. Februar 2020

I'm still not sure exactly what happened but what ended up fixing it was either restarting or hitting Install again on Docker in OMV-Extras. Still not sure what I did to Docker to have whatever the issue was persist through a reboot. Oh well. I appreciate the help and am VERY glad all my containers weren't gone.

Thanks!

Huberer · 21. Februar 2020

But just to know. Which kernel do you use?

Gesendet von iPhone mit Tapatalk

AustinML · 21. Februar 2020

I'm not really sure - whatever installs standard with OMV5 I guess?

gderf · 21. Februar 2020

Zitat von AustinML

I'm not really sure - whatever installs standard with OMV5 I guess?

In the shell run:

uname -a

Or login to the WebUI and read the System Information screen.

AustinML · 21. Februar 2020

Linux 5.4.0-0.bpo.3-amd64

Huberer · 21. Februar 2020

Thanks. It looks that you're using the proxmox kernel.
I really don't understand why is portainer working on some users with proxmox kernel and on three systems of mine (2 real machines and one VM) not. Really, really curious .....

gderf · 21. Februar 2020

Zitat von Huberer

Thanks. It looks that you're using the proxmox kernel.
I really don't understand why is portainer working on some users with proxmox kernel and on three systems of mine (2 real machines and one VM) not. Really, really curious .....

I thought the proxmox kernels had pve in their names?

I'm running 5.4.0-0.bpo.3-amd64 too and Portainer works fine.

Huberer · 21. Februar 2020

Zitat von gderf

I'm running 5.4.0-0.bpo.3-amd64 too and Portainer works fine.

Is this the proxmox kernel or did you install the kernel by hand?

trythat · 21. Februar 2020

Regarding bittorrent-vpn I use binhex/arch-delugevpn works really well, I'm well please with it, easy to setup and get running. My VPN of choice is Windscribe, I think it comes with default setup for PIA if I remember though.

I did set it up under portainer, but now I now how to use the stacks option using docker-compose thats even easier, I really like the stacks option, Portainer just needs to update it to use the newer version of compose to make it perfect.

gderf · 21. Februar 2020

Zitat von Huberer

Is this the proxmox kernel or did you install the kernel by hand?

This is a backports kernel (bpo). They were made available if the backports repo was enabled on OMV4, but IIRC, more recently they are used as the default. I'm on OMV5.

Huberer · 21. Februar 2020

Zitat von gderf

This is a backports kernel (bpo). They were made available if the backports repo was enabled on OMV4, but IIRC, more recently they are used as the default. I'm on OMV5.

Thanks for the info. So the last hour I did a fresh installation and it looks like that I've overseen the backport option under OMV v5. I've enabled it and now I run the backport kernel v5.4. And, can you imagine, portainer runs fine. So, there's is something with the proxmox kernel which hinders the installation of portainer.
So the problem is solved for me. Thanks again

Soliver84 · 26. November 2020

Has anyone reported the error that it will be fixed?

I have the error.

Because: Proxmox for ZFS.

Portainer and yacht don't work! I don't let the pages open!

LOG PROXMOX install:

Supported kernel found

Get:1 file:/var/cache/openmediavault/archives InRelease

Ign:1 file:/var/cache/openmediavault/archives InRelease

Get:2 file:/var/cache/openmediavault/archives Release

Ign:2 file:/var/cache/openmediavault/archives Release