I think it’s an issue with the generated Lima config not being updated properly.
What does your .trellis/lima/[site name].yml file look like? Here’s an example:
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/scott/dev/site
mountPoint: /srv/www/example.com/current
writable: true
mountType: "virtiofs"
ssh:
forwardAgent: true
networks:
- vzNAT: true
containerd:
user: false
provision:
- mode: system
script: |
#!/bin/bash
echo "127.0.0.1 $(hostname)" >> /etc/hosts
You can see my one site under mounts. One issue with the Lima integration is that file isn’t the source of truth, Lima itself will generate its own under ~/.lima/[site name]/lima.yaml. So there’s some situations where trellis-cli updates its config but it’s not reflected in the other Lima one.
This isn’t a proper solution but you could manually edit that file and stop + start the VM. trellis-cli should update these configs so if it doesn’t then it’s a bug. But there’s never going to be a way to support this without at least stopping the VM.
Even Vagrant required a specific vagrant reload command. Just provisioning wouldn’t pick up new mounts.