Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Evaluate linking against containerized VirtualBox #4

Open
clue opened this issue Jan 12, 2015 · 1 comment
Open

Evaluate linking against containerized VirtualBox #4

clue opened this issue Jan 12, 2015 · 1 comment

Comments

@clue
Copy link
Owner

clue commented Jan 12, 2015

Besides running VirtualBox on a separate host and connecting to it, one can also start VirtualBox in a container. The container would need to expose the vboxwebsrv port and we would need to support linking it.

See e.g. docker pull jencryzthers/vboxinsidedocker. This image does not currently expose vboxwebsrv, however.

@imoore76
Copy link

Why would one run VirtualBox inside a container? If you really want to containerize VirtualBox, the solution would be to have vboxwebserv bind on all ports and link the container to it, then edit phpvirtualbox's config to point to the linked container. Actually, since it looks like your script looks for linked 18083 ports, it should "just work" with any existing clue/docker-phpvirtualbox container. The jencryzthers/vboxinsidedocker image would have to expose port 18083 and run vboxwebsrv bound to all host ips vboxwebsrv -H 0.0.0.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants