You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
The text was updated successfully, but these errors were encountered: