VM writeable mount not actually writeable when working on an M2 machine.

[mgadshead]

Apologies in advance for the giant wall of text, also if I'm posting in the wrong place please let me know.

I'm using Lima via Trellis, and everything works perfectly on my macbook running on an intel processor. However, the exact same setup on my M2 machine runs into errors every time that all appear to be due to the VM mount not being writeable, except that my tests indicate that it is indeed writeable. I've already exhausted my efforts into finding out whether the issue is on the Trellis side, so I'm trying over here!

Though the VM does start, the Trellis server provisioning doesn't work due to the non-writeable issue (I think). To further confuse matters, restarting the computer makes the issue go away, but obviously I'd rather not have to restart my computer every time I start or boot up a project.

Here's an example error that seems to imply a lack of writeable drive (apparently that's what "No usable temporary directory found" implies):

RUNNING HANDLER [common : restart journald] ************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: FileNotFoundError: [Errno 2] No usable temporary directory found in ['/tmp', '/var/tmp', '/usr/tmp', '/home/matthew.linux']
fatal: [default]: FAILED! => {"changed": false, "module_stderr": "Traceback (most recent call last):\n  File \"<stdin>\", line 107, in <module>\n  File \"<stdin>\", line 92, in _ansiballz_main\n  File \"/usr/lib/python3.10/tempfile.py\", line 496, in mkdtemp\n    prefix, suffix, dir, output_type = _sanitize_params(prefix, suffix, dir)\n  File \"/usr/lib/python3.10/tempfile.py\", line 265, in _sanitize_params\n    dir = gettempdir()\n  File \"/usr/lib/python3.10/tempfile.py\", line 438, in gettempdir\n    return _os.fsdecode(_gettempdir())\n  File \"/usr/lib/python3.10/tempfile.py\", line 431, in _gettempdir\n    tempdir = _get_default_tempdir()\n  File \"/usr/lib/python3.10/tempfile.py\", line 362, in _get_default_tempdir\n    raise FileNotFoundError(_errno.ENOENT,\nFileNotFoundError: [Errno 2] No usable temporary directory found in ['/tmp', '/var/tmp', '/usr/tmp', '/home/matthew.linux']\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}

Here's the output of some test commands that seem to imply everything is fine on the VM:

df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           392M 1004K  391M   1% /run
/dev/vda1        97G  2.0G   95G   3% /
tmpfs           2.0G     0  2.0G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/vda15       98M  6.3M   92M   7% /boot/efi
mount0          229G  182G   47G  80% /srv/www/test.com/current
/dev/vdb         36M   36M     0 100% /mnt/lima-cidata
tmpfs           392M  4.0K  392M   1% /run/user/501

df -i
Filesystem        Inodes   IUsed     IFree IUse% Mounted on
tmpfs             501198     664    500534    1% /run
/dev/vda1       12966400   84467  12881933    1% /
tmpfs             501198       1    501197    1% /dev/shm
tmpfs             501198       3    501195    1% /run/lock
/dev/vda15             0       0         0     - /boot/efi
mount0         493479715 2356915 491122800    1% /srv/www/test.com/current
/dev/vdb               0       0         0     - /mnt/lima-cidata
tmpfs             100239      25    100214    1% /run/user/501

cat /etc/fstab
LABEL=cloudimg-rootfs	/	 ext4	discard,errors=remount-ro	0 1
LABEL=UEFI	/boot/efi	vfat	umask=0077	0 1
mount0	/srv/www/test.com/current	virtiofs	rw,nofail,comment=cloudconfig	0	0

Finally here's the mount config file:

vmType: "vz"
rosetta:
  enabled: false
images:
- location: https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64.img
  arch: x86_64
- location: https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-arm64.img
  arch: aarch64

mounts:
- location: /Users/matthew/Sites/localhost/test.com/site
  mountPoint: /srv/www/test.com/current
  writable: true

mountType: "virtiofs"
networks:
- vzNAT: true
portForwards:

containerd:
  user: false
provision:
- mode: system
  script: |
    #!/bin/bash
    echo "127.0.0.1 $(hostname)" >> /etc/hosts

If anyone can help make sense of this it would be much appreciated.

[sudocurse]

Experiencing the same thing on an M1 using virtiofs. I added

- mounts:
  - location: "~"
    writable: true
  - location: "/tmp/lima"
    writable: true

and stopped + started the VM.

$ touch /Users/sudocurse/tmp-file
touch: cannot touch '/Users/sudocurse/tmp-file': Read-only file system

[sudocurse]

Experiencing the same thing on an M1 using virtiofs. I added

- mounts:
  - location: "~"
    writable: true
  - location: "/tmp/lima"
    writable: true

and stopped + started the VM.

$ touch /Users/sudocurse/tmp-file
touch: cannot touch '/Users/sudocurse/tmp-file': Read-only file system

Oh, deleting and re-creating the VM from the modified config seems to have worked in my case