Drive redirection doesn't work in LXC container in Proxmox

[Mogaba]

Hello,

I can't make drive redirection work in LXC container in Proxmox. The container is privileged with all features enabled. /dev/fuse exists with 666 permissions and the user is in fuse group. The thinclient_drives folder is here but it's empty.

Here's xrdp-chansrv.log:

[20240506-11:43:18] [INFO ] Socket 12: AF_UNIX connection received
[20240506-11:43:18] [INFO ] Detected remote drive 'D:'
[20240506-11:43:18] [INFO ] Detected remote drive 'C:'

xrdp-sesman.log:

20240506-11:55:35] [INFO ] Socket 12: AF_INET connection received from 127.0.0.1 port 49104
[20240506-11:55:35] [INFO ] ++ created session (access granted): username mva, ip 10.66.1.20:1789 - socket: 12
[20240506-11:55:35] [INFO ] starting Xorg session...
[20240506-11:55:36] [INFO ] Starting session: session_pid 846, display :10.0, width 1376, height 740, bpp 24, client ip 10.66.1.20:1789 - socket:
12, user name mva
[20240506-11:55:36] [INFO ] [session start] (display 10): calling auth_start_session from pid 846
[20240506-11:55:36] [ERROR] sesman_data_in: scp_process_msg failed
[20240506-11:55:36] [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans
[20240506-11:55:36] [INFO ] Starting X server on display 10: Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xo
rgxrdp.%s.log
[20240506-11:55:36] [INFO ] Found X server running at /tmp/.X11-unix/X10
[20240506-11:55:36] [INFO ] Found X server running at /tmp/.X11-unix/X10
[20240506-11:55:36] [INFO ] Found X server running at /tmp/.X11-unix/X10
[20240506-11:55:36] [INFO ] Session started successfully for user mva on display 10
[20240506-11:55:36] [INFO ] Starting the default window manager on display 10: /etc/xrdp/startwm.sh
[20240506-11:55:36] [INFO ] Starting the xrdp channel server for display 10
[20240506-11:55:36] [INFO ] Session in progress on display 10, waiting until the window manager (pid 847) exits to end the session

xrdp.log:

[20240506-11:55:30] [INFO ] Socket 12: AF_INET connection received from 10.66.1.20 port 1789
[20240506-11:55:30] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20240506-11:55:30] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20240506-11:55:30] [INFO ] Security protocol: configured [SSL|RDP], requested [SSL|HYBRID|HYBRID_EX|RDP], selected [SSL]
[20240506-11:55:30] [INFO ] Connected client computer name: MVA-TS
[20240506-11:55:30] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc006 is unknown (ignored)
[20240506-11:55:30] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc00a is unknown (ignored)
[20240506-11:55:30] [INFO ] xrdp_load_keyboard_layout: Keyboard information sent by the RDP client, keyboard_type:[0x04], keyboard_subtype:[0x00],
 keylayout:[0x00000409]
[20240506-11:55:30] [INFO ] xrdp_load_keyboard_layout: model [pc105] variant [] layout [us,ru] options [grp:alt_shift_toggle]
[20240506-11:55:30] [INFO ] TLS connection established from 10.66.1.20 port 1789: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384
[20240506-11:55:30] [INFO ] xrdp_caps_process_pointer: client supports new(color) cursor
[20240506-11:55:30] [INFO ] xrdp_process_offscreen_bmpcache: support level 1 cache size 5242880 MB cache entries 100
[20240506-11:55:30] [INFO ] xrdp_caps_process_codecs: nscodec, codec id 1, properties len 3
[20240506-11:55:30] [WARN ] xrdp_caps_process_codecs: unknown codec id 5
[20240506-11:55:30] [INFO ] xrdp_caps_process_codecs: RemoteFX, codec id 3, properties len 49
[20240506-11:55:30] [INFO ] Loading keymap file /etc/xrdp/km-00000409.ini
[20240506-11:55:30] [WARN ] local keymap file for 0x00000409 found and doesn't match built in keymap, using local keymap file
[20240506-11:55:35] [INFO ] connecting to sesman on 127.0.0.1:3350
[20240506-11:55:35] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20240506-11:55:35] [INFO ] sesman connect ok
[20240506-11:55:35] [INFO ] sending login info to session manager. Please wait...
[20240506-11:55:36] [INFO ] xrdp_wm_log_msg: login successful for user mva on display 10
[20240506-11:55:36] [INFO ] login successful for user mva on display 10
[20240506-11:55:36] [INFO ] loaded module 'libxup.so' ok, interface size 10296, version 4
[20240506-11:55:36] [INFO ] started connecting
[20240506-11:55:36] [INFO ] lib_mod_connect: connecting via UNIX socket
[20240506-11:55:36] [INFO ] lib_mod_log_peer: xrdp_pid=842 connected to X11rdp_pid=848 X11rdp_uid=500 X11rdp_gid=500 client_ip=10.66.1.20 client_p
ort=1789
[20240506-11:55:36] [INFO ] connected ok

[Mogaba]

So the problem was not container specific, there was an error in systemd logs:
failed to exec fusermount: No such file or directory

The distro I use (ALT Linux) has fuse3 installed by default. And there's no fusermount executable, only fusermount3. I made a symlink fusermount -> fusermount3 and now drive redirection works fine.