diff --git a/images/docker-lidarr/index.html b/images/docker-lidarr/index.html index 3aa2297e20..f4fa099c32 100644 --- a/images/docker-lidarr/index.html +++ b/images/docker-lidarr/index.html @@ -1,4 +1,4 @@ - lidarr - LinuxServer.io
Skip to content

linuxserver/lidarr

Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build LSIO CI

Lidarr is a music collection manager for Usenet and BitTorrent users. It can monitor multiple RSS feeds for new tracks from your favorite artists and will grab, sort and rename them. It can also be configured to automatically upgrade the quality of files already downloaded when a better quality format becomes available.

lidarr

Supported Architectures

We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling lscr.io/linuxserver/lidarr:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

Architecture Available Tag
x86-64 ✅ amd64-<version tag>
arm64 ✅ arm64v8-<version tag>
armhf ❌

Version Tags

This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.

Tag Available Description
latest ✅ Stable Lidarr releases.
develop ✅ Develop Lidarr Releases.
nightly ✅ Nightly Lidarr Releases.

Application Setup

Access the webui at <your-ip>:8686, for more information check out Lidarr.

Special Note: Following our current folder structure will result in an inability to hardlink from your downloads to your Music folder because they are on seperate volumes. To support hardlinking, simply ensure that the Music and downloads data are on a single volume. For example, if you have /mnt/storage/Music and /mnt/storage/downloads/completed/Music, you would want something like /mnt/storage:/media for your volume. Then you can hardlink from /media/downloads/completed to /media/Music.

Another item to keep in mind, is that within lidarr itself, you should then map your download client folder to your lidarr folder: Settings -> Download Client -> advanced -> remote path mappings. I input the host of my download client (matches the download client defined) remote path is /downloads/Music (relative to the internal container path) and local path is /media/downloads/completed/Music, assuming you have folders to seperate your downloaded data types.

Media folders

We have set /music and /downloads as optional paths, this is because it is the easiest way to get started. While easy to use, it has some drawbacks. Mainly losing the ability to hardlink (TL;DR a way for a file to exist in multiple places on the same file system while only consuming one file worth of space), or atomic move (TL;DR instant file moves, rather than copy+delete) files while processing content.

Use the optional paths if you dont understand, or dont want hardlinks/atomic moves.

The folks over at servarr.com wrote a good write-up on how to get started with this.

Usage

To help you get started creating a container from this image you can either use docker-compose or the docker cli.

---
+ lidarr - LinuxServer.io       
 
 
  
 
  
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
   
linuxserver/lidarr
 
Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build LSIO CI
 
Lidarr is a music collection manager for Usenet and BitTorrent users. It can monitor multiple RSS feeds for new tracks from your favorite artists and will grab, sort and rename them. It can also be configured to automatically upgrade the quality of files already downloaded when a better quality format becomes available.
 
lidarr
 
Supported Architectures
 
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
 
Simply pulling lscr.io/linuxserver/lidarr:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
 
The architectures supported by this image are:
 
  
 Architecture Available Tag 
   
 x86-64 ✅ amd64-<version tag> 
 
 arm64 ✅ arm64v8-<version tag> 
 
 armhf ❌  
  
 
Version Tags
 
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
 
  
 Tag Available Description 
   
 latest ✅ Stable Lidarr releases. 
 
 develop ✅ Develop Lidarr Releases. 
 
 nightly ✅ Nightly Lidarr Releases. 
  
 
Application Setup
 
Access the webui at <your-ip>:8686, for more information check out Lidarr.
 
Special Note: Following our current folder structure will result in an inability to hardlink from your downloads to your Music folder because they are on seperate volumes. To support hardlinking, simply ensure that the Music and downloads data are on a single volume. For example, if you have /mnt/storage/Music and /mnt/storage/downloads/completed/Music, you would want something like /mnt/storage:/media for your volume. Then you can hardlink from /media/downloads/completed to /media/Music.
 
Another item to keep in mind, is that within lidarr itself, you should then map your download client folder to your lidarr folder: Settings -> Download Client -> advanced -> remote path mappings. I input the host of my download client (matches the download client defined) remote path is /downloads/Music (relative to the internal container path) and local path is /media/downloads/completed/Music, assuming you have folders to seperate your downloaded data types.
 
Media folders
 
We have set /music and /downloads as optional paths, this is because it is the easiest way to get started. While easy to use, it has some drawbacks. Mainly losing the ability to hardlink (TL;DR a way for a file to exist in multiple places on the same file system while only consuming one file worth of space), or atomic move (TL;DR instant file moves, rather than copy+delete) files while processing content.
 
Use the optional paths if you dont understand, or dont want hardlinks/atomic moves.
 
The folks over at servarr.com wrote a good write-up on how to get started with this.
 
Usage
 
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
  
---
 version: "2.1"
 services:
   lidarr:
@@ -53,4 +53,4 @@
   --pull \
   -t lscr.io/linuxserver/lidarr:latest .
 
 
The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static
 
docker run --rm --privileged multiarch/qemu-user-static:register --reset
-
 
Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.
 
Versions
 
     
  • 06.06.23: - Rebase master to Alpine 3.18, deprecate armhf as per https://www.linuxserver.io/armhf.
    •  
  • 17.01.23: - Rebase master branch to Alpine 3.17, migrate to s6v3.
    •  
  • 06.06.22: - Rebase master branch to Alpine 3.15.
    •  
  • 06.05.22: - Rebase master branch to Focal.
    •  
  • 06.05.22: - Rebase develop branch to Alpine.
    •  
  • 04.02.22: - Rebase nightly branch to Alpine, deprecate nightly-alpine branch.
    •  
  • 30.12.21: - Add nightly-alpine branch.
    •  
  • 01.08.21: - Add libchromaprint-tools.
    •  
  • 11.07.21: - Make the paths clearer to the user.
    •  
  • 18.04.21: - Switch latest tag to net core.
    •  
  • 25.01.21: - Publish develop tag.
    •  
  • 20.01.21: - Deprecate UMASK_SET in favor of UMASK in baseimage, see above for more information.
    •  
  • 18.04.20: - Removed /downloads and /music volumes from Dockerfiles.
    •  
  • 05.04.20: - Move app to /app.
    •  
  • 01.08.19: - Rebase to Linuxserver LTS mono version.
    •  
  • 13.06.19: - Add env variable for setting umask.
    •  
  • 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
    •  
  • 08.03.19: - Rebase to Bionic, use proposed endpoint for libchromaprint.
    •  
  • 26.01.19: - Add pipeline logic and multi arch.
    •  
  • 22.04.18: - Switch to beta builds.
    •  
  • 17.03.18: - Add ENV XDG_CONFIG_HOME="/config/xdg" to Dockerfile for signalr fix.
    •  
  • 27.02.18: - Use json to query for new version.
    •  
  • 23.02.18: - Initial Release.
    •  
 
 
  Last update: October 7, 2023 
 Created: February 7, 2019  
 
 
 
  
  
 
 
 
      
\ No newline at end of file
+

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

Versions

  • 06.06.23: - Rebase master to Alpine 3.18, deprecate armhf as per https://www.linuxserver.io/armhf.
  • 17.01.23: - Rebase master branch to Alpine 3.17, migrate to s6v3.
  • 06.06.22: - Rebase master branch to Alpine 3.15.
  • 06.05.22: - Rebase master branch to Focal.
  • 06.05.22: - Rebase develop branch to Alpine.
  • 04.02.22: - Rebase nightly branch to Alpine, deprecate nightly-alpine branch.
  • 30.12.21: - Add nightly-alpine branch.
  • 01.08.21: - Add libchromaprint-tools.
  • 11.07.21: - Make the paths clearer to the user.
  • 18.04.21: - Switch latest tag to net core.
  • 25.01.21: - Publish develop tag.
  • 20.01.21: - Deprecate UMASK_SET in favor of UMASK in baseimage, see above for more information.
  • 18.04.20: - Removed /downloads and /music volumes from Dockerfiles.
  • 05.04.20: - Move app to /app.
  • 01.08.19: - Rebase to Linuxserver LTS mono version.
  • 13.06.19: - Add env variable for setting umask.
  • 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
  • 08.03.19: - Rebase to Bionic, use proposed endpoint for libchromaprint.
  • 26.01.19: - Add pipeline logic and multi arch.
  • 22.04.18: - Switch to beta builds.
  • 17.03.18: - Add ENV XDG_CONFIG_HOME="/config/xdg" to Dockerfile for signalr fix.
  • 27.02.18: - Use json to query for new version.
  • 23.02.18: - Initial Release.
Last update: November 22, 2023
Created: February 7, 2019
\ No newline at end of file diff --git a/sitemap.xml.gz b/sitemap.xml.gz index fd32761792..9b1e6866be 100644 Binary files a/sitemap.xml.gz and b/sitemap.xml.gz differ