Anyone running the latest OrbStack on macOS 27 yet? Any issues?

[jean-humann]

Hi all,

With macOS 27 out now, I wanted to check in with the community before upgrading.

Has anyone updated to macOS 27 and run the latest version of OrbStack on it yet?

A few things I'm curious about:

• Does OrbStack install and start up normally?
• Any issues with the VM, networking, or file sharing?
• Are the Docker and Kubernetes engines working as expected?
• Any crashes, virtualization-framework changes, or new permission prompts?

If you've tried it, please share:

• Your OrbStack version
• Your macOS 27 build number
• Mac model / chip (Apple Silicon or Intel)
• Anything that broke and any workarounds you found

Thanks!

[SeanLF]

Working fine here on macOS 27 beta 1.

• OrbStack version: 2.2.1 (2020100)
• macOS build: 27.0 beta 1 (26A5353q)
• Hardware: MacBook Pro, Apple M4 Pro, arm64

Ran through the checklist you posted:

• Install & startup: initializes normally, daemon reports Running. Got the usual permission prompts on first launch (the privileged helper install), nothing new or macOS 27-specific.
• Containers: Docker engine 29.4.0 (server-side), ran Alpine and nginx containers without issue. Egress networking works (curl to an external HTTPS host returns 200), and host port forwarding works (-p 18080:80 reachable on localhost).
• Linux VMs: created an Alpine 3.23 machine, command exec works, deleted cleanly.
• File sharing: verified both directions, reading a Mac file from inside the VM and writing back to the Mac home dir.
• Kubernetes: haven't enabled it, so can't speak to that one.

No crashes, no virtualization-framework breakage, nothing obviously off on beta 1. Will report back if anything surfaces under heavier use.

[jean-humann]

Thanks a lot @SeanLF for the thorough testing and write-up — really appreciate you covering startup, networking, file sharing, and the VM lifecycle. 🙏

One follow-up, since your setup is Apple Silicon (M4 Pro): did you get a chance to test amd64/x86_64 Linux containers (e.g. docker run --platform linux/amd64 ...)?

Good news on the roadmap front: Apple's Rosetta docs now state that "macOS 27 directly integrates support for Intel binary translation, without needing to install Rosetta … This enables support for Intel Linux binaries running in ARM virtual machines (VMs) as well as Intel Linux containers." So it should keep working through macOS 27 — the cutback to "a subset for older unmaintained gaming titles" only kicks in after macOS 27.

Since that path leans on Rosetta + the Virtualization framework together (historically the most fragile area across macOS upgrades), I'd still love to know whether amd64 containers actually run cleanly on beta 1 in practice.

Thanks again!

[SeanLF]

Tested amd64:

• Rosetta is the registered binfmt interpreter in the VM, not qemu
• --platform linux/amd64 alpine, python:3.12-slim, gcc:14 all run clean; compiled-and-ran a C binary under translation
• amd64 postgres:16 boots, takes writes, answers queries

No crashes or translation errors so far. Beta 1 caveats apply; I have not stress-tested JIT-heavy stuff like amd64 Node or Java yet.