"~" mountpoint is empty after starting a lima container

[marcoslor]

After starting the default container, the /Users/{user} directory exists but is empty.

Something to mention about my setup is that the “default” container folder is symlinked from another partition to the ~/.lima/ folder.

The log shows:

[   42.874685] cloud-init[1295]: + mountpointvar=LIMA_CIDATA_MOUNTS_0_MOUNTPOINT
[   42.876811] cloud-init[1295]: + eval echo $LIMA_CIDATA_MOUNTS_0_MOUNTPOINT
[   42.890933] cloud-init[1295]: + echo /Users/marcos
[   42.892203] cloud-init[1295]: + mountpoint=/Users/marcos
[   42.902011] cloud-init[1295]: + mkdir -p /Users/marcos
[   42.914171] cloud-init[1295]: + id -g marcos
[   42.917884] cloud-init[1295]: + gid=1000
[   42.925878] cloud-init[1295]: + chown 501:1000 /Users/marcos
[   42.927431] cloud-init[1295]: + mountpointvar=LIMA_CIDATA_MOUNTS_1_MOUNTPOINT
[   42.933604] cloud-init[1295]: + eval echo $LIMA_CIDATA_MOUNTS_1_MOUNTPOINT
[   42.941857] cloud-init[1295]: + echo /tmp/lima
[   42.950844] cloud-init[1295]: + mountpoint=/tmp/lima
[   42.952364] cloud-init[1295]: + mkdir -p /tmp/lima
[   42.953938] cloud-init[1295]: + id -g marcos
[   42.955155] cloud-init[1295]: + gid=1000
[   42.960437] cloud-init[1295]: + chown 501:1000 /tmp/lima
[   42.965358] cloud-init[1295]: + install -m 755 /mnt/lima-cidata/lima-guestagent /usr/local/bin/lima-guestagent
[   43.049977] cloud-init[1295]: + [ -f /sbin/openrc-init ]
[   43.051777] cloud-init[1295]: + rm -f /home/marcos.linux/.config/systemd/user/lima-guestagent.service

[jandubois]

Did you define additional mount points in lima.yaml? I've only seen this issue while trying to use overlapping mounts, which don't work (with sshfs): #302

[marcoslor]

The mountpoints are the ones found in default.yaml:

mounts:
  - location: "~"
    writable: null
    sshfs:
      followSymlinks: false
  - location: "/tmp/lima"
    writable: true
    sshfs:
      followSymlinks: null

Tried changing - location: "~" to the absolute path of my home folder, removing /tmp mount point, and deleting the mount point folder in client, now limactl start default gives me:

INFO[0071] [hostagent] Mounting "/Users/marcos"         
INFO[0072] [hostagent] fusermount: reading /etc/fuse.conf: missing newline at end of file 
INFO[0072] [hostagent] fusermount: option allow_other only allowed if 'user_allow_other' is set in /etc/fuse.conf 
WARN[0103] [hostagent] failed to confirm whether /Users/marcos [remote] is successfully mounted 

[marcoslor]

The log hinted an invalid fuse.conf file.

INFO[0072] [hostagent] fusermount: reading /etc/fuse.conf: missing newline at end of file 
INFO[0072] [hostagent] fusermount: option allow_other only allowed if 'user_allow_other' is set in /etc/fuse.conf

Viewing the file with nano showed the last line contained a series of @ characters. I removed them and rebooted the service.