At work I was initially using podman on an M1 MacBook, but switched to Rancher Desktop + dockerd a couple months ago after having too many issues with podman. Many in my org are also moving away from podman for similar reasons.
I could never get bind mounts working consistently, relying instead on volumes, which are more awkward/less explicit when persisting local DBs used when testing.
I've had zero problems with Rancher Desktop + dockerd - definitely recommend it for M1 users that are having issues with podman.
> I could never get bind mounts working consistently
What type of problems were you seeing? Was it with podman or through podman desktop, and possibly some issue with what it was attempting?
bind mounts are a pretty standard kernel feature, so I'm wondering how podman/podman desktop could have been screwing it up, unless it was some user level permissions thing.
I wish I remembered the exact error; it was just with podman though. Podman desktop being newer, I hadn't really tried it out much.
FWIW, it could simply be chalked up to M1 weirdness. We have an ongoing list of various workarounds for the M1, whereas those using Intel MacBooks seem to be mostly fine.
I could never get bind mounts working consistently, relying instead on volumes, which are more awkward/less explicit when persisting local DBs used when testing.
I've had zero problems with Rancher Desktop + dockerd - definitely recommend it for M1 users that are having issues with podman.