No description
Find a file
2018-09-23 23:26:38 -07:00
.github Initial Commit 2018-09-13 14:07:48 +01:00
root/etc tidying and using g++ and gcc over build-base 2018-09-15 10:01:35 +01:00
.dockerignore Initial Commit 2018-09-13 14:07:48 +01:00
.gitattributes Initial Commit 2018-09-13 14:07:48 +01:00
.gitignore Initial Commit 2018-09-13 14:07:48 +01:00
Dockerfile adding the development branch and tag to the project to build off of the latest commit of the bazarr development branch 2018-09-23 22:28:45 -07:00
Dockerfile.aarch64 adding the development branch and tag to the project to build off of the latest commit of the bazarr development branch 2018-09-23 22:28:45 -07:00
Dockerfile.armhf adding the development branch and tag to the project to build off of the latest commit of the bazarr development branch 2018-09-23 22:28:45 -07:00
Jenkinsfile need to use the array endpoint not the latest release to index the releases 2018-09-23 23:26:38 -07:00
readme-vars.yml adding the development branch and tag to the project to build off of the latest commit of the bazarr development branch 2018-09-23 22:28:45 -07:00
README.md adding the development branch and tag to the project to build off of the latest commit of the bazarr development branch 2018-09-23 22:28:45 -07:00

linuxserver.io

The LinuxServer.io team brings you another container release featuring :-

  • regular and timely application updates
  • easy user mappings (PGID, PUID)
  • custom base image with s6 overlay
  • weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
  • regular security updates

Find us at:

  • Discord - realtime support / chat with the community and the team.
  • IRC - on freenode at #linuxserver.io. Our primary support channel is Discord.
  • Blog - all the things you can do with our containers including How-To guides, opinions and much more!
  • Podcast - on hiatus. Coming back soon (late 2018).

PSA: Changes are happening

From August 2018 onwards, Linuxserver are in the midst of switching to a new CI platform which will enable us to build and release multiple architectures under a single repo. To this end, existing images for arm64 and armhf builds are being deprecated. They are replaced by a manifest file in each container which automatically pulls the correct image for your architecture. You'll also be able to pull based on a specific architecture tag.

TLDR: Multi-arch support is changing from multiple repos to one repo per container image.

linuxserver/bazarr

Docker Pulls Docker Stars

Bazarr is a companion application to Sonarr and Radarr. It can manage and download subtitles based on your requirements. You define your preferences by TV show or movie and Bazarr takes care of everything for you.

bazarr

Supported Architectures

Our images support multiple architectures such as X86-64, arm64 and armhf. We utilise the docker manifest for multi-platform awareness. More information is available from docker here.

The architectures supported by this image are:

Architecture Tag
X86-64 amd64-latest
arm64 arm64v8-latest
armhf arm32v6-latest

Usage

Here are some example snippets to help you get started creating a container.

docker

docker create \
  --name=bazarr \
  -e PUID=1001 \
  -e PGID=1001 \
  -e TZ=Europe/London \
  -p 6767:6767 \
  -v </path/to/bazarr/config>:/config \
  -v </path/to/movies>:/movies \
  -v </path/to/tv:/tv \
  linuxserver/bazarr

You can choose between ,using tags, various branch versions of bazarr, no tag is required to remain on the main branch. Add one of the tags, if required, to the linuxserver/bazarr line of the run/create command in the following format, linuxserver/bazarr:development The development tag will be the latest commit in the development branch of bazarr. HOWEVER , USE THE DEVELOPMENT BRANCH AT YOUR OWN PERIL !!!!!!!!!

docker-compose

Compatible with docker-compose v2 schemas.

---
version: "2"
services:
  bazarr:
    image: linuxserver/bazarr
    container_name: bazarr
    environment:
      - PUID=1001
      - PGID=1001
      - TZ=Europe/London
    volumes:
      - </path/to/bazarr/config>:/config
      - </path/to/movies>:/movies
      - </path/to/tv:/tv
    ports:
      - 6767:6767
    mem_limit: 4096m
    restart: unless-stopped

Parameters

Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.

Parameter Function
-p 6767 Allows HTTP access to the internal webserver.
-e PUID=1001 for UserID - see below for explanation
-e PGID=1001 for GroupID - see below for explanation
-e TZ=Europe/London Specify a timezone to use EG Europe/London
-v /config Bazarr data
-v /movies Location of your movies
-v /tv Location of your TV Shows

User / Group Identifiers

When using volumes (-v flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=1001 and PGID=1001, to find yours use id user as below:

  $ id username
    uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)

 

Application Setup

  • Once running the URL will be http://<host-ip>:6767.
  • You must complete all the setup parameters in the webui before you can save the config.

Support Info

  • Shell access whilst the container is running: docker exec -it bazarr /bin/bash
  • To monitor the logs of the container in realtime: docker logs -f bazarr
  • container version number
    • docker inspect -f '{{ index .Config.Labels "build_version" }}' bazarr
  • image version number
    • docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/bazarr

Versions

  • 11.09.18: - Initial release.