Docker Guide - Revision history

Bakerboy448 at 20:25, 12 July 2021

2021-07-12T20:25:40Z

Bakerboy448: Replaced content with "[https://wikijs.servarr.com/docker-guide Moved to the new wiki]"

2021-06-20T06:36:04Z

Replaced content with "[https://wikijs.servarr.com/docker-guide Moved to the new wiki]"

Show changes

TRaSH: /* Consistent and well planned paths */

2021-05-08T21:17:36Z

Consistent and well planned paths

Bakerboy448: /* Interesting docker images */

2021-05-08T14:35:37Z

Interesting docker images

Bakerboy448: Drop LSIO and fix radarr discord

2021-05-08T14:11:00Z

Drop LSIO and fix radarr discord

Bakerboy448: /* Consistent and well planned paths */

2021-05-05T18:13:16Z

Consistent and well planned paths

Bakerboy448 at 14:37, 23 March 2021

2021-03-23T14:37:50Z

Bakerboy448: /* Get docker-compose */ add trash link

2021-01-18T19:54:53Z

Get docker-compose: add trash link

Bakerboy448: trash to TRaSH

2020-12-06T19:50:18Z

trash to TRaSH

Bakerboy448: add link to trash's guide

2020-12-06T19:43:19Z

add link to trash's guide

← Older revision		Revision as of 20:25, 12 July 2021
Line 1:		Line 1:
−	[https://~~wikijs~~.servarr.com/docker-guide Moved to the new wiki]	+	[https://wiki.servarr.com/docker-guide Moved to the new wiki]

@@ Line 37: / Line 37: @@
 ==== Consistent and well planned paths ====
-'''Note: Many folks find [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ TRaSH's Hardlink Tutorial] helpful and easier to understand than this guide. This guide is more conceptual in nature while TRaSH's tutorial walks you through the process.'''
+'''Note: Many folks find [https://trash-guides.info/hardlinks TRaSH's Hardlink Tutorial] helpful and easier to understand than this guide. This guide is more conceptual in nature while TRaSH's tutorial walks you through the process.'''
 The easiest and most important detail is to create unified path definitions across all the containers.

@@ Line 298: / Line 298: @@
 * [https://hub.docker.com/r/rasmunk/sshfs rasmunk/sshfs] let you create an sshfs volume, ''perfect'' for a seedbox setup using a remote mount instead of sync. Better documentation, including examples can be found at the github [https://github.com/rasmunk/docker-volume-sshfs rasmunk/docker-volume-sshfs] repository. This is a more recently maintained fork of [https://hub.docker.com/p/vieux/sshfs vieux/sshfs].
-* [https://hub.docker.com/u/hotio hotio’s] [https://hub.docker.com/r/hotio/sonarr sonarr], [https://hub.docker.com/r/hotio/radarr radarr] and [https://hub.docker.com/r/hotio/lidarr lidarr] images let you run the built in version ''or'' specify an alternative via environment variable. The documentation and Dockerfile also don’t make any poor path suggestions.
+* [https://hub.docker.com/u/hotio hotio’s] [https://hub.docker.com/r/hotio/sonarr sonarr], [https://hub.docker.com/r/hotio/radarr radarr] and [https://hub.docker.com/r/hotio/lidarr lidarr] images let you run the built in version ''or'' specify an alternative via environment variable. The documentation and Dockerfile also don’t make any poor path suggestions.  Images are automatically updated 2x in 1 hour if upstream changes are found. Hotio also builds our Pull Requests which may be useful for testing.
 * [https://hub.docker.com/u/hotio hotio’s] [https://hub.docker.com/r/hotio/ombi ombi], [https://hub.docker.com/r/hotio/jackett jackett], [https://hub.docker.com/r/hotio/nzbhydra2 nzbhydra2] and [https://hub.docker.com/r/hotio/bazarr bazarr] are useful too, but don’t really require any special permissions or paths.
 * [https://hub.docker.com/u/hotio hotio’s] [https://hub.docker.com/r/hotio/unpackerr unpackerr] is useful for packed torrent extraction across a variety of torrent clients where unpacking is lacking or missing entirely.
 * [https://hub.docker.com/u/binhex binhex’s] [https://hub.docker.com/r/binhex/arch-qbittorrentvpn/ qbittorrent], [https://hub.docker.com/r/binhex/arch-delugevpn/ deluge] and [https://hub.docker.com/r/binhex/arch-rtorrentvpn/ rtorrent] are popular torrent clients with built in VPN support. For usenet, there is [https://hub.docker.com/r/binhex/arch-sabnzbd/ sabnzbd] and [https://hub.docker.com/r/binhex/arch-nzbget/ nzbget].
 * [https://hub.docker.com/u/binhex binhex’s] [https://hub.docker.com/r/binhex/arch-sonarr/ sonarr], [https://hub.docker.com/r/binhex/arch-radarr/ radarr] and [https://hub.docker.com/r/binhex/arch-lidarr/ lidarr] images suggest default paths that don’t allow for hard linking, instead follow the process described above and pass in a single volume.
-* [https://hub.docker.com/u/linuxserver linuxserver.io’s] images also suggest default paths that don’t allow for hard linking, instead follow the process described above and pass in a single volume. But they do have images for a ''lot'' of software and they’re well maintained.
+* [https://hub.docker.com/u/linuxserver linuxserver.io’s] images have images for a ''lot'' of software and they’re well maintained.
 * [https://hub.docker.com/r/pyouroboros/ouroboros pyouroboros/ouroboros] or [https://hub.docker.com/r/containrrr/watchtower containrrr/watchtower] automatically update your running Docker containers to the latest available image. These are not recommended if you use Docker Compose.

@@ Line 323: / Line 323: @@
 If you find yourself setting a UMASK of <code>000</code> (which is 777 for folders and 666 for files), you’re ''also'' doing something wrong. It leaves your files and folders read/write to ''everyone'', which is poor Linux hygiene.
 ==== Getting Help ====
-Need some help? For real time, chat style support try the [https://discord.gg/xyRwnyB Sonarr] or [https://discord.gg/SRBnFmX Radarr] Discord servers. If you prefer forum style support, make a post in [http://reddit.com/r/sonarr /r/sonarr] or [http://reddit.com/r/radarr /r/radarr].
+Need some help? For real time, chat style support try the [https://discord.gg/xyRwnyB Sonarr] or [https://radarr.video/discord Radarr] Discord servers. If you prefer forum style support, make a post in [http://reddit.com/r/sonarr /r/sonarr] or [http://reddit.com/r/radarr /r/radarr].

← Older revision		Revision as of 18:13, 5 May 2021
Line 36:		Line 36:

	==== Consistent and well planned paths ====		==== Consistent and well planned paths ====
		+
		+	'''Note: Many folks find [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ TRaSH's Hardlink Tutorial] helpful and easier to understand than this guide. This guide is more conceptual in nature while TRaSH's tutorial walks you through the process.'''

	The easiest and most important detail is to create unified path definitions across all the containers.		The easiest and most important detail is to create unified path definitions across all the containers.

@@ Line 3: / Line 3: @@
 '''TL; DR''': An [https://www.lexico.com/en/definition/eponymous eponymous] user per daemon and a shared group with a umask of <code>002</code>. Consistent path definitions between ''all'' containers that maintains the folder structure. Using one volume for Sonarr, Radarr and Lidarr so the download folder and library folder are on the same file system which makes hard links and instant moves possible. And most of all, ignore ''most'' of the Docker image’s path documentation!
-'''Note: Many folks find [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ TRaSH's guide] helpful in addition to this guide.'''
+'''Note: Many folks find [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ TRaSH's Hardlink Tutorial] helpful and easier to understand than this guide. This guide is more conceptual in nature while TRaSH's tutorial walks you through the process.'''
 ==== Introduction ====

@@ Line 250: / Line 250: @@
 <pre>docker run --rm -v /var/run/docker.sock:/var/run/docker.sock assaflavie/runlike CONTAINER_NAME</pre>
 ===== Get docker-compose =====
 Getting a <code>docker-compose.yml</code> from running instances is possible with [https://hub.docker.com/r/red5d/docker-autocompose red5d/docker-autocompose], in case you’ve already started your containers with <code>docker run</code> or <code>docker create</code> and want to change to <code>docker-compose</code> style. It is also great for sharing your settings with others, since it doesn’t matter what management software you’re using. The last argument(s) are your container names and you can pass in as many as needed at the same time. The first container name is required, more are optional. You can see container names in the '''NAMES''' column of `docker ps`, they're usually set by you or might be generated based on the image like <code>binhex-qbittorrent</code>. It is ''not'' the image name, like <code>binhex/arch-qbittorrentvpn</code>.

← Older revision		Revision as of 19:43, 6 December 2020
Line 2:		Line 2:

	'''TL; DR''': An [https://www.lexico.com/en/definition/eponymous eponymous] user per daemon and a shared group with a umask of <code>002</code>. Consistent path definitions between ''all'' containers that maintains the folder structure. Using one volume for Sonarr, Radarr and Lidarr so the download folder and library folder are on the same file system which makes hard links and instant moves possible. And most of all, ignore ''most'' of the Docker image’s path documentation!		'''TL; DR''': An [https://www.lexico.com/en/definition/eponymous eponymous] user per daemon and a shared group with a umask of <code>002</code>. Consistent path definitions between ''all'' containers that maintains the folder structure. Using one volume for Sonarr, Radarr and Lidarr so the download folder and library folder are on the same file system which makes hard links and instant moves possible. And most of all, ignore ''most'' of the Docker image’s path documentation!
		+
		+	'''Note: Many folks find [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ Trash's guide] helpful in addition to this guide.'''

	==== Introduction ====		==== Introduction ====