I've had OMV 5.x install for a couple weeks and running smooth, no issues, actually seemed to run smoother even classified as beta. Then plex started not allowing remote access and i couldn't find a solution, so figured to reinstall plex. but then realized that portainer wasn't not pulling images, believe the error was image not found. So I figured to clean install OMV and doing so, I'm getting same type error. From within the omv-extras tab, docker and cockpit will install but not portainer, which gives me the "Something went wrong trying to pull and start portainer" error. Similar thing happened trying to install DockSTARTer, installed all the way to part of installing the individual dockers, then nothing but errors. Any help would be much appreciated, thanks in advance
error every docker pull, including portainer
-
- OMV 5.x
- elvincent
-
-
Is your server online? Sometimes your network will need reconfigured after installing docker (it happened to me once)
SSH your server
ping -c 10 aol.comand see if you get a response. It should try to ping aol.com 10 times and then give you the results. If it says anything but 0% packet loss, then just omv-firstaid (as root) and choose the option to reconfigure your NIC. Note, your IP may change.
-
did the ping and came back with 0% packet loss, still did the reconfigure nic and same issue
-
any other suggestions or going back 4.x
-
ok, how are you trying to install Portainer? with the button in omv-extras?
Is your machine completely up to date? (apt-get update apt-get upgrade)
-
yes I'm trying to install from the button, and getting error message "Something went wrong trying to pull and start portainer". Cockpit installs fine. Yes the system is updated and apt is updated
-
That is weird.
1. Create a "portainer" folder in your appdata folder.
2. Make sure docker-compose is installed (apt install docker-compose)
3. touch docker-compose.yml
4. nano docker-compose.yml
5. Copy/paste the contents of this pastebin into the docker-compose file... https://pastebin.com/XRXzRA01
6. Use the arrow keys to go down to the "APP DATA" section under volumes, and put the entire path to your portainer folder in app data (ie.. /srv/some_uuid/appdata/portainer)
7. Cntrl X, then Y and enter to save.
8. Back at the prompt, type docker-compose up -d
That should install it.
-
no got another error message ... ERROR: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.8.1:53: read udp 192.168.8.100:41278->192.168.8.1:53: i/o timeout
-
I have no idea what that error message means, never saw that one.
Are you running a firewall of some sort that may be blocking docker?
-
not that i know of, was running 5.x fine, had a few dockers running for a couple weeks, then tried to install duckdns through portainer and was getting can't find image. then plex wasn't getting internet connection and couldn't install again. Then reinstalled omv and same thing, dockers won't install. I'll try re-installing again, if same error, probably go back to 4.x. Thanks for assistance
-
not that i know of, was running 5.x fine, had a few dockers running for a couple weeks, then tried to install duckdns through portainer and was getting can't find image. then plex wasn't getting internet connection and couldn't install again. Then reinstalled omv and same thing, dockers won't install. I'll try re-installing again, if same error, probably go back to 4.x. Thanks for assistance
This seems to suggest it might be a DNS issue...
-
i set the dns previously, but for whatever reason it was cleared out, but i set it again and same issue.
-
i set the dns previously, but for whatever reason it was cleared out, but i set it again and same issue.
Well that sounds like it's the problem. -
it had trouble during the mirror stage on the install, until I turned off my vpn which is attached to my router. But I'll try another fresh install and hopefully it'll work
-
Sorry for reviving a dead thread, but I had the same issue after updating from OMV 4 to 5 and it turned out the problem was that I have an existing docker container already using port 8000, which portainer was attempting to use as its agent port by default. Toggled the “advanced” portainer config, set the agent port to 8002, and then I didn’t have any problems installing.
-
I had this issue (re)installing portainer every time there was an update to docker on OMV6. For me, it was a DNS issue, even though terminal displayed "DNS OK." Yes, DNS was ok, but my ad blocker is at the DNS level (nextdns), and the logs showed it was blocking "api.ipify.org." I added it to the allowlist, and portainer installed with no issues.
-
I don't know if someone has this problem still, but in my case the issue was that something else was already running on port 9000.
Which is also the default port for portainer.
Before in stalling portainer set the port to something else (for example 9042) and then install and for me this helped a lot!
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!