Posts by Huberer

I've updated the above how-to (point no. 2 and 4) because today I couldn't update to the latest Virtualbox. By killing all the processes related to VB I was able to update again (v6.1.12).

Hello,

with the help of TechnoDadLife I've installed openvpn-as via docker to connect to my home server from outside.

It's possible to have access to my home server (OMV v5) via the IP-address of the server. But I've some dockers running like PlexMediaServer (Port 32400) or TVHeadend (Port 9981).

When I enter the IP-address of my home server, together with the port of PMS or TVH, in the browser of an Openvpn-client, I can't connect to these dockers. The IP-address, without any port, allows me to connect to the OMV-server.

Now my question is, how can I have access to my dockers.

Any help is appreciated

Thanks in advance

Hello,

unfortunately there's something missing in the Virtualbox-Installation-Guide under OMV v5.

The process of updating Virtualbox.

I always got the error of still running VBoxSVC daemon therefore I couldn't update Virtualbox.

1. Stop your VM's

2. stop Virtualbox-services under CLI:

sudo systemctl stop vboxweb-service
sudo systemctl stop vboxdrv
sudo systemctl stop vboxautostart-service

3. Stop VBoxVSC daemon with:

sudo killall VBoxSVC

4. find and kill other process

ps -A | grep VB
sudo kill <pid>

5. Update Virtualbox. I've downloaded the VB-package (.deb) and installed it via CLI

dpkg -i virtualbox-6.1_6.1.x-xxx.deb

With these steps I was able to update Virtualbox

And to update the extension pack just follow the guide in the Guide-section by downloading

cd ~/
wget "link to the latest extension pack" (like today https://download.virtualbox.org/virtualbox/6.1.10/Oracle_VM_VirtualBox_Extension_Pack-6.1.10.vbox-extpack)

and with the command --replace you can update EP

sudo VBoxManage extpack install --replace Oracle_VM_VirtualBox_Extension_Pack-6.1.10.vbox-extpack 

after that I're rebooted my OMV-server and everything was up-to-date

Quote from aindriu

How do I go about creating a virtual machine from an .ISO image?

Just install VirtualBox liked described here and install Ubuntu iso...

Today I did the step to disable AppArmor (how-to see two posts above) and after reboot I've installed the proxmox kernel.
Everything is running fine. No problems with portainer anymore and even VirtualBox runs great. No need to do any modifications.

@sfu420

Now by googling around I found this thread here.
Really interesting that nobody could remember anymore

Thank you for this great info. Now I know why portainer is not working with the proxmox kernel.

Maybe @votdev or @ryecoaaron know why AppArmor is not in the OMV installation iso but in the Debian iso.

But according to this webside it's not recommended to disable AppArmor.

Disable AppArmor
AppArmor is a security mechanism and disabling it is not recommended. If you really need to disable AppArmor on your system:


$ sudo mkdir -p /etc/default/grub.d
$ echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT apparmor=0"' \
  | sudo tee /etc/default/grub.d/apparmor.cfg
$ sudo update-grub
$ sudo reboot

At the moment I still use the stable kernel v4.19

@roru69

First of all I want to thank you for the real great VirtualBox-Guide here. It's a pity that VirtualBox is not anymore in the Debian 10 repo.
With your how-to it was easy to install. Thanks again.

There's still one issue I had.
After I did all the steps in the guide I wanted to log in the web interface (IP-Server:8080) but neither with the vbox user nor with phpvirtualbox-webgui user I couldn't log in. I always got the info that user/password is incorrect.
So I was looking around in the www and found a hint to use admin/admin for user/password. With that I could log into the GUI.

Why it is like that? Did I something wrong or is this correct to use admin/admin.

Till now I didn't have time to create a VM. First I want to be sure that the basic stuff is running without any issues.

Thanks in advance

Quote from 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

Quote from 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?

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 .....

But just to know. Which kernel do you use?

Gesendet von iPhone mit Tapatalk

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

I know about TABs @macom I work a lot with CLI
But as I saw on different guides for docker-compose some are mixing the paths. Like /srv/dev-disk-by-label/xxx and /sharedfolders/xxx
I read somewhere that paths with /srv/dev-xxx should be more stable than /sharedfolders/xxxx

@draddy
I know what symlinks are but didn't work with it. I also didn't know about the plugin (shame on me).

What I do with my containers and compose-files is to copy them. So when I do a fresh installation, I create the same folder structure again under OMV. Put the compose-files to a special folder, run them to create the container. Stop the container, delete the new one and replace it with the backup. Of course I've to change permissions and owner. With that I don't face any problems.

Quote from KM0201

If you use filesystem labels,

Sorry, what do you understand by that. Would you be so kind and post an example. Thanks in advance

@Gst

wie @draddy schrieb, ohne deine compose-file ist es nur raten mit der Glaskugel.

Quote from ryecoaaron

there had only been a few commits

Sorry, I didn't check the commits. I've just had a look at the date of the last chance. So I can't say how active this repo is. But I will check KVM anyway. This is an official repo so why not to try.
Thanks for the hint on that

Quote from ryecoaaron

plus phpvirtualbox isn't really actively maintained anymore.

I guess yes. You can see it here that updates are still made.

You're right the repo for the virtualbox is a one man show. It's not fix if there're updates in the future or not.

@ryecoaaron

Thanks. I know that OMV is not an OS. OMV is just a GUI for Debian Server. This is what I learned for sure in the last years
I've installed virtualbox via CLI and it was very easy to install. I saw that Virtualbox is not in the Debian repos and I also read why. But with adding the repos it was very easy. I also found that someone is supporting an unofficial repo for Virtualbox for Debian 10.
I also could install the extension pack but, than came phpvirtualbox. That was really terrible but at the end and with a lot of testing I also could get phpvirtualbox to run. But the autostart of the VM's was the real pain therefore I stopped everything and deleted virtualbox.
Maybe I will look at KVM and see how this works.

Thanks anyway for the info.

Now I found out that there's a phpvirtualbox image on docker. Maybe I will test this to see if it's possible to run VM's under OMV/Debian.

Hello,

is there a chance to get Virtualbox working under OMV v5?
It looks like that this is the first "Server OS" without the possibility to run virtual machines besides OMV (except by using ESXI - which I really don't know how it works). OMV v4 with the Virtualbox Plugin was great. I really loved it.
Maybe there's a chance to get Virtualbox running under OMV v5.

Thanks in advance