virtualbox/module using coreos-4.3.6

[joggerjoel]

How do I fake centos linux header?

core@localhost ~ $ uname -a
Linux localhost 4.3.6-coreos #2 SMP Tue Apr 5 10:32:16 UTC 2016 x86_64 Intel(R) Xeon(R) CPU L5420 @ 2.50GHz GenuineIntel GNU/Linux

core@localhost ~ $ docker run -it virtualbox
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modules [ OK ]
Trying to register the VirtualBox kernel modules using DKMSError! echo
Your kernel headers for kernel 4.3.6-coreos cannot be found at
/lib/modules/4.3.6-coreos/build or /lib/modules/4.3.6-coreos/source.
[FAILED](Failed, trying without DKMS)
Recompiling VirtualBox kernel modules [FAILED](Look at /var/log/vbox-install.log to find out what went wrong)

When I executed Dockerfile.

WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (4.3.6-coreos) or it failed to
load. Please recompile the kernel module and install it by

       sudo /sbin/rcvboxdrv setup

[wood1986]

use -v to fake the kernel source
I can fake the kernel source but I got another error

[joggerjoel]

Ok let me know.. But how did you get it working first time?
On Apr 16, 2016 08:44, "WooD" notifications@github.com wrote:

I can fake the kernel source but I got another error

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#2 (comment)

[joggerjoel]

I think we need to find a compatible header binary.. I asked the coreos
team and they said it couldn't be done.
On Apr 16, 2016 08:44, "WooD" notifications@github.com wrote:

I can fake the kernel source but I got another error

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#2 (comment)

[wood1986]

docker run -it -v /lib/modules/:/lib/modules/ --privileged wood1986/virtualbox
you need to mount a volume from host. The OS itself has the binary and source but it has build error for some reason

[joggerjoel]

Can I get. Your dockerfile?
On Apr 17, 2016 01:11, "WooD" notifications@github.com wrote:

docker run -it -v /lib/modules/:/lib/modules/ --privileged
wood1986/virtualbox

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#2 (comment)

[wood1986]

Dockerfile
Dockerfile

[joggerjoel]

Ok thanks I will try soon
On Apr 17, 2016 13:20, "WooD" notifications@github.com wrote:

Dockerfile
https://github.com/wood1986/docker-library/blob/master/virtualbox/Dockerfile

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#2 (comment)

[joggerjoel]

But did you change the Linux header
On Apr 17, 2016 13:28, "Joel LaBelle" joel.labelle@gmail.com wrote:

Ok thanks I will try soon
On Apr 17, 2016 13:20, "WooD" notifications@github.com wrote:

Dockerfile
https://github.com/wood1986/docker-library/blob/master/virtualbox/Dockerfile

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#2 (comment)

[joggerjoel]

Coreos team said they won't provide
On Apr 16, 2016 01:24, "WooD" notifications@github.com wrote:

You figure out this step. Do you have the CoreOS kernel source and header?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#2 (comment)

[wood1986]

I don't think we can put the virtualbox into CoreOS

[joggerjoel]

What's your current setup then?
On Apr 19, 2016 01:00, "WooD" notifications@github.com wrote:

I don't think we can put the virtualbox into CoreOS

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#2 (comment)

[wood1986]

I am blocked by this

DKMS make.log for vboxhost-5.0.16 for kernel 4.3.6-coreos (x86_64)
Mon Apr 18 20:44:28 UTC 2016
make: Entering directory `/usr/lib/modules/4.3.6-coreos/build'

  ERROR: Kernel configuration is invalid.
         include/generated/autoconf.h or include/config/auto.conf are missing.
         Run 'make oldconfig && make prepare' on kernel src to fix it.

  LD      /var/lib/dkms/vboxhost/5.0.16/build/built-in.o
  LD      /var/lib/dkms/vboxhost/5.0.16/build/vboxdrv/built-in.o
make[4]: *** No rule to make target `/var/lib/dkms/vboxhost/5.0.16/build/vboxdrv/linux/SUPDrv-linux.o', needed by `/var/lib/dkms/vboxhost/5.0.16/build/vboxdrv/vboxdrv.o'.  Stop.
make[3]: *** [/var/lib/dkms/vboxhost/5.0.16/build/vboxdrv] Error 2
make[2]: *** [_module_/var/lib/dkms/vboxhost/5.0.16/build] Error 2
make[1]: *** [sub-make] Error 2
make: *** [__sub-make] Error 2
make: Leaving directory `/usr/lib/modules/4.3.6-coreos/build'

[joggerjoel]

I mean the setup which works with your current docker Makefile. I was under
the impression that you had it working :)

On Tue, Apr 19, 2016 at 4:45 AM, WooD notifications@github.com wrote:

DKMS make.log for vboxhost-5.0.16 for kernel 4.3.6-coreos (x86_64)
Mon Apr 18 20:44:28 UTC 2016
make: Entering directory `/usr/lib/modules/4.3.6-coreos/build'

ERROR: Kernel configuration is invalid.
include/generated/autoconf.h or include/config/auto.conf are missing.
Run 'make oldconfig && make prepare' on kernel src to fix it.

LD /var/lib/dkms/vboxhost/5.0.16/build/built-in.o
LD /var/lib/dkms/vboxhost/5.0.16/build/vboxdrv/built-in.o
make[4]: *** No rule to make target /var/lib/dkms/vboxhost/5.0.16/build/vboxdrv/linux/SUPDrv-linux.o', needed by/var/lib/dkms/vboxhost/5.0.16/build/vboxdrv/vboxdrv.o'. Stop.
make[3]: *** [/var/lib/dkms/vboxhost/5.0.16/build/vboxdrv] Error 2
make[2]: *** [module/var/lib/dkms/vboxhost/5.0.16/build] Error 2
make[1]: *** [sub-make] Error 2
make: *** [__sub-make] Error 2
make: Leaving directory `/usr/lib/modules/4.3.6-coreos/build'

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#2 (comment)

[wood1986]

docker run -it -v /lib/modules/:/lib/modules/ --privileged --entrypoint="/bin/bash" wood1986/virtualbox
./vboxdrv.sh setup

[joggerjoel]

I mean what bareos operating system do you have this working on?

On Tue, Apr 19, 2016 at 4:51 AM, WooD notifications@github.com wrote:

docker run -it -v /lib/modules/:/lib/modules/ --privileged
--entrypoint="/bin/bash" wood1986/virtualbox
./vboxdrv.sh setup

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#2 (comment)

[wood1986]

CentOS. my README.md, I mentioned host and container should run the same linux distribution and kernel version in order to get it running

[joggerjoel]

yes, I thought it was this:

coreos -> centos -> virtualbox -> windows 7

On Tue, Apr 19, 2016 at 4:55 AM, WooD notifications@github.com wrote:

CentOS. my README.md
https://github.com/wood1986/docker-library/blob/master/virtualbox.vboxwebsrv.phpvirtualbox/Makefile,
I mentioned host and container should run the same linux distribution and
kernel version

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#2 (comment)

[wood1986]

I tried to do that a year ago but I can't due to coreos kernel.

[joggerjoel]

yeah that really sucks.
so do you do it the other way around?

centos -> vagrant -> docker -> virtualbox -> windows 7.

I currently just use ubunut -> virtualbox -> windows 7.

The whole docker doesn't make sense if I can't do it from bare metal.

On Tue, Apr 19, 2016 at 4:58 AM, WooD notifications@github.com wrote:

I tried to do that a year ago but I can't due to coreos kernel.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#2 (comment)

[wood1986]

CentOS -> Docker -> CentOS -> VirtualBox vertified

[joggerjoel]

which system has the smallest footprint? centos or ubuntu; I suppose this
could be done in headless mode. What system allows you to connect to
virtualbox via remote? have you gotten rdp working.. trying to figure out
best remote system instead of using teamviewer. btw; my google hangout is
joel.labelle@gmail.com

On Tue, Apr 19, 2016 at 5:43 AM, WooD notifications@github.com wrote:

CentOS -> Docker -> CentOS -> VirtualBox vertified

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#2 (comment)

[wood1986]

I am not sure which one has the minimum footprint. I believe CentOS is because the minimal iso image size is just 603M. see CentOS-7-x86_64-Minimal-1511.iso

To remote control virtualbox, you can just use phpvirtualbox and don't need ssh or rdp to control the host. You can use the browser to remote control the VM via the VNC-like protocol.