Unreliable sshfs bind mount - directories/files gradually appear after container start

[rfay]

I note that after a container start, directories that already existed and were bind-mounted may gradually appear after the container start. I imagine this is due to using the sshfs bind-mount, and sshfs isn't completed before container start. Is there a way to force sshfs flush before bringing up a container with a bind-mount?

I'll work on a repro scenario, but I wanted to point this out. It showed up in a ddev test which used bind-mount and worked consistently on docker for mac (and everywhere else).

[rfay]

• Don't cache sshfs directory, fixes abiosoft/colima#99 lima-vm/lima#538 seems to fix this.

[abiosoft]

@rfay thanks for submitting the PR upstream.

[abiosoft]

This has been merged upstream and should be fixed now. Can you kindly update lima and try again?

[rfay]

With updated colima/lima I see the correct
ssh -F /dev/null -o IdentityFile="/Users/rfay/.lima/_config/user" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o Ciphers="^aes128-gcm@openssh.com,aes256-gcm@openssh.com" -o User=rfay -o ControlMaster=auto -o ControlPath="/Users/rfay/.lima/colima/ssh.sock" -o ControlPersist=5m -p 61506 127.0.0.1 -- sshfs :/tmp/colima /tmp/colima -o slave -o allow_other,cache=no

And the ddev test that persistently demonstrated the problem runs cleanly now.

Thanks!