[VirtualBox 5.2.6 Verfugbar
Virginie Fayad
After installing Leap 15.5 i installed virtualbox 7.0.10. After installing there came a question about activating USB-Access for vbox-Guests. Acceapting this lead to the USB-Entries in usr/lib/udev/rules.d/60-vboxdrv.rules
I have installed a docker container and it is working, but only on my local machine. I can access it through the specific container IP, but noone else can access this from another computer on the same local network. In other words how do I make my container reachable for other people?
Thanks for your comment, but you have misunderstood the issue. Problem is not accessing container from the host machine, but other computers on the local network. This is because docker-machine assigns an ip to the docker vm that is only visible from the host machine. My question is how can other computers on local network access my docker container.
Sorry, my bad. Now for your requirement you will have to run the boot2docker vm network in bridge mode so that your VM will get an IP in your LAN subnet. After that when you expose ports using -p other people in the network can access it using the ip which you got for the boot2docker vm. In virtualbox you should modify the Adapter 2 settings as shown. Btw the bridge interface in your case may vary.
Hi ,
Am new to docker.am trying to bring up one setup on linux.
Where i have 2 container i.e A and B and i have one proxy server X
I am able to send msges from A to X but am not able to send or ping from X to B.
I want to know how i can achive this.
By Dockert HOSt container have eth0 and eth1 interface
Container A is using eth0 to send packets from A to X and i want to use eth1 to recieve the packet from X
Can you please help me on this?
Hi!
I am also new to docker and even I got a lot of things working perfectly, I am completely failing on doing one simple thing:
I have one server running several docker container providing different services on different ports. Using the simple bridge network, this works totally fine. Example: Unifi Controller is :8080 and UniFi Video is :7080.
But by installing more and more services as docker containers, I run into difficulties as multiple ports are the same on different services. In addition, I want to switch some services to a secondary IP address that is not the one that is set as exposed host in my router.
So I followed the guide and saw to create pools for ISOs and the actual storage. Did that, installed my OS, and now I am wanting to expose/mount a specific shared folder to one of the VMs I made. How is this done? Is this possible to do like in Docker? It's mounted on the OMV server as a shared folder already. e.g. /srv/dev-disk-by-uuid-db707ffe-637d-4e7a-aad0-68ab3c803185/NAS2/myfolderiwanttoaccess (I am wanting to overwrite/point to the folder that's inside the VM titled myfolderiwanttoaccess.
I just access a samba or nfs share just like I would any other system. But you can passthrough a filesystem. This is fairly easy to do with virt-manager but I can see what it would take to do it with the plugin.
Lol I just bricked it by trying to edit the XML I guess. Is there a default folder where the XML is stored so I can maybe edit it correctly? My VM instance I was editing disappeared from the VMs list. (I removed the wrong hard disk :/) Hoping I can edit in back the proper hard disk name.qcow2.
Just installed Windows 10 as guest. Works good. I created CDROM for installation ISO. I want to remove it but don't know how to do it correctly. I don't see the CD disk in gui while guest machine is stopped or running. Manual deletion of ISO causing error.
One problem at a time is much easier to solve... If OMV is a virtual machine running on virtualbox, you are not enabling nested virtualization. I don't remember how to do that in virtualbox but I would recommend not running nested virtualization.
You are combining two things that are a pain in the ass - nested virtualization and Windows. It won't boot because you technically moved Windows to completely different hardware. I don't use windows but I am pretty sure you have to do some special things to it and/or boot in safe mode and/or boot with the Windows ISO/fix the boot record. All of that is beyond on the scope of the plugin and really this forum.
You do not want to convert an ova. That is a compressed zip file with one or more disks and the machine description file in it. There is no need to export something from virtualbox. Just copy the virtual hard disks and convert them.
yesterday i tried to setup a VM fo the first time with this plugin. But i had some trouble with the pools/folders. I followed the "How To Use the Openmediavault-KVM plugin" exactly. I made new shared folders "pool" and "ISOS" within one of my existing local SSD's. I gave the folders to the libvirt-qemu owner with all permissions. Then i copied a ISO file in the ISOS folder. Next i created the Pools in the Plugin and activated them. And this is where my problems begin, normaly i should now see my ISO file in the ISO's Tab but there is nothing (Screenshot 1), it's like greyed out. Instead my ISO is mounted as a Volume. I dont know whats the problem here. I thought it is the folders permissions and ownership. I tried to give the folders many different owners (root, my own private...) and different combinations of permissions but nothing works. What could be my Problem ?
oh ok, sorry. I think that was a misconception from my side. Is there any possibility to use a qcow2 file to create a VM via the plugin ? Or can you convert a qcow2 file to an iso ? The problem is: For the specific VM i want to make there is only a qcow2 file provided. I want to run a Home Assistant OS.
Is there any possibility to use a qcow2 file to create a VM via the plugin ? Or can you convert a qcow2 file to an iso ? The problem is: For the specific VM i want to make there is only a qcow2 file provided. I want to run a Home Assistant OS.
Yeah cool thanks. It worked and i can see the Home Assistant now running in the NoVNC Window. And there is my next problem (sorry that I'm such a noob). Now i want to reach the Home Assistant UI via Browser from another PC in my local network, but i cant reach the IP adress or the ".local:8123" Adress that Home Assistant is showing me (screenshot 1). I get following errors in Chrome. I thought that i configured the Network properly. I made a "Macvtap Bridge" to my network adapter and selected that at the VM creation. What could be the problem ?
oh man yeah, it worked. That was the only combination that i didn't tried at first. Thank you for the help. Now it's reachable and works fine. Next step is to get my reverse proxy running, so that i can reach in from outside with proper domain name. But i think that i can get this on my own
795a8134c1