[GH-ISSUE #4] Evaluate linking against containerized VirtualBox #3

New issue

Open

opened 2026-02-25 21:32:22 +03:00 by kerem · 1 comment

kerem commented

2026-02-25 21:32:22 +03:00

Owner

Originally created by @clue on GitHub (Jan 12, 2015).
Original GitHub issue: https://github.com/clue/docker-phpvirtualbox/issues/4

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.

Originally created by @clue on GitHub (Jan 12, 2015). Original GitHub issue: https://github.com/clue/docker-phpvirtualbox/issues/4 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](https://registry.hub.docker.com/u/jencryzthers/vboxinsidedocker/). This image does not currently expose vboxwebsrv, however.

kerem added the

help wanted

new feature

labels

2026-02-25 21:32:22 +03:00

kerem commented

2026-02-25 21:32:22 +03:00

Author

Owner

@imoore76 commented on GitHub (Dec 17, 2015):

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.

@imoore76 commented on GitHub (Dec 17, 2015): 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`.

kerem referenced this issue

2026-02-25 21:32:24 +03:00

[PR #3] [CLOSED] Minor changes #7