Title: Docker - TRaSH Guides

URL Source: https://trash-guides.info/File-and-Folder-Structure/How-to-set-up/Docker/

Markdown Content:
[](https://github.com/TRaSH-Guides/Guides/edit/master/docs/File-and-Folder-Structure/How-to-set-up/Docker.md "Edit this page")[](https://github.com/TRaSH-Guides/Guides/raw/master/docs/File-and-Folder-Structure/How-to-set-up/Docker.md "View source of this page")

Tip

If you're new to Docker containers and want an easy setup, we suggest taking a look at [DockSTARTer](https://dockstarter.com/). We've also created a short guide [HERE](https://trash-guides.info/File-and-Folder-Structure/How-to-set-up/Dockstarter/) where we explain the settings for the most used applications.

The main goal of DockSTARTer is to make it quick and easy to get up and running with Docker. You may choose to rely on DockSTARTer for various changes to your Docker system or use DockSTARTer as a stepping stone and learn to do more advanced configurations.

_DockSTARTer was actually my first step into the world of Docker containers._

Note

I'm not going to explain how to get Docker installed and running, we will only explain which folder structure we recommend.

The paths mentioned below refer to internal paths (or `Container Path`) for the containers!

External paths (or `Host Path`) depend on where you mounted your share or your drives.

For example `/<path_to_data>/data`, or even `/data`.

Folder Structure[](https://trash-guides.info/File-and-Folder-Structure/How-to-set-up/Docker/#folder-structure "Permanent link")
-------------------------------------------------------------------------------------------------------------------------------

Warning

It doesn't really matter which path you use for your media and appdata,

the only thing you should avoid is `/home`.

Because user folders in `/home` are expected to have some restrictive permissions.

It just could end up creating a permissions mess, so it's better to just avoid entirely.

For this example we're going to make use of a share called `data`.

The `data` folder has sub-folders for `torrents` and `usenet` and each of these have sub-folders for `tv`, `movie`, `books` and `music` downloads to keep things neat. The `media` folder has nicely named `TV`, `Movies`, `Books` and `Music` sub-folders, this is your library and what you’d pass to Plex, Emby or JellyFin.

_In this examples I'm using lower case on all folder on purpose, being Linux is case sensitive._

### Bad path suggestion[](https://trash-guides.info/File-and-Folder-Structure/How-to-set-up/Docker/#bad-path-suggestion "Permanent link")

The default path setup suggested by some Docker developers that encourages people to use mounts like `/movies`, `/tv`, `/books` or `/downloads` is very suboptimal and it makes them look like two or three file systems, even if they aren’t (_Because of how Docker’s volumes work_). It is the easiest way to get started. While easy to use, it has a major drawback. Mainly losing the ability to hardlink or instant move, resulting in a slower and more I/O intensive copy + delete is used.

### Breakdown of the Folder Structure[](https://trash-guides.info/File-and-Folder-Structure/How-to-set-up/Docker/#breakdown-of-the-folder-structure "Permanent link")

#### Torrent clients[](https://trash-guides.info/File-and-Folder-Structure/How-to-set-up/Docker/#torrent-clients "Permanent link")

qBittorrent, Deluge, ruTorrent

The reason why we use `/data/torrents` for the torrent client is because it only needs access to the torrent files. In the torrent software settings, you’ll need to reconfigure paths and you can sort into sub-folders like `/data/torrents/{tv|movies|music}`.

`Container Path:` =>`/data/torrents/`

`Host Path:` =>`/<path_to_data>/data/torrents/`

#### Usenet clients[](https://trash-guides.info/File-and-Folder-Structure/How-to-set-up/Docker/#usenet-clients "Permanent link")

NZBGet or SABnzbd

The reason why we use `/data/usenet` for the Usenet client is because it only needs access to the Usenet files. In the Usenet software settings, you’ll need to reconfigure paths and you can sort into sub-folders like `/data/usenet/complete/{tv|movies|music}`.

`Container Path:` =>`/data/usenet/`

`Host Path:` =>`/<path_to_data>/data/usenet/`

#### The Starr Apps[](https://trash-guides.info/File-and-Folder-Structure/How-to-set-up/Docker/#the-starr-apps "Permanent link")

Sonarr, Radarr, Readarr and Lidarr

Sonarr, Radarr, Readarr and Lidarr gets access to everything using `/data` because the download folder(s) and media folder will look like and be one file system. Hardlinks will work and moves will be atomic, instead of copy + delete.

`Container Path:` =>`/data`

`Host Path:` =>`/<path_to_data>/data/`

#### Media Server[](https://trash-guides.info/File-and-Folder-Structure/How-to-set-up/Docker/#media-server "Permanent link")

Plex, Emby, JellyFin and Bazarr

Plex, Emby, JellyFin and Bazarr only needs access to your media library using `/data/media`, which can have any number of sub folders like Movies, Kids Movies, TV, Documentary TV and/or Music as sub folders.

`Container Path:` =>`/data/media`

`Host Path:` =>`/<path_to_data>/data/media/`

* * *

**Don't forget to look at the [Examples](https://trash-guides.info/File-and-Folder-Structure/Examples/) how to set up the paths inside the applications.**

### Permissions[](https://trash-guides.info/File-and-Folder-Structure/How-to-set-up/Docker/#permissions "Permanent link")

Recursively chown user and group and Recursively chmod to 775/664

Docker-compose Example[](https://trash-guides.info/File-and-Folder-Structure/How-to-set-up/Docker/#docker-compose-example "Permanent link")
-------------------------------------------------------------------------------------------------------------------------------------------

This is a docker-compose example based on a default Ubuntu install.

The storage location used for the host is the same as in the container to make it easier to understand in this case `/data`.

The appdata (`/config`) will be stored on the host in the `/docker/appdata/{appname}`

docker-compose - [Click to show/hide]

### Docker-Compose Commands[](https://trash-guides.info/File-and-Folder-Structure/How-to-set-up/Docker/#docker-compose-commands "Permanent link")

docker-compose commands - [Click to show/hide]
*   `sudo docker-compose up -d` (This Docker-compose command helps builds the image, then creates and starts Docker containers. The containers are from the services specified in the compose file. If the containers are already running and you run docker-compose up, it recreates the container.)
*   `sudo docker-compose pull` (Pulls an image associated with a service defined in a docker-compose.yml)
*   `sudo docker-compose down` (The Docker-compose down command also stops Docker containers like the stop command does. But it goes the extra mile. Docker-compose down, doesn’t just stop the containers, it also removes them.)
*   `sudo docker system prune -a --volumes --force` (Remove all unused containers, networks, images (both dangling and unreferenced), and optionally, volumes.)

* * *

Questions or Suggestions?

If you have questions or suggestions, click the button below to join our Discord server.[Click For Support](https://trash-guides.info/discord)[![Image 1: Discord chat](https://img.shields.io/discord/492590071455940612?style=for-the-badge&color=4051B5&logo=discord)](https://trash-guides.info/discord)