linuxserver / docker-bazarr

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Bazarr crashing when I load /series on a container with base image Alpine 3.15

germancasares opened this issue · comments

linuxserver.io

Crossposting from: morpheus65535/bazarr#1860

But the current version of the base image used for docker-bazarr (Alpine 3.15) contains an older library of sqlite-libs that it is making it crash on my Raspberry Pi 3b. I tested this and it was working fine on a Raspberry Pi 4b.


Expected Behavior

Bazarr UI working correctly.

Current Behavior

Bazarr UI crashes with Segmentation Fault.

Steps to Reproduce

  1. Setup Bazarr with Sonarr
  2. Go to BAZARR_URL:6767/series
  3. The page will eventually crash with "Cannot Initialize Bazarr"

Environment

OS: Raspbery Pi OS
CPU architecture: arm64
Hardware: Raspberry Pi 3b (It does not happen on Raspberry Pi 4b)
How docker service was installed: lscr.io/linuxserver/bazarr:latest

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

  bazarr:
    image: lscr.io/linuxserver/bazarr:latest
    container_name: bazarr
    depends_on:
      - sonarr
      - radarr
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/Vancouver
    volumes:
      - /home/USER/Bazarr:/config
      - /media/USER/Movies:/movies
      - /media/USER/TV Shows:/tv
    ports:
      - 6767:6767
    restart: unless-stopped

Docker logs

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

Please provide logs

Hi!

Sorry about that, I though I added them to the initial ticket over at Bazarr.

https://pastebin.com/G0PwCp93

These logs are from when I tried to run Bazarr with GDB, so it includes at the end the Segmentation Fault.

I'm facing the same issue, is there any workaround until its fixed? I spent ages trying to debug this, not knowing you could run bazarr with GDB, without it only Bazarr exited. message pops up

@RouNNdeL There is! You can go to where I initially posted it: morpheus65535/bazarr#1860

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.