The lima-vm config on lima-kilo does not currently mount the current directory inside the VM when ran on a Linux host. This is caused by the QEMU mount using the 9p filesystem driver, which is not included in the "cloud" kernel variant being used in the Debian cloud image. Manually installing the base kernel image and rebooting fixed the issue on my local machine.
Description
Description
Event Timeline
Comment Actions
I'm using it on fedora 41 without issues (recreated it last week), I'll try again see if I can reproduce
Comment Actions
It seems that 9p was made the default when bumping to 1.0.0:
In one of the pull requests doing the move, they mention that for Debian they still default to the old reverse-sshfs, but you might need to manually revert the mount type sometimes:
https://github.com/lima-vm/lima/pull/1953
So maybe we should just force that?
Though for some time I've been thinking on building our own image/pre-install some stuff in it so the bootstrapping is quicker, if we do so then we can install the right kernel at that point, that will enable read-write mounts.
Comment Actions
dcaro opened https://gitlab.wikimedia.org/repos/cloud/toolforge/lima-kilo/-/merge_requests/220
start-devenv: set the mounttype to reverse-sshfs for linux
Comment Actions
dcaro merged https://gitlab.wikimedia.org/repos/cloud/toolforge/lima-kilo/-/merge_requests/220
start-devenv: set the mounttype to reverse-sshfs for linux