• generic/ext/external/ssh: Generic/External internal driver for all OS #2000
  • "ext" is cryptic can be interpreted as both extended and external
  • name doesn't "work" now, after internal/external driver framework
  • the docker-machine driver was called "generic" (as in generic cloud*)
  • the minikube driver was eventually renamed to "ssh" (after a long time)

* https://github.com/machine-drivers/docker.github.io/blob/346a066b6886f3deab23383f14822c0a32ec38d8/machine/drivers/generic.md

This is useful if you are using a provider that Machine does not support directly or if you would like to import an existing host to allow Docker Machine to manage.

AI-generated meeting note

Quick Recap

The team discussed environment variable propagation and bug reports related to architecture validation, while also addressing CI failures and testing concerns. They reviewed driver naming conventions and decided to move external drivers to separate repositories from the main Lima repo, with plans to maintain the API as experimental in Lima 2.0. The team established regular meeting schedules and discussed using AI for meeting notes, while also addressing the need for written summaries of GSOC project results and infrastructure improvements.

Next Steps

• Ansuman to fix the bug where architecture type x86_64 for vz is not returning an error when it should.
• Ansuman to share the error message and command to reproduce the issue on Slack.
• Ansuman to decide by tomorrow whether to split the PR or proceed with a single PR.
• Ansuman to fix the validation config issue causing CI failures.
• Ansuman to prepare a gist containing completed work and remaining tasks for GSoC final submission.
• Anders to create a discussion for brainstorming name suggestions for the external SSH driver.
• Anders to keep the external driver code up to date while name negotiations continue.
• Akihiro to schedule the next meeting for August 26th.
• Akihiro to continue creating meeting entries in GitHub discussions.
• Ansuman to handle social media accounts for posting monthly meeting updates and project news.

Summary

Environment Variables and CI Issues:
The team discussed environment variable propagation from host to guest, with Jan suggesting further discussion via GitHub as the current proposal might not cover all use cases. Ansuman reported a bug related to architecture type validation for vz, which he will share on Slack, and discussed splitting a PR into smaller parts. The team also addressed CI failures, with Jan noting some flakiness in GitHub tests, and Akihiro advised Ansuman to proceed with merging despite CI errors if they are not actionable. Ansuman mentioned preparing a data gist for final submissions, which will be made public as it will be added to the TO 25 archive.

Driver Repository and API Updates:
The team discussed driver naming conventions and the decision to move external drivers to separate repositories from the main Lima repo, with existing core drivers like WSL2, Apple Container, and QEMU remaining in the main repo. They agreed that the API would remain experimental in Lima 2.0, with API version checking to be implemented to ensure compatibility between drivers and Lima. Anders reported that he had rebased the previous driver on the framework and it was now compatible, though it still requires manual configuration for pre-provisioned machines.

External Driver Naming Convention Discussion:
The team discussed naming conventions for external drivers, particularly regarding SSH implementation. Anders explained that while SSH is currently used for provisioning and communication between Lima and external machines, it's not necessarily the only protocol that could be used in the future. Abiola suggested avoiding the term "SSH" in the naming as it implies a specific protocol, and Jan proposed "unmanaged" as an alternative name but acknowledged it wasn't ideal. The team agreed to create a poll for brainstorming alternative names before making a final decision.

Establishing Regular Meeting Schedule:
The team discussed scheduling regular meetings, with Akihiro confirming the next meeting would be on September 18th. They agreed to establish a regular cadence, with Akihiro taking responsibility for scheduling and creating meeting entries, while notes would be rotated among attendees. Abiola emphasized the importance of fixed dates for better planning, and Jan suggested using the calendar's iCal link for easier meeting discovery.

AI Meeting Notes and Updates:
The team discussed using AI for meeting notes and agreed to add meeting information to the repository's README with links to the calendar and meetings category. Ansuman volunteered to handle social media posting for the project, and the team decided to schedule their next meeting for July 26th. They also discussed the need for a written summary of the GSOC project's final results and infrastructure improvements before the next meeting, with Anders noting that the framework's API would be tested through additional drivers.