I had the same issues, the container was not able to find the device ( a RTL-SDR USB radio for reading 433mhz devices in Home Assistant) when using the device parameter.
However, adding the --device=$(readlink -f /dev/symlinkname) to the Extra Arguments were very unreliable. Sometimes the container could access the USB through the symlink and most of the times it could not.
I changed to the -e option and it worked flawlessly:
--device=$(readlink -e /dev/rtlsdr)
# Change "rtlsdr" to your symlink name
I also noticed the user scripts function "At first Array start only" was not working reliably either.
Instead I added it to the /boot/config/go file:
#Add udev rules
cp /boot/config/rules.d/99-usb-rules.rules /etc/udev/rules.d/99-usb-rules.rules
chmod 744 /etc/udev/rules.d/99-usb-rules.rules
udevadm trigger --attr-match=subsystem=usb
This is what I put into the /boot/config/rules.d/99-usb-rules.rules file.
The name of this file is not important just that the filename begins with a large number, in this case 99, because the udev rules gets executed in order.
So depending on what udev rules you have on your system you can name it 99-yourname.rules.
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="2838", MODE="0666", SYMLINK+="rtlsdr"
# Change "rtlsdr" to your preferred symlink name
Now it survive reboots, it is working reliably every time and I do not have to unplug/replug it to get it to recognize the device.