The heart of this is docker-machine which is deprecated
Yup.. > Docker Machine has been deprecated. Please use Docker Desktop instead. https://docs.docker.com/machine/
[deleted]
Docker for Mac Without Docker Desktop
141–150 of 198 posts
Re: Docker for Mac Without Docker Desktop
#142Earlier quoted context omitted.
Is this a short term issue or is nobody working on docker-compose 3.x compatibility?
I assume you meant 2.x; Compose 2.x is only ~4 months old. I believe the intention of the Podman team is to abandon their podman-compose and work on compatibility with docker-compose 2.x going forward.
The version of the file format is different to the version of the CLI tool. Compose (the file format) 3.x was introduced with Compose (the tool) version 1.10 in 2017: https://github.com/docker/compose/releases/tag/1.10.0
Re: Docker for Mac Without Docker Desktop
#143Earlier quoted context omitted.
Quoted post unavailable.
> macOS is mainly targeted at secretaries, managers and artists. Counterpoint: I've never seen someone in the Bay Area developing on a Windows machine, in any company I've worked at. In my experience, locally, it's more like 95% Mac, 5% Linux, and 0% Windows. Now, I know that neither of our anecdotes represent the state of the world in general, but the notion that "Macs are for non-techies" is laughable on the face o…
I had a windows laptop a few times while working. I much prefer it to Mac laptops (which is what I've been made to use most of the time), or even linux laptops. Most of my dev work targets linux but with visual studio code remote, or a shell, or a remote desktop, what I run on the local machine is less important.
What is important is having a set of keystrokes that make sense to me (the mac command button does not work well on my PC laptops, and remapping just makes stuff worse) and don't change over decades.
Re: Docker for Mac Without Docker Desktop
#144We do two strange things (right now) that only seem to work with Docker Desktop for Mac We use registry mirrors to access a registry over an SSH tunnel. Doesn't seem to work with Docker via Colima, etc. as it's initiating connections from inside the VM, which doesn't see the SSH tunnel. Broke with Docker Desktop for Mac 4.4.2 as well, and tbh I can't explain why it ever worked, but it did. Nerdctl just learned about registry mirrors like 3 weeks ago[0], but it looks like it's having containerd do the pull so it would be in the same boat.
We set up IP aliases on lo0, and bind containers to individual addresses. This lets multiple containers and their services be directly accessible from the host - and e.g. applications running in Windows on VirtualBox - without having to remap ports. I don't think any of the alternatives support this. I know Colima does not. I don't think anything including Docker Desktop have a way to expose the docker bridge adapter directly to the host.
Re: Docker for Mac Without Docker Desktop
#145As others have pointed out, Virtualbox doesn't work on ARM (M1). A few months ago I switched to a new setup on my M1 Max: running a Ubuntu VM in UTM ( https://mac.getutm.app/ ), and installing Docker there. I use Mutagen ( https://mutagen.io/ ) for syncing files between macOS and the VM, which works really well. There is a 10x-20x speed improvement running a large PHP (Drupal) project through the VM than Docker for M…
Any additional guidance or resources you can point to for setup with UTM and Mutagen? Lando on macOS with Docker Desktop is driving me insane...
It was pretty straightforward, following UTM's setup guide for Ubuntu, Docker's setup guide, and Mutagen's:
- https://mac.getutm.app/gallery/ubuntu-20-04 - https://docs.docker.com/engine/install/ubuntu/ - https://mutagen.io/documentation/introduction/installation
I create my Mutagen sync with a command like:
mutagen sync create --name=mysite ~/Sites/mysite ubuntu@192.168.64.2:~/mysite --ignore=node_modules,vendor --ignore-vcs --default-owner-alpha=tallytarik --default-group-alpha=staff
Other than that, it mostly just worked! Feel free to get in touch if you have more specific questions.
Re: Docker for Mac Without Docker Desktop
#146I know people doing docker dev are generally targeting a Linux of some sort, but why the heck doesn't the macOS kernel support native containerization? Come on Apple. Microsoft can do it. edit: this seems like a new development since my last whine/complaint on this topic: https://macoscontainers.org/
I don’t think it’s lack of support so much as lack of demand. MacOS containers sound like a solution looking for a problem.
Re: Docker for Mac Without Docker Desktop
#147Ehh I prefer limactl/nerdctl to this.
Re: Docker for Mac Without Docker Desktop
#148As others have pointed out, Virtualbox doesn't work on ARM (M1). A few months ago I switched to a new setup on my M1 Max: running a Ubuntu VM in UTM ( https://mac.getutm.app/ ), and installing Docker there. I use Mutagen ( https://mutagen.io/ ) for syncing files between macOS and the VM, which works really well. There is a 10x-20x speed improvement running a large PHP (Drupal) project through the VM than Docker for M…
One can use Vagrant and VMware (instead of Virtualbox) on ARM M1. VMware fusion is free and Hashicorp has released the VMware vagrant plugin for free as well.
Re: Docker for Mac Without Docker Desktop
#149This won't work on the new M1 macs since it uses VirtualBox
Yeah :( Ever since I switched to an M1, I haven't found a way to reliably build and run x86_64 containers on it. Docker desktop with Qemu is not just painfully slow, it's also very buggy and some containers just can't be built without crashing. Is there any alternative?
VMware fusion plus Vagrant.
Re: Docker for Mac Without Docker Desktop
#150Earlier quoted context omitted.
I assume you meant 2.x; Compose 2.x is only ~4 months old. I believe the intention of the Podman team is to abandon their podman-compose and work on compatibility with docker-compose 2.x going forward.
The version of the file format is different to the version of the CLI tool. Compose (the file format) 3.x was introduced with Compose (the tool) version 1.10 in 2017: https://github.com/docker/compose/releases/tag/1.10.0
Oh. I was only talking about the program and the interface it uses with the underlying runtime. Compose 2.x expects the underlying tool to have a different API.