Community blogs and write-ups about Lima

[singhvishalkr]

Sharing a small curated index of posts, talks, and long-form write-ups about Lima from across the community. Opening this here in Show and tell (per @AkihiroSuda's suggestion on #4863) so it can grow organically as new pieces get published, rather than living in the docs tree.

CNCF / official

• Lima completes fuzzing audit -- CNCF, Oct 2024.

NTT Labs (Akihiro Suda et al.)

• containerd and Lima -- running containerd on Lima (Sep 2021).
• Accelerating Llama on Lima with WASI-NN RPC -- GPU-backed wasi-nn from a Lima guest (Jun 2024).
• containerd v2.0 / nerdctl v2.0 / Lima v1.0 -- the 2024 stable-release triplet.
• containerd v2.1 / nerdctl v2.1 / Lima v1.1 -- what landed in the follow-up (2025).

Community write-ups

• Lima: a nice way to run Linux VMs on Mac -- Julia Evans, Jul 2023.
• Exposing LoadBalancer services running on kind in Lima VMs -- Liz Rice.
• Why I chose limactl
• Lima: Linux on macOS without the ceremony
• Setup k3s single-node GitOps with Flux on Lima
• Lima on Tencent Cloud developer blog -- Chinese-language overview.

---

Happy to keep adding links as folks drop them in replies. If you've written something about Lima (getting started, benchmarks, use-cases, migrations from Docker Desktop, etc.), reply below and I'll roll it into the top post.

Note: this post was re-edited to fix Unicode mojibake (em-dashes had been garbled by a PowerShell encoding mishap on my side -- thanks @AkihiroSuda for flagging). ASCII -- now used throughout to avoid any future encoding roundtrip issues.

[singhvishalkr]

Thanks @unsuman -- I've folded all six of your links into the top post (under Community write-ups), alongside @AkihiroSuda's NTT Labs / CNCF suggestions.

(This comment originally listed the links here, but the text had been mangled by a PowerShell encoding mishap on my side -- @AkihiroSuda caught it and flagged it on #4863. Rewrote both the top post and this reply in clean UTF-8 with ASCII -- throughout to avoid any repeat roundtrip issues.)

[AkihiroSuda]

@singhvishalkr Unicode chars in your post are garbled

[singhvishalkr]

Thanks @AkihiroSuda -- nice catch, fixed.

Root cause: the body I posted via gh api had Unicode em-dashes (U+2014), and PowerShell on my side re-encoded them through the Windows-1252 console codepage before handing off to the GitHub API, so GitHub stored the classic UTF-8-as-Latin1 mojibake for each em-dash (three non-ASCII glyphs in place of the single character).

Rewrote the top post and the redundant reply above via GraphQL updateDiscussion / updateDiscussionComment, with the body sent as raw UTF-8 bytes from a file (-F body=@file.md), bypassing PowerShell's stdin re-encoding. Also switched to ASCII -- throughout instead of U+2014 so any future roundtrip through a non-UTF-8 stream can't reintroduce the issue.

Cross-checked the PR #4863 page I pushed earlier today (b900c08) -- its _index.md was written via [IO.File]::WriteAllText(..., UTF8Encoding(false)) and the blob bytes on GitHub confirm no mojibake there. The discussion posts were the only places affected.