Segmentation fault on Docker+Proxmox

Hi everyone,

I am using VirtualHere in a Docker Container, but I keep getting segmentation faults.
The container starts up briefly but will shut down after a second.
I tried to correct the permissions for the folder - changing permissions leads to a different error, so I don't think thats it.
I removed the container multiple times to start with a fresh image, but it makes no difference.

The LXC Container in which Docker is placed, runs with nesting=1 and keyctl=1.

Your system architecture was identified as x86_64. The x86_64 version of the virtualhere-client will be used.
*** Listing all usb-devices. Use this list to adjust AllowedDevices in config.ini ...
Bus 001 Device 001: ID 1d6b:0002 Linux 6.8.12-2-pve ehci_hcd EHCI Host Controller
Bus 001 Device 002: ID 8087:8008  
Bus 002 Device 001: ID 1d6b:0002 Linux 6.8.12-2-pve ehci_hcd EHCI Host Controller
Bus 002 Device 002: ID 8087:8000  
Bus 003 Device 001: ID 1d6b:0002 Linux 6.8.12-2-pve xhci-hcd xHCI Host Controller
Bus 003 Device 002: ID 046d:c31c Logitech USB Keyboard
Bus 003 Device 003: ID 04f9:0182  
Bus 004 Device 001: ID 1d6b:0003 Linux 6.8.12-2-pve xhci-hcd xHCI Host Controller
*** Deleting previous bus_usb_*-files from data directory ...
*** Checking for new version of VirtualHere ...
--2025-02-27 15:48:17--  https://www.virtualhere.com/sites/default/files/usbserver/vhusbdx86_64
Resolving www.virtualhere.com (www.virtualhere.com)... 143.198.145.150, 2604:a880:4:1d0::63d:5000
Connecting to www.virtualhere.com (www.virtualhere.com)|143.198.145.150|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 439620 (429K) [application/octet-stream]
Saving to: 'vhusbdx86_64'

    0K .......... .......... .......... .......... .......... 11%  146K 3s
   50K .......... .......... .......... .......... .......... 23% 1.69M 1s
  100K .......... .......... .......... .......... .......... 34%  347K 1s
  150K .......... .......... .......... .......... .......... 46% 1.74M 1s
  200K .......... .......... .......... .......... .......... 58%  344K 0s
  250K .......... .......... .......... .......... .......... 69% 33.4M 0s
  300K .......... .......... .......... .......... .......... 81% 42.4M 0s
  350K .......... .......... .......... .......... .......... 93% 2.23M 0s
  400K .......... .......... .........                       100% 26.1M=0.7s

2025-02-27 15:48:18 (600 KB/s) - 'vhusbdx86_64' saved [439620/439620]

VirtualHere 4.7.5 caught signal 11 (Segmentation fault) and must exit. Sorry for the inconvenience, please contact mail@virtualhere for help
Segmentation fault (core dumped)

I really can't get my head around this, so any help is much appreciated.

#3

You are linking to the client, I have the Server. 

Proxmox hosts an LXC Container with Docker in it. Dockers Containers are not LXC as I am aware and the Setup did work before on Fedora with Docker on the host. But a normal Container on Proxmox is by default LXC or a full-blown VM which I am NOT going to use, because it would be the only container in the extra vm.

My Server has an i5-4690k which is decent in single core but not multi-core so another vm would hurt my performance big way.

Though I saw that it may be possible to use something like runq to create it under the same docker instance?

Any help is appreciated :)

Greetings

#4

Sorry misread, anyway virtualhere server is not supported In docker. It must run in a real OS on a real machine, not a VM or container

#5

Saying as it is not supported means...not officially? As it did work in Docker for...years...Just now that another LXC is wrapped around it, it leads to the segmentation fault. 

#6

it was never officially supported. The server has always been supported to run on real os/hardware. 

#7

As I am using Proxmox and following standard practice, Its said to do as little modification to the host (regarding programm installs). 

So this would mean I would have to use a vm - so I think I am going to switch to usbip as far as its possible.

 

Thank you for your help :)