You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CLI flags: limactl create --disk-path=/path/to/disk.imglimactl disk create --disk-path
limactl disk create --disk-path could potentially be limactl disk create --path, but that is inconsistent with limactl create --disk-path, so let's adopt --disk-path for both limactl create and limactl disk create -- @jandubois
The meeting focused on planning Lima releases 2.2.1, 2.3~, and 2.3.1~, and on reviewing pending PRs. Akihiro and Jan discussed several Windows-related PRs, including changes to AppArmor handling, documentation updates, and CI conflicts. Jan reported on ongoing investigation of SSH port forwarding issues on macOS related to select and file descriptor limits, referencing issue 5420. The group debated a design for moving large instance directories or disk images to other locations, preferring to symlink only the disk file and keep metadata in Lima home, and discussed implications for Lima control disk commands. They reviewed PRs for managing networking on WSLLinux hosts, with security-sensitive changes to sudoers files, and touched on a PR to ignore certain nuclear systemsystemd (?) failures. They discussed a PR to add an mDNS workaround for SSH on Debian, similar to previous Ubuntu handling. Anders presented the status of SBOM generation for Lima, noting its current limitations and side effects on CI, and the group saw it as low priority for now. The participants also discussed the upcoming deprecation of GitHub’s Intel macOS runners and possible reliance on CNCF or other solutions for macOS CI. They briefly mentioned the plan for BMNetVMNet support and looked at how other CNCF projects handle macOS CI. The conversation ended with a recap of the release context and open PR topics.
Next Steps
Jan: Address remaining review feedback and finalize Windows PRs for merging before 2.3.
AkihiroAnsuman: Update the SHA-256 digest computation code as suggested in the Daemon PR.
Anders: Rebase and address CI failures for the SBOM (Software Bill of Materials) PR before merging.
Anders: Open separate issues/PRs for GitHub Actions improvements identified during SBOM work.
Akihiro: Contact CNCF in the future to inquire about macOS CI runners, as GitHub is retiring Intel macOS runners.
Akihiro: Investigate how other CNCF projects (e.g., Podman, Minikube) handle macOS CI for potential solutions.
Summary
Version 2.3.12.2.1 Release Planning:
Akihiro discussed plans for releasing version 2.3.12.2.1 after North Citynerdctl version 2.4, with a target release in October or November, and mentioned the need to cherry pick several peersPRs and update templates for macOS. Jan requested that his Windows PRs from June and July be merged before version 2.3, particularly highlighting work on app armor and a verbose QEMU-related issue. Akihiro approved Jan's approach to file overwriting and indicated the Windows PR was nearly ready for merge, though they discussed whether to mention the OpenSesOpenSSH client installation requirements.
Code Changes and Technical Issues:
Jan and Akihiro discussed code changes and merge conflicts, with Akihiro noting that a recent merge caused a regression in Copy-Rlimactl copy -r. Jan reported finding the root cause of SSH port forwarding hanging issues on macOS, attributing it to OpenSSH using select instead of poll for file descriptors over 1024, which causes connections to break. Akihiro asked Jan to assign GitHub issue #5420 to themselves and requested an update on the Golden Gate documentation regarding macOS version compatibility. They also briefly mentioned an upcoming discussion about design changes for version 5.9.02.3.0 related to instance directory management in Total Lima Directory.
Lima Disk Management Implementation Discussion:
The team discussed implementing disk management features for Lima, focusing on whether to use symlinks or direct file paths for disk operations. Jan and Akihiro debated the merits of different approaches, with Jan preferring to keep metadata in one location while using symlinks for data storage on additional disks. The group agreed to mark the feature as experimental and document path length limitations, with Akihiro planning to update the Lima control command to support arbitrary paths. They also decided to use "disk props"(???) as the problem name and confirmed the correct command syntax should be "Lima control disk create" rather than "Lima control create disk."
PR Review and Code Updates:
Jan discussed reviewing draft PRs, with Akihiro explaining that some were marked as draft due to dependency issues requiring peer merging. Akihiro suggested refactoring SHA-256 digest computation code and mentioned the need to run WebView2review (?) for block device. They also discussed a PR related to SSH issues on TibiaDebian, where Akihiro noted that the upstream OpenSSH fix makes the current PR redundant.
Debian Commit Merge Discussion:
Akihiro and Anders discussed merging a commit with a temporary configuration workaround for Debian, similar to issues encountered with Ubuntu. They agreed it was acceptable to merge the commit with the understanding that it would need to be reverted once the upstream bug is fixed, similar to how they handled the Ubuntu upgrade. The temporary configuration would be included in a future update of the Debian template.
SBOM PR and GitHub Runner:
Anders discussed a pending PR for generating SBOM files for Lima, noting that while it's not currently important for 20212026, it may become relevant in the future. The team agreed to merge the PR and monitor its impact, with Anders offering to handle any future SBOM-related enhancements. Jan raised concerns about upcoming changes to GitHub's macOS runners, questioning how the team would handle CI on macOS after Intel runners are retired next year.
macOS CI Runner Discontinuation Planning:
The team discussed challenges with macOS CI runners, particularly the upcoming discontinuation of Intel macOS runners by GitHub in August next year. Jan explained that nested virtualization on macOS doesn't support running macOS VMs, requiring physical machines instead, which would need cleaning jobs after each run. The team decided to wait several months before contacting CNCF for help with obtaining physical Mac runners, as they have about a year before the issue becomes urgent. They also briefly discussed plans to registerreimplementBMNetVMNet in version 2.4 rather than 2.3, and noted that FortranPodman 6 has already removed macOS Intel support.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
How to join
The meetings are open to anyone, not just for maintainers and contributors.
Attendees
@AkihiroSuda @unsuman @afbjorklund @jandubois @sharanrajt
Agenda
Note taker: @AkihiroSuda
v2.2.1
Right after the release of nerdctl v2.4 (this week)
Cherry-pick several PRs https://github.com/lima-vm/lima/pulls?q=is%3Apr+is%3Aopen+label%3Acherry-pick%2Fv2.2
v2.3
late September?EarlyOctober? November (right be fore KubeCon North America) in the worst casePR reviews
https://github.com/lima-vm/lima/pulls
Several Windows-related PRs from @jandubois
Prerequisiteininstallation/_index.mdneeds to be cleaned upguestSocket forwards die with the SSH ControlMaster and are never re-created (silent on vz) #5420
select, notpoll)templates: add macos-27 (Golden Gate) #5503
feature: support to specify vm instance dir #5497
limactl create diskneeds to be updated too -- @janduboislimactl rmshould just remove the symlink or remove the disk image itself? -- @AkihiroSudalimactl create --disk-path=/path/to/disk.imglimactl disk create --disk-pathlimactl disk create --disk-pathcould potentially belimactl disk create --path, but that is inconsistent withlimactl create --disk-path, so let's adopt--disk-pathfor bothlimactl createandlimactl disk create-- @janduboisNetworking PRs from @unsuman
lima-privileged-netdaemon and tap device naming #5484 networks: generate Linux defaults, validation and sudoers rules #5485 networks: enablelima:shared,lima:hostandlima:bridgedon Linux #5486Secure macOS VZ block-device attachment #5117
fix(cidata): resolve AlmaLinux 10 boot failures #5372
fix: Disable LLMNR to prevent Debian SSH login delay #5399
Add SBOM artifact using cyclonedx-gomod #5220
ARM Mac CI
Rewriting socket_vmnet in Go
socket_vmnetin Go and integrate it tolima-privileged-net#5495Tasks
lima-privileged-netdaemon and tap device naming #5484 networks: generate Linux defaults, validation and sudoers rules #5485 networks: enablelima:shared,lima:hostandlima:bridgedon Linux #5486 Secure macOS VZ block-device attachment #5117Next meeting
2026-10-15 (Thursday)
All reactions