Container not mounting /etc/fstab on boot

[sweaty-tim]

I am in the process of moving my containers from native LXC on Debian 11 to Proxmox and thus learning Proxmox in the process.

I have setup a Debian 11 container using 'pct' to mount a remote file system (SSHFS) using /etc/fstab. It mounts when I execute 'mount -a' without issue from inside the running container.

Is there something special I need to enable for Proxmox to execute /etc/fstab on boot?

 

[fweber]

Hi, I was able to have an sshfs mounted at boot inside a Debian 11 LXC with the following fstab entry:

user@HOST:PATH /mnt/sshshare fuse.sshfs defaults,reconnect 0 0

Can you post your /etc/fstab?

 

[dvdwsn]

I'm having the exact same issue as OP. Works with 'mount -a', but doesn't work automatically after a reboot.
My container is Debian 10 (Turnkey), trying to connect to a VM of OMV6 on the same node.

/etc/fstab
docker@172.16.11.22:/srv/mergerfs/snapraid/conf /mnt/config fuse.sshfs noauto,x-systemd.automount,_netdev,user,idmap=user,follow_symlinks,identityfile=/home/docker/.ssh/id_rsa,allow_other,default_permissions,ServerAliveInterval=15,ServerAliveCountMax=3,uid=1001,gid=101,reconnect 0 0 docker@172.16.11.22:/srv/mergerfs/snapraid/data /mnt/media fuse.sshfs noauto,x-systemd.automount,_netdev,user,idmap=user,follow_symlinks,identityfile=/home/docker/.ssh/id_rsa,allow_other,default_permissions,ServerAliveInterval=15,ServerAliveCountMax=3,uid=1001,gid=101,reconnect 0 0

I've been struggling with this for weeks, so this config has kept growing. user,idmap=user,follow_symlinks,uid=1001,gid=101
May not be needed, but various tutorials used them. ServerAliveInterval=15,ServerAliveCountMax=3 were added to try and avoid the connection from closing. But if I understand the purpose of x-systemd.automount correctly, I shouldn't need them?

 

[fweber]

Can you try removing the x-systemd.automount option, and replacing noauto with auto? Apparently systemd.automount doesn't work inside a LXC because autofs is not namespace-aware (some more info here). However, at least in my Debian 11 LXC, systemd does mount the sshfs at boot without the x-systemd.automount option.

 

[dvdwsn]

Can you try removing the x-systemd.automount option, and replacing noauto with auto?

That worked! Thank you!! I haven't fully tested, re permissions, etc, but it's mounted and navigable.
What does auto vs noauto do?

 

[fweber]

See e.g. here for some details: https://wiki.debian.org/fstab

I would guess that noauto,x-systemd.automount is a combination that works on ordinary systems (because it delegates the task to systemd.automount [1]). But since systemd.automount doesn't work within containers, we have to remove x-systemd.automount from the options, and use auto instead.

[1] https://www.man7.org/linux/man-pages/man5/systemd.automount.5.html

 

[dvdwsn]

The mount is working well so far. I haven't had any issues doing backups either which older posts said can cause the system to hang. One small issue is that the permissions set by newly created folders aren't how I'd like them. When created automatically it's set to rwxr-sr-x, but I would like rwsrwsr-x.
Any way I change this?

 

[fweber]

Glad to hear it works so far! sshfs uses SFTP under the hood, and apparently the SFTP server is responsible for setting permissions of files that are created via SFTP. If you use openssh, adjusting the default permissions of new files seems a bit complicated, but there are some posts online e.g. [1] [2].

[1] https://unix.stackexchange.com/q/237938
[2] https://bbs.archlinux.org/viewtopic.php?id=218434