docker.machine

Edit: The project does not run on "docker machine" as per the graceful correction by OrbStack's developer below[2]. It's a proprietary container interface that - as far as I could tell - runs on the outdated and unsupported "docker machine"[1]. An alternative would be to run a more recent container runtime of your choosing in a VM through UTM which works beautifully. [1]: https://github.com/docker/machine [2]: https://news.ycombinator.com/item?id=37107233

Just visit the repo: https://github.com/docker/machine It is archived and hasn't had a commit in almost 2.5 years. See also: https://github.com/docker/roadmap/issues/245

We use docker-machine at browserless.io for a lot of dev stuff, and noticed that new create calls weren’t working. It appears that docker version 20.10.0 has some kind of issue when docker-machine copies over configuration to the daemon. Workaround is to use a custom engine URL, eg https://releases.rancher.com/install-docker/19.03.9.sh GH issue: https://github.com/docker/machine/issues/4858

The process in the OP—starting a VM in Virtualbox, and having Docker use the VM—is basically a manual version of what docker-machine does automatically. https://github.com/docker/machine Even though it's all a VM under the hood, docker-machine makes it all feel a bit more streamlined/native. Also, the version of Linux it uses—Boot2Docker—will likely start up more quickly, and probably use slightly fewer resources as well. I'm using docker-machine so I can run Docker on OS X 10.9, which predates Docker Desktop (and Hyperkit).

This one: https://github.com/docker/machine/issues/3212 In essence, it is impossible to work with an existing Docker-managed host from another computer. I often work from home, and when I wanted to manage my Docker hosts from my laptop, it turned out to be impossible and this issue was closed without resolution. This was the day when I gave up on using native Docker.

Thanks! It was closed in favor of autoscaling with Docker Machine https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_r... it seems that Docker Machine doesn't support Kubernetes https://github.com/docker/machine/tree/master/drivers https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_r... introduces many dependencies. Not sure how to solve it. Maybe something like https://github.com/deric/gitlab-ci-mesos ?

looks great, but doesn't have a docker-machine driver yet https://github.com/docker/machine/pull/1401

This is a known bug, we're addressing it with a new version of open-vm-tools, there's a thread going on over at github[1] to track this. [1] https://github.com/docker/machine/issues/1460

The docker team completely ignored the great work the parallels team put into creating a parallels driver instead telling them to wait for the plugin architecture to be finished. Reference: https://github.com/docker/machine/pull/939

Let me chime in and say that getting rid of VirtualBox and moving to xhyve would be amazing. I was really sad when this PR was closed: https://github.com/docker/machine/pull/1358#issuecomment-126...

Super sorry to hear - we've had some issues with VirtualBox around networking and some setups we didn't anticipate -- Would be really appreciative if you'd give the latest 0.3.0 release candidate a whirl and see if it fixes the issue for you: https://github.com/docker/machine/releases.

Using docker-machine as a superset of boot2docker is my favorite on OS X instead of the "plain old" boot2docker command (due to simple local machine management and VMware Fusion support), doesn't it run on Windows since it also has an Hyper-V driver? [0]: https://github.com/docker/machine/tree/master/drivers

There has been a request (https://github.com/docker/machine/issues/504) but no PR yet.

> My ideal setup would be a hypervisor infrastructure with a bunch of VM's running only Docker applications. You should take a look at https://github.com/docker/machine and https://github.com/docker/swarm , they were designed with exactly that goal in mind!