github-mirrors/docker-sonarr
1
0
Fork 0
mirror of https://github.com/linuxserver/docker-sonarr.git synced 2025-06-27 17:00:33 -04:00
Code Issues Projects Releases Packages Wiki Activity

Bot Updating Templated Files

Browse source
This commit is contained in:
LinuxServer-CI 2025-05-02 00:49:25 +00:00
parent 6d4ca179a2
commit 37f96655af
No known key found for this signature in database
1 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

18
README.md
View file

@ -70,6 +70,15 @@ This image provides various versions that are available via tags. Please read th
Access the webui at `<your-ip>:8989`, for more information check out [Sonarr](https://sonarr.tv/).
### Media folders
We have set `/tv` 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 don't understand, or don't want hardlinks/atomic moves.
>[!TIP]
>The folks over at servarr.com wrote a good [write-up](https://wiki.servarr.com/docker-guide#consistent-and-well-planned-paths) on how to get started with this.
## Read-Only Operation
This image can be run with a read-only container filesystem. For details please [read the docs](https://docs.linuxserver.io/misc/read-only/).
@ -78,15 +87,6 @@ This image can be run with a read-only container filesystem. For details please
This image can be run with a non-root user. For details please [read the docs](https://docs.linuxserver.io/misc/non-root/).
### 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 don't understand, or don't want hardlinks/atomic moves.
>[!TIP]
>The folks over at servarr.com wrote a good [write-up](https://wiki.servarr.com/docker-guide#consistent-and-well-planned-paths) 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.