I appreciate your message and I will look into testing and running freeswitch on lxd once I get an environment setup for it.
Currently I still have freeswitch in lxc on proxmox and was trying to exhaust all possibilities of getting freeswitch running unprivileged without impacting freeswitch’s IOSchedulingClass, IOSchedulingPriority, and CPUSchedulingPolicy settings.
I was searching and found your posts from last year where you posted you were able to successfully run freeswitch unprivileged. Granting access to kernel capabilities and keep default ones - #2 by stgraber
On proxmox I edited /etc/pve/lxc/<container_id>.conf and added what you suggested before in the above link:
lxc.prlimit.nice: -20
lxc.prlimit.nofile: 1024:999999
Unfortunately, after rebooting the lxc I see same errors in freeswitch lxc container whenever I try to
systemctl start freeswitch
or
systemctl restart freeswitch
However, in the current iteration of configuring a freeswitch lxc container I am able to run
freeswitch -c
which does successfully get freeswitch running and connects me to the console. In the proxmox host console running top I do see freeswitch running with nice -10.