linuxserver/docker-bazarr

Cannot start bazarr on docker after upgrade to v0.9.1

Closed this issue · 5 comments

linuxserver.io


Expected Behavior

Normal process startup listening on port 6767.

Current Behavior

I am trying to start the Docker container once I pulled the latest bazarr docker image from linuxserver.io. Process is failing with the following error:

Current thread 0x75f79390 (most recent call first):                                                                                                                               
<no Python frame>                                                                                                                                                                 
Fatal Python error: pyinit_main: can't initialize time                                                                                                                            
Python runtime state: core initialized                                                                                                                                            
PermissionError: [Errno 1] Operation not permitted   

Steps to Reproduce

On NAS QNAP TS-231P2, Pull latest Docker image from linuxserver.io - version 0.9.1 and try to start it.

Environment

OS:
CPU architecture: arm32
How docker service was installed:
via Container Station from Docker Hub using latest linuxserver.io image.
Bazarr: v 0.9.1
Docker 20.10.3 on linux, arm
QNAP TS-231P2
OS: Arm 32bit

Command used to create docker container (run/create/compose/screenshot)

Screenshot 2021-02-22 at 4 07 48

Docker logs

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

Your log probably mentions this link: https://docs.linuxserver.io/faq#libseccomp

@Roxedus ,
thanks for sharing that but QNAP is using some proprietary Linux base and I these Debian packages cannot be installed on it:

[~] # dpkg -i libseccomp2_2.4.4-1~bpo10+1_armhf.deb
-sh: dpkg: command not found 

Any other workaround here?

@eevlogiev you would need to ask QNAP about getting this package updated due to the nature of the OS.

The issue was fixed after upgrading QNAP Container Station to latest version 2.3.4.1698.

Thanks.