News for hackers. Stuff that matters.

A comment on Asahi Linux Still Working on Apple M3 Support, M1n1 Bootloader Going Rust. Parent comment

Re:Asahi Linux Still Working on Apple M3 Support, M1n1 Bootl... by baby on Friday October 24, 2025 @04:04PM (#45698547)
Why is docker so bad on mac and why is apple not fixing that?
[ Parent | on HN ]
Re:Asahi Linux Still Working on Apple M3 Support, M1n1 Bootl... by oblio on Friday October 24, 2025 @05:46PM (#45699432)
Because they don't care and don't have to care.
[ Parent | on HN ]
Re:Asahi Linux Still Working on Apple M3 Support, M1n1 Bootl... by zbentley on Friday October 24, 2025 @06:04PM (#45699564)
There is now work from Apple in that direction: https://github.com/apple/container

No idea what the future of that project, or its potential integration with other container management systems might be, but it is certainly interesting at first glance.

[ Parent | on HN ]
Re:Asahi Linux Still Working on Apple M3 Support, M1n1 Bootl... by baby on Tuesday October 28, 2025 @05:11PM (#45739243)
According to chatgpt:

Why Not Use Apple Containers Instead?

Because Apple containers:

Aren’t meant for system-level isolation — they’re for app sandboxing.

Don’t provide process namespaces, cgroups, or Linux syscalls, which are essential to containerization.

Wouldn’t be compatible with the entire Linux-based Docker ecosystem (images, tooling, etc.).

So Docker sticks with Linux containers, running them in a VM layer on macOS.

[ Parent | on HN ]
Re:Asahi Linux Still Working on Apple M3 Support, M1n1 Bootl... by jemmyw on Saturday October 25, 2025 @09:15AM (#45703660)
Because docker containers need to run on a Linux kernel so it requires some form of VM on non Linux systems. No matter how well integrated that is it's never going to be as lightweight as running containers on Linux. It wouldn't be a trivial task to implement an emulation, if that's even possible.
[ Parent | on HN ]