does your CPU support virtualization? And did you activate it in your BIOS?
Surprisingly, That was the issue.
I say surprisingly, as I was running VMWARE before OMV and didn't change the settings when installing OMV. I was able to run VM's on Cockpit as well. So not sure why it was disabled or worked on other software. Anyways good catch!
Hi,
Currently testing this add on and I have an issue creating a Ubuntu 18.04 VM. Using the standard options, it fails to load, when checking the system log, I get the following error
libvirtd[650]: invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm
I have tried looking around the forum, but couldn't locate anything.
Thanks
Everything seems fine. What is the problem?
Not able to reach the default the gateway on the VM.
Hi,
I have a new installation of OMV 5. I am trying to run Virtual Servers on the installation but I am having some issues with getting Bridge Network to work so the Virtual Machines are on the physical network. I used OMV-Extras to install Docker and Cockpit.
I followed the steps here to create the bridge network: https://jamielinux.com/docs/li…etwork.html#bridge-debian
The physical interface name is eno1
This is the output from the command brct1 show br0
bridge name bridge id STP enabled interfaces
br0 8000.a0481cadc446 no eno1
vnet0On Cockpit, under the virtual machines network settings, On a new server it automatically applied the network bridge
I have applied a IP Address to the physical network on the virtual machine, which can be seen below.
My linux skills are not the best and I am most likely missing some thing basic. I been on this for 2 days now. So anyone has any pointers, it would be really appreciated.
Thanks
Didn't take too long to sort.
You can create the snapshots using the terminal console with some basic command line.
So all good over here for myself!
Thanks!
I went down the route of installing OMV directly on the hardware and then using omv-extras to install Cockpit.
Cockpit looks pretty decent to be honest, only issue I have at the minute, is creating snapshots. So once I work this out, if its even possible, this will be the perfect solution for me.
Was very simple to do.
The storage situation is much easier when running OMV with the KVM plugin. You can have a file server without a VM. No need for large VMDKs or drive passthru.
That's a valid point, didn't really put much thought into the storage side,
Hi,
I am looking consolidate my home appliances, I have a couple of Virtual Servers running on my main PC and OMV running on dedicated hardware. As I am looking to upgrade to OMV 5, I would like to know what the recommended method would be:
I am not sure which is best option, I know VMWARE on hardware gives me future options regarding more virtual appliances, and would allow me to throw away OMV if its not suitable, but then I am also thinking, if OMV can do what VMWARE can (Provide Virtual Machines) and more, then maybe the 2nd option is best.
I look forward to your points of view.
Thanks
Hi Guys,
I was able to activate LetsEncrypt this morning without using the docker network that was created. For some reason, if I included that, then it would not work. Not sure what issues that will cause.
Regardless, I can see now why the interface is not exposed to the WWW. Changing the UI port resolves that issue!
I guess now it is time to try setup another docker on one of the subdomains and see if it accepts the SSL.
Thanks for your help.
the letsencrypt container has an inbuilt reverse proxy.
Ok, That answers most of my queries.
I have seen the video multiple times. Even before I posted today.
I can only assume, the letsencrypt container has the proxy included within the container, so when you browse to myplex.duckdns.net you would specify the URL on the receiving container and it would load plex. The same would be for myha.duckdns.org it would load the Home Assistant container?
The issue I have is, my router does not support Port Address Translation (PAT) so I am not able to forward port 80 -> 90 and 443 -> 450. But even with using PAT, I can't see how multiple containers would work on the same IP Address and Port without some element directing the header request to the correct container.
I use letsencrypt to use HTTPS to access my containers,
Maybe I am over thinking here.
But letsencrypt requires port 443 to be open and forwarding to your OMV IP Address. So if you browse to your DNS address, does it not route to the OMV login page?
https://domain.duckdns.org -> WAN IP ADDRESS -> http://HTTPS://LANIPADDRESS (OMV LOGIN)
Would you not need a reverse proxy to route requests based on URL headers to other ports?
https://domain.duckdns.org -> WAN IP ADDRESS -> http://HTTPS://LANIPADDRESS -> REVERSE PROXY -> http://HTTPS://LANIPADDRESS:8443
All you need to do in your router is expose the OMV machine IP address and only the specific port (or ports) the container is using. This does not expose the entire OMV machine to the world.
Ok, So what your saying, the containers will always use the same IP Address and you just permit the ports you select for the container applications.
No need to assign a detected LAN address to each container.
Hi All,
I am new to OMV and Docker. I am really enjoying the challenge and self learning, not to mention it is also helpful for my career. However I have some questions.
I know how to make OMV accessible to the internet. That is working perfectly fine, however I do not want to make the whole OMV system available to the external world, I would only want, let's say, Home Assistant or ZoneMinder which is running in its own container. What I would like to do, would be assign a local IP Address to the container so I can port forward 443 traffic to this software directly. Excluding the routing settings, could anyone point me to a document that details assigning a static IP Address to the container so it can be accessed on the physical network. (Not the same IP Address as OMV)
There is a chance I could be miss understanding the requirements here, and I just need to assign the IP Address to the software?
thanks in advance.
