How might I mount a host directory into a container and set raw.idmap in one command?

[derekmahar]

NFS, CIFS/SMB, or SSHFS don’t appear to be available disk device types.

[derekmahar]

@qkiel

shift=true tells Incus to use VFS idmap shifting - a flexible uid/gid shifting at the kernel level. This way you don’t have to set up idmap by hand. I don’t know why that doesn’t work on proxmox.

As for a single incus config command, I don’t think it exists

Today I discovered that Incus idmap shifting does work on Proxmox running Linux kernel 6.5.13-3-pve, but fails when I attempt to mount into a container a host directory to which I’ve already mounted an SMB/CIFS share. I found, however, that this works on Linux Mint Debian Edition (LMDE) 6 running Linux kernel 6.5.

Any idea why mounting an SMB/CIFS share to a host directory might prevent idmap shifting for that directory? How might I instruct Incus to report a more detailed error message than “Error: Failed to start device “sftpgo”: Required idmapping abilities not available”?

[qkiel]

This might help:

Mount SMB with id shifting

cifs doesn’t support idmap shifting yet. Your best bet is to instead perform the mount from inside the container using a FUSE version of cifs. smbnetfs looks like a potential candidate for this.

[derekmahar]

@qkiel

This might help:
Mount SMB with id shifting - #2 by stgraber

Thank you for the reference! I’ll consider smbnetfs.

Note that my test using idmap shifting to mount a host directory into a container on LMDE 6 worked only because I had mounted a normal directory, not a mounted CIFS share! When I tried the same test using a mounted CIFS share, it failed.