I broke portainer

do and apt-clean ( in omvextras webGUI) and try again.

Zitat von perkunas

Nope same thing it wont install

I had the same problem. Ended up with re-installation of OMV5. It took couple of hours to reconfigure and update but Portainer is back.

Note: Do NOT reformat OMV drive, just re-install.

Zitat von perkunas

wow so OMV is broken?

Well, no. What is broken is Portainer. I did not have any other solution for fixing Portainer so ended up re-installing the whole thing. Good thing was that, MariaDB database (I use it for 5 installations of Kodi) did not get lost so I did not have to rebuild that. Just pain in the neck.

Zitat von perkunas

I hope someone else comes up with better then that

I hope so too, because this is not the last time Portainer will get broken and re-installing and configuring OMV is just pain in the neck.

Zitat von perkunas

what if i did it command line

Code

sudo docker pull portainer/portainer-ce
sudo docker run --restart=always --name=portainer -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer-ce

I think I tried this but did not worked for me. Might work for you, dough.

Zitat von KM0201

I'm sorry, that is the most ridiculous advice I've seen on this forum . The error clearly states there is a DNS issue.

OP... post the output of

Code

ping -c 5 aol.com

Most likely it's going to tell you something about the host could not be reached because while your network device is working (so you can use SSH, the webUI, etc..) it cannot access the Internet, so you can't get updates, the new container, etc..

At that point, as root run the command:

Code

omv-firstaid

I believe the first option, is to reconfigure your network controller. Choose that, choose your network device, then set it up (I'm assuming your router is probably using DHCP, so it should be pretty straight forward to take the defaults)

once you're done, test that it's working again..

Code

ping -c 5 aol.com

and you should get a successful ping result.

Now, go back to the webUI, run apt clean again as raulfg3 suggested, then reinstall portainer.

After that, you may want to check for system updates. Just be forewarned this could change your OMV IP address. (you'll get no access to anything)...

If that's the case, download angryIP scanner to one of the devices on your network, and scan your network. It should find your OMV server and give you your new IP address. After that, if you need help setting it to your "old" IP, just post and I"m sure someone can talk you through setting a static IP.

https://angryip.org/

Alles anzeigen

Well, you are totally wrong. I had no issue with internet access, logging to OMV5, even accessing MariaDB through SQLyog. I DID all of the things you suggested and that did NOT work. So, instead assuming (and you know how to spell it) that someone is incompetent, look a little bit deeper first before jumping into conclusions.

Zitat von KM0201

Then you had a different problem than him. I'm not wrong.. read the output of the error. It says right there...

DNS error.. exiting.

As he described, after an attempt to update Portainer, Portainer died and would NOT reinstall. That is MY understanding of his initial problem. I had exactly the same issue and the only way to fix it, without super experts advice, I did what I did. BTW, do you have solution to the problem as described?. So far whatever you suggested did not work for me, so I am all ears.