It looks like the container can see the reader, but the OS is blocking access because of permission rules on the device.
On ZimaOS the FTDI device appears as
crw-rw---- root dialout
which means only root and the dialout group can open it.
Inside your container you are running as PUID 1000 and PGID 1000. That user does not belong to the dialout group, so even with privileged mode enabled the kernel still applies the host permissions. This is why Oscam shows
errno 13 permission denied.
I suggest trying one of these approaches
- Run the container as root inside the container.
Oscam does not require root, but this is the simplest way to match the device permissions. - Add the container user to the dialout group.
ZimaOS does not automatically map supplementary groups into containers, so you may need to override the user mapping or switch to a root user. Many LinuxServer images allow
PUID 0 and PGID 0
which makes access immediate. - Confirm the host sees the reader correctly.
If lsusb shows the FTDI chip and ttyUSB0 is created, then the problem is only permission mapping and not hardware.
I think option 1 is the fastest fix on ZimaOS.
Change your compose to run Oscam as root (PUID 0 PGID 0) and keep privileged mode on. That should allow Oscam to open ttyUSB0 without error.
If it still fails, then the issue is not permissions but the driver binding, and we can explore forcing the ftdi_sio driver or checking udev rules.