2026-01-15 (Thursday)

[AkihiroSuda]

How to join

• Date: 2026-01-15 (Thursday) 05:30 UTC (Wednesday 21:30 PST, 06:30 CET, 11:00 IST, 14:30 JST) - 06:30
• Link: https://zoom-lfx.platform.linuxfoundation.org/meetings/lima
  • Zoom, Video recording, and AI-generated meeting note

The meetings are open to anyone, not just for maintainers and contributors.

Attendees

@AkihiroSuda @afbjorklund @jandubois @unsuman @dharsanb

Agenda

Note taker: @AkihiroSuda

FOSDEM (Jan 31-Feb 1)

• Lima v2.0: expanding the focus to hardening AI by @AkihiroSuda , Jan 31 (Sat) 15:30-16:00

KubeCon EU (Mar 23-26)

• Lima Project Updates: Expanding the Focus To Hardening AI by @AkihiroSuda and @unsuman , Mar 25 (Wed) 11:00 - 11:30

• Also applied for Kiosk, waiting for acceptance

v2.1

• https://github.com/lima-vm/lima/milestone/62

  • Expected to be released before KubeCon EU
  • We should prune milestone items in the next month

• limactl list --filter (yq-less, alternative to PR 4187) #4529 : implement limactl list --filter without depending on yq, to avoid yq expression injection attacks. Alternative for add filter option to list command #4187 -- @AkihiroSuda

  • not convinced to introduce another configuration languages @jandubois @unsuman @afbjorklund

• Disable env access and file load operations in yqlib #4405

  • Let's merge after adding test for yq multi-call binary, and, add a document to explain the "dialect" of yq language -- @AkihiroSuda

• add filter option to list command #4187 can be merged after merging Disable env access and file load operations in yqlib #4405 -- @AkihiroSuda @jandubois

• build(deps): bump the k8s group across 1 directory with 2 updates #4528 not mergable after dropping the support for Go 1.24

• Stub out HCL dependencies #4522

  • Not a fan of replace() -- @AkihiroSuda
  • Not urgent -- @jandubois
  • Other CNCF projects are using hcl/v2, so CNCF will have to review the exception request anyway ([License Exception Request] [hashicorp/hcl/v2 and its dependencies] [MPL-2.0, etc.] cncf/foundation#1242)
  • Not a blocker for v2.1

• Feature(cli): Add --sync to prevent AI agents from breaking the host files #4429 refactor: rsync and scp into copytool pkg #4521

  • --sync should take strings, not a boolean, to allow specifying arbitrary paths -- @AkihiroSuda

• cidata: strip control characters from user comment #4516 looks fine, the issue isn't realistic to happen?

• build(deps): bump github.com/golangci/golangci-lint/v2 from 2.6.2 to 2.8.0 in /hack/tools #4513 linter no longer allows "api" as a package name, it should be exceptionally allowed

• fix: Merge VMOpts from configurations #4503 looks fine

  • In the long-term defaults.go should be simplified using the template merging mechanism -- @jandubois

• build(deps): bump github.com/modelcontextprotocol/go-sdk from 1.1.0 to 1.2.0 #4491 the CI is failing, maybe a regression, or maybe an intentional change in MCP SDK. Needs analysis -- @AkihiroSuda @jandubois

• Add limactl watch command and JSON events for test scripts #4489 the command does not seem working as expected yet, but the basic design seems ok -- @AkihiroSuda

• feat: VZ configurable display, audio, and clipboard support #4480 feat: QEMU SPICE display and audio support #4479 looks like AI-generated. Too long and not maintainable -- @AkihiroSuda

• vz: Fix scrollbar issue with runtime swizzle #4476 does not seem appropriate as it monkey patches AppKit. Should be fixed in Code-Hex/vz

• feat(templates): add amazonlinux-2023 distro #4454

  • virtiofs issue seems worked around by adding mount.virtiofs helper -- @AkihiroSuda
  • Unlike other templates, there is no stable URL of "latest" images. -- @afbjorklund
  • Snapshot images are removed or retained? we thought removed but maybe retained. Needs checking. Asking in https://github.com/lima-vm/lima/pull/4454/changes#r2693143777 -- @AkihiroSuda

• Docker 29 in Lima shows containers that it cannot delete #4496 does not seem related to Lima? The issue is reported to happen with WSL2 (apparently non-Lima) . Hard to analyze without a reproducer. Docker 29 in Lima shows containers that it cannot delete #4496 (comment)

Tasks

• @AkihiroSuda : Add @norio-nomura to @lima-vm/committers and remove him from @lima-vm/reviewers per MAINTAINERS: promote Norio Nomura (norio-nomura) to a Committer #4511
• @jandubois : Update Disable env access and file load operations in yqlib #4405 (test and docs)
• all maintainers: please review and merge/reject PRs (we now have 60)

Next meeting

2026-02-19 (Thursday)

• Focus on pruning v2.1 milestone items

[afbjorklund]

Breaking change in Docker v29, when using the Podman server:

• Docker client v29 now requires Docker server v25 containers/podman#27890

Previously it was backwards compatible for 10 years, 1.24 -> 1.44:

moby/moby@2c59be7

---

It is related to what products the Docker company wants to support:

The daemon currently provides support for API versions all the way back
to v1.24, which is the version of the API that shipped with docker 1.12.0
(released in 2016).

Such old versions of the client are rare, and supporting older API versions
has accumulated significant amounts of code to remain backward-compatible
(which is largely untested, and a "best-effort" at most).

This patch updates the minimum API version to v1.44, matching the minimum
version of the client, and matching the API version of docker v25.0, which
is the oldest supported version (through Mirantis MCR).

The intent is to start deprecating older API versions when daemons implementing
them reach EOL. This patch does not yet remove backward-compatibility code
for older API versions, and the DOCKER_MIN_API_VERSION environment variable
allows overriding the minimum version (to allow restoring the behavior from
before this patch), however, API versions below v1.44 should be considered
"best effort", and we may remove compatibility code to provide "degraded"
support.

Not related to Lima per se, and you can use either podman or docker (v25)

Unfortunately this now makes the Podman API the "stable" one, not Docker API

It supports Podman 4.0.0 (2022), and eventually will support Docker 25.0.0 (2024)

var APIVersion = map[Tree]map[Level]semver.Version{
       Libpod: {
               CurrentAPI: Version,
               MinimalAPI: semver.MustParse("4.0.0"),
       },
       Compat: {
-               CurrentAPI: semver.MustParse("1.41.0"),
+               CurrentAPI: semver.MustParse("1.44.0"),
               MinimalAPI: semver.MustParse("1.24.0"),
       },
}

[AkihiroSuda]

Does not seem actionable on Lima's side. Maybe we should add a documentation somewhere?

[afbjorklund]

Currently we only have minimum documentation with regards to compability, so I think it is upstream?

templates/podman.yaml

# To run `podman` on the host (assumes podman-remote is installed):
# $ export CONTAINER_HOST=$(limactl list podman --format 'unix://{{.Dir}}/sock/podman.sock')
# $ podman --remote ...

# To run `docker` on the host (assumes docker-cli is installed):
# $ export DOCKER_HOST=$(limactl list podman --format 'unix://{{.Dir}}/sock/podman.sock')
# $ docker ...

But maybe something for the "book" (Lima Manual), when going beyond README and the website...

[AkihiroSuda]

AI-generated meeting note

Quick Recap

The team discussed upcoming events and project updates, including talks, PR reviews, and dependency management. They addressed various technical issues related to filter expressions, licensing concerns, and code improvements, with Jan and Akihiro engaging in detailed discussions about implementation approaches and potential regressions. The team also reviewed multiple PRs and code issues, including template problems and Docker compatibility concerns, while considering the timing of the next release before KubeCon.

Next Steps

• Akihiro: Merge PR 4405 after adding a test to ensure Lima CTL YQ binary is not affected by security preference configuration, and update documentation in the website/docs (not default.yaml) to explain the new security settings.
• Jan: Implement the filter option using YQ (after PR 4405 is merged), aiming for next week or as time allows.
• Ansuman: Update the PR related to specifying arbitrary parts (as discussed) and merge it.
• Akihiro: Remove Norio Nomura from the organization reviewer list and update team/organization leader settings as discussed.
• Jan: Review the Dima CT watch command PR and related PRs as requested by Akihiro.
• Akihiro: Update the quickstart guide as needed.
• All maintainers: Review and merge (or reject) the 6 GPRs currently in the queue, as requested by Akihiro.
• Jan and Akihiro: Prune the 2.1 milestone next month to focus on release-critical items before KubeCon.

Summary

Project Updates and PR Review:
Akihiro discussed upcoming events, including a talk at the end of the month and a project update session in March with Ansuman. They applied for the Teoscope and are awaiting acceptance. Akihiro also reviewed a PR for implementing a filter using white expression, but noted concerns about white expression injection. Instead, they proposed using the Continuity library to implement filter acceptance with Continuity Future expressions.

Lima Filter Expression Implementation:
The team discussed the implementation of filter expressions in Lima, with Jan expressing concerns about adding another configuration language and advocating for consistency in using YQ expressions across all options. Akihiro defended the simplicity of the proposed filter expressions and mentioned that powerful expressions could still be implemented using Dash YQ. The team agreed to disable certain operators for implementing filters and to document the changes in the website documentation. They also discussed bumping up dependencies and a PR for time sync functionality, which Jan had not reviewed yet.

Go Module Licensing Discussion:
Jan and Akihiro discussed a licensing issue related to Go modules and HCL version 2, noting that using Go mod vendor mode could be a workaround but might not be compatible with Akihiro's tool. Jan mentioned that YQ regressions need to be fixed before they can proceed, and he is also exploring CNCF project repos to identify additional projects using the problematic modules. They agreed to wait for the YQ regressions to be addressed and for further input from Ansuman before merging the related pull request.

Code Cleanup and PR Review:
The team discussed several PRs and code issues. They agreed to strip non-printable characters from comment fields, with Jan suggesting they should wait for an actual issue before extending this to other fields like usernames. Akihiro mentioned that partition name API issues could be addressed later, and Anders reported cleaning up legacy code from previous maintainers and AI bots, which has been completed.

Proposal Approval and Configuration Simplification:
Jan and Akihiro discussed the need for explicit approvals on a proposal, with Jan emphasizing the importance of clear approval marks. They also talked about simplifying logic in configurations by using refresh and template merging functionality, which Jan planned to implement eventually. Akihiro mentioned a protocol for creating CI or refreshing in the MCP Core SDK library, but they did not finalize this point.

PR Reviews and Release Planning:
The team discussed several PR reviews and issues, including a test validation problem and a Lima City Watch command that needs fixing. They reviewed Amazon Linux template issues, where Anders explained that the lack of stable URLs for snapshots is a design decision rather than a bug. The team also addressed Docker version 29 compatibility issues, with Jan noting that reverting to version 1.41 resolved the problems. Akihiro mentioned needing help with reviewing and merging six PRs, and the team discussed whether to do a release before KubeCon for version 2.1, with Jan suggesting they could prune the milestone next month.

[AkihiroSuda]

Corrections

Akihiro: Remove Norio Nomura from the organization reviewer list and update team/organization leader settings as discussed.

Correct, but the topic here is to add Norio Nomura to the committer list

Jan: Review the Dima CT watch command PR and related PRs as requested by Akihiro.

Dima CT → limactl

All maintainers: Review and merge (or reject) the 6 GPRs currently in the queue, as requested by Akihiro.

6 GPRs → 60 PRs

Jan and Akihiro: Prune the 2.1 milestone next month to focus on release-critical items before KubeCon.

All the maintainers are expected to involve in this

They applied for the Teoscope and are awaiting acceptance.

Teoscope → Kiosk

Akihiro also reviewed a PR for implementing a filter using white expression, but noted concerns about white expression injection.

white → yq

Instead, they proposed using the Continuity library to implement filter acceptance with Continuity Future expressions.

continuity → containerd

Akihiro defended the simplicity of the proposed filter expressions and mentioned that powerful expressions could still be implemented using Dash YQ

Dash YQ → --yq

They agreed to wait for the YQ regressions to be addressed and for further input from Ansuman before merging the related pull request.

Further input from Ansuman would be definitely appreciated, but I don't think we agreed to particularly wait for his input

Akihiro mentioned that partition name API issues could be addressed later, and Anders reported cleaning up legacy code from previous maintainers and AI bots, which has been completed.

partition name API issues → package name api issues ? (w.r.t. golangci-lint failure)

Jan and Akihiro discussed the need for explicit approvals on a proposal, with Jan emphasizing the importance of clear approval marks.

On which proposal ?

Akihiro mentioned a protocol for creating CI or refreshing in the MCP Core SDK library, but they did not finalize this point.

Creating what CI?

The team discussed several PR reviews and issues, including a test validation problem and a Lima City Watch command that needs fixing.

Lima City Watch → limactl watch

The team also addressed Docker version 29 compatibility issues, with Jan noting that reverting to version 1.41 resolved the problems.

This was noted by Anders #4526 (comment)

Akihiro mentioned needing help with reviewing and merging six PRs, and the team discussed whether to do a release before KubeCon for version 2.1, with Jan suggesting they could prune the milestone next month.

six PRs → sixty PRs

[jandubois]

Jan and Akihiro discussed the need for explicit approvals on a proposal, with Jan emphasizing the importance of clear approval marks.

On which proposal ?

I mentioned that for the purpose of maintainers voting, the GitHub checkboxes don't work: you can toggle them back and forth multiple times without any audit trail, and you also cannot tell who clicked a checkbox. So for voting we need either a PR approval, or a comment saying which way you intend to vote. Something that leaves a permanent record.

Akihiro mentioned a protocol for creating CI or refreshing in the MCP Core SDK library, but they did not finalize this point.

Creating what CI?

I have no idea.