docker-wine VS pulseaudio-module-xrdp

Docker container This alternative would eat more resources than necessary as an additional OS would be running in the background. I've also noticed that displaying the application in X11/Wayland this way seems to introduce an overhead if no GPU is shared with the container (which is negligible with the proper configuration): https://github.com/scottyhardy/docker-wine

i do not know much about docker images so i may not be of much help here but i think you should check out this project to see if it may give you a baseline idea https://github.com/scottyhardy/docker-wine

For those not using windows (like Linux or Mac), you can use docker + wine, and works great! =) (If you need help, let me know so I can explain with more details.)

This will not work out of the box. You will need to build and install something like https://github.com/neutrinolabs/pulseaudio-module-xrdp . I cannot help you with that, however.

There is a module for PulseAudio. There seems to be early support for PipeWire as well.

I've been following the process described at https://github.com/neutrinolabs/pulseaudio-module-xrdp to enable the pulseaudio module for xRDP. I am currently attempting to build the Pulseaudio modules as described at https://github.com/neutrinolabs/pulseaudio-module-xrdp/wiki/Build-on-Debian-or-Ubuntu, using the variant command

I have xrdp and it is working fine when I'm doing a remote session on my Windows 10 machine but I can't get the sound working. I did pulseaudio thing via this website: https://github.com/neutrinolabs/pulseaudio-module-xrdp/wiki/README but I'm having a problem when trying to build xrdp source / sink modules. It shows me this: