Live data from Hacker News

Docker for Mac Without Docker Desktop

github.com

131–140 of 198 posts

Re: Docker for Mac Without Docker Desktop

#131
post #122
post #76

Earlier quoted context omitted.

You'll get the same issues, since utm uses qemu. Tried it a few days ago with x64 linux only to have the os crash while copying stuff over smb

FWIW I switched from Docker Desktop to UTM+Ubuntu+Docker a few months ago and it has been great.

ARM Ubuntu or X86?

Re: Docker for Mac Without Docker Desktop

#132
post #5

I've been exploring 2 alternatives (podman and colima) to replace my normal docker workflow, which is just building and running containers locally, sometimes with docker-compose. I started with podman but had issues with 2 main pieces of my workflow: docker-compose (or podman-compose) and shared volumes (with `run -v`). Switched over to colima and those worked out of the box for me ("brew install docker; brew install…

Podman works with docker-compose 1.x only and needs some finagling to work. I have this wrapper script as podman-compose #!/bin/bash set -e tmpdir=$(mktemp -d) port=$(podman system connection ls | grep -Eo 'localhost:\d+' | head -1 | cut -d: -f2) [[ -n $port ]] || exit 1 ssh -fnNT -L"$tmpdir/podman.sock":/run/user/1000/podman/podman.sock -i ~/.ssh/podman-machine-default ssh://core@localhost:"$port" -o StreamLocalBind…

Is this a short term issue or is nobody working on docker-compose 3.x compatibility?

Re: Docker for Mac Without Docker Desktop

#133
As 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 Mac.

Re: Docker for Mac Without Docker Desktop

#135
post #132

Earlier quoted context omitted.

Podman works with docker-compose 1.x only and needs some finagling to work. I have this wrapper script as podman-compose #!/bin/bash set -e tmpdir=$(mktemp -d) port=$(podman system connection ls | grep -Eo 'localhost:\d+' | head -1 | cut -d: -f2) [[ -n $port ]] || exit 1 ssh -fnNT -L"$tmpdir/podman.sock":/run/user/1000/podman/podman.sock -i ~/.ssh/podman-machine-default ssh://core@localhost:"$port" -o StreamLocalBind…

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.

Re: Docker for Mac Without Docker Desktop

#136

Earlier quoted context omitted.

Podman works with docker-compose 1.x only and needs some finagling to work. I have this wrapper script as podman-compose #!/bin/bash set -e tmpdir=$(mktemp -d) port=$(podman system connection ls | grep -Eo 'localhost:\d+' | head -1 | cut -d: -f2) [[ -n $port ]] || exit 1 ssh -fnNT -L"$tmpdir/podman.sock":/run/user/1000/podman/podman.sock -i ~/.ssh/podman-machine-default ssh://core@localhost:"$port" -o StreamLocalBind…

This is exactly why I ditched Podman. I really wanted to use it badly, but lacking an alternative to Docker Compose or compatibility with it in 2022 is unacceptable. Yes, there is technically a way you can orchestrate containers through configuration, and I don't remember what it was called, but I found it both difficult to use and learn. It's crazy to me that people wanted to develop an alternative to Docker... with…

There are use-cases that Podman can be used for that don’t involve Compose (yes, even with orchestration). Likewise there are a lot of features Podman and family have that Docker does not. Historically rootless is the big one; Docker sort of has that now but it’s still not daemon-less.

Re: Docker for Mac Without Docker Desktop

#137
post #20

Earlier quoted context omitted.

In case you missed it the license terms for Docker Desktop have changed and require companies with ~250 employees to start paying for it: https://www.docker.com/blog/updating-product-subscriptions/

And in those larger companies, just paying for the "coffee a month" may not be an option, since they insist all licenses are company owned and it's less effort to change my docker VM wrapper than get shit past my company's purchasing department in a reasonable amount of time.

It doesn’t help that the compulsory “Business” edition is burdened with the anti-feature of Docker Registry but that SSO is still “on the roadmap.”

There’s no way we would have gotten the product through IT Security Management on time, much less through purchasing. Docker appears to have fallen down a bit on their market research - they forgot that their real customer for the Business subscriptions weren’t the developers at large companies, but their software purchasing processes.

Re: Docker for Mac Without Docker Desktop

#138
post #131
post #122

Earlier quoted context omitted.

FWIW I switched from Docker Desktop to UTM+Ubuntu+Docker a few months ago and it has been great.

ARM Ubuntu or X86?

ARM 21.10. Greatly improved disk performance. (Not measured, just based on my dev experience with the RoR + MySQL app I am working on.). I did find file sharing via WebDAV and SMB to be lacking so ended up going with sshfs.

Re: Docker for Mac Without Docker Desktop

#139

As 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...

Re: Docker for Mac Without Docker Desktop

#140

Earlier quoted context omitted.

> why the heck doesn't the macOS kernel support native containerization? Because Apple has no plans of growing their server OS marketshare. I know there are benefits of using namespaces (containers) in the desktop market, but they don't sell iMacs/MBPs. Exterior design and heavy marketing is their sales strategy.

I never understood this, because surely some huge percentage of developers use Macs. Enterprises buy stacks of them nonstop. Just making that group happy would get you the reputation of being a developers machine, for serious computer people, which could translate into laymen purchases too.

Would developers really be happy with containers running macOS inside? Production is running Linux, so they need two sets of images and their local image will be different from the one running in production.
Post reply on HN