With the command
omv-firstaidI could fix the problem with the connection to the internet.
But apt-clean didn't help. I've no access to the webinterface of Portainer. I've tried to install via OMV-GUI and also by hand. No connection to Portainer.
The installation of Portainer didn't give any errors.
So no clue what's going on.
Cockpit runs fine.
Really funny...
Just for info.
The last hour I did a brand new installation of OMV v5 (over Debian 10). With latest OMV5-extras I've installed docker and tried to install Portainer, but I didn't have access to the web interface. Even OMV showed me that Portainer was successful installed.
Than I've tried cockpit and this worked perfect. I could open the Webinterface of cockpit.
So the best way right now to use Portainer is to install it by hand (via command line)
Edit: sorry, but even installing Portainer by hand didn't work. I don't know what's going on here
I had the same problem with the broken internet connection after installation of docker.
Intranet worked but no internet. So I changed from DHCP to a fixed IP-address with DNS (from google) and the problem is gone. Internet was working again.
You're right. I had an error in my thinking 
Normally the kernel exists side by side.
Thank's for the info
I've also created a new script that will install OMV itself if it isn't installed already - https://github.com/OpenMediaVa…-Developers/installScript
Yesterday and today I did a new installation of Debian 10 (netinstall - just ssh server and system utilities enabled) and used your script to install OMV over Debian 10.
Unfortunately the script stops because of missing sudo.
I normally install Debian, login with root (direct on the server), enable ssh and when I connect via a client to the server (with 'ssh root@IP-server') and try to run the script, it says that sudo is missing.
So I've installed sudo by hand and afterwards everything is working fine.
Maybe you can update in your script the matter to install sudo first.
Thanks in advance
Just to understand. Does that mean that Proxmox overwrite the kernel installed by Debian/OMV?
Thanks, but maybe a stupid question. Why do someone need Proxmox? As I understand is a virtualization software (like VMware) and you can run several different systems at the same time.
In my case I just need one system (OMV) and want to benefit from the power of the hardware. That's why I install direct (Debian with OMV) on the PC. And therefore Debian 10 still uses the 4.19 kernel.
Or do I miss something in my thinking?
OMV 5 use kernell 5.x , please consider to upgrade OMV or do a new fresh install to test it.
How do you know it. I've installed OMV v5 (over Debian 10) and it uses kernel 4.19. I haven't seen a kernel above 4.9.
I followed your guide, but I used the script to install OMV + omv-extras directly. Did a clean installation on VMware Fusion.
It didn't work either. So no connection to portainer 
But I can install it manually anyway. And when I get a second PC I will install it on a real hardware.
Thanks for the info. Maybe it has something to do with the activated tab for the installation of Portainer after enabling omv-extras.
Because when you have a look on this side you can see the enabled Portainer docker (it's in green) even you haven't installed docker. Maybe this is the issue?
And after installation of docker the system won't install portainer.
I had the same issue. By installing portainer manually (via CLI) it was working like it should
for years it's been suggested to only install the SSH server. It didn't cause an issue before... now it obviously does.
I learned here (in the second video - starting at 06:49) to install both. With that I think you're on the right way. But anyway not necessary to dispute that.
Thanks for the info. So the issue must be docker and Portainer
did you do the installation in a VM or on real hardware?
I had the same problems in my VM (VMware Fusion v15 on Mac Mojave). Yesterday I did a fresh installation of Debian 10 and OMV (the script of @ryecoaaron) but after installation of docker the network connection was gone. Even Portainer didn't work (error to connect).
This week I will get a used PC and I will do a fresh installation on real hardware again. Just to be sure that the problem is maybe the VM and not the software.
when you do a fresh installation of Debian (I always use the "netinst" version) I always tick "ssh-server" and "standard system utilities". I didn't face any problems by doing that. These two I would always recommend.
When you follow the guide to install OMV v5 over Debian 10, the error comes when you have to install the (security) key.
It says that gnupg, gnupg1 or gnupg2 is missing. By installing all three (I don’t know which exactly) the error is gone and you can continue with the guide
Gesendet von iPhone mit Tapatalk
Thank you for the tip with manually downloading. This could solve the issue. I downloaded the image manually and afterward I've installed Portainer via CLI and now I can connect to the web interface.
Thanks again 
I know that it's not necessary, but docker do it anyway. Before downloading docker looks locally and if it can't find the image it downloads from the internet.
But thanks I will give it a try
root@OMV-Testsystem:~# dpkg -l | grep -E "cockpit|docker"
ii docker-ce 5:19.03.2~3-0~debian-buster amd64 Docker: the open-source application container engine
ii docker-ce-cli 5:19.03.2~3-0~debian-buster amd64 Docker CLI: the open-source application container engine
root@OMV-Testsystem:~#
This is the output. I also have tried to install Portainer via command line
docker volume create portainer_data
docker run -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainerand this was the output:
root@OMV-Testsystem:~# docker volume create portainer_data
portainer_data
root@OMV-Testsystem:~# docker run -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer
Unable to find image 'portainer/portainer:latest' locally
docker: Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:60260->[::1]:53: read: connection refused.
See 'docker run --help'.
root@OMV-Testsystem:~#Another test with "Cockpit". Also not working.
This will download and place docker-compose in /usr/local/bin/.This stands under "Install docker". But when I have a look under /usr/local/bin, there's nothing.
Under "/var/lib/docker" all the folders are there.
That's what I also did. After installation of docker I restarted the server. As well after turning off and on of Portainer.
I think that the tab for installation of Portainer was enabled by default. Even docker wasn't installed.
So no clue what to do next