|
| 1 | +## Standard Docker Run Command (STRM) |
| 2 | + |
| 3 | +Below is a standard Docker run command if spawning from the command line. Keep in mind the volume mount paths. If you change these in the environment variable, make sure you change it in the volume mount path. |
| 4 | + |
| 5 | +```bash |
| 6 | +docker run -it -d \ |
| 7 | + --name=torbox-media-center \ |
| 8 | + --restart=always \ |
| 9 | + --init \ |
| 10 | + -v /home/$(whoami)/torbox:/torbox \ |
| 11 | + -e TORBOX_API_KEY=<EDIT_THIS_KEY> \ |
| 12 | + -e MOUNT_METHOD=strm \ |
| 13 | + -e MOUNT_PATH=/torbox \ |
| 14 | + anonymoussystems/torbox-media-center:main |
| 15 | +``` |
| 16 | + |
| 17 | +## Standard Docker Run Command (FUSE) |
| 18 | + |
| 19 | +Below is a standard Docker run command for using FUSE. Notice the difference when attaching the `/dev/fuse` device. We also needed to add the `--cap-add SYS_ADMIN` parameter. The Docker container needs access to the FUSE device of the system to activate the virtual file system. |
| 20 | + |
| 21 | +> [!CAUTION] |
| 22 | +> The `--cap-add SYS_ADMIN` parameter gives the container certain permissions which it would otherwise have. This is required to access the host systems FUSE device, but keep this in mind. You can read more about this [here](https://docs.docker.com/reference/cli/docker/container/run/#privileged). |
| 23 | +
|
| 24 | +```bash |
| 25 | +docker run -it -d \ |
| 26 | + --name=torbox-media-center \ |
| 27 | + --restart=always \ |
| 28 | + --init \ |
| 29 | + --cap-add SYS_ADMIN \ |
| 30 | + --device /dev/fuse \ |
| 31 | + -v /mnt/torbox:/torbox:rshared \ |
| 32 | + -e TORBOX_API_KEY=<EDIT_THIS_KEY> \ |
| 33 | + -e MOUNT_METHOD=fuse \ |
| 34 | + -e MOUNT_PATH=/torbox \ |
| 35 | + anonymoussystems/torbox-media-center:main |
| 36 | +``` |
| 37 | + |
| 38 | + |
| 39 | +## Standard Docker Run Command Using GitHub Repository (STRM) |
| 40 | + |
| 41 | +This config below is exactly the same as the above, except it is pulling from the GitHub repository rather than Docker Hub. Some people, find that GitHub is much faster than Docker, and sometimes Docker is down. |
| 42 | +```bash |
| 43 | +docker run -it -d \ |
| 44 | + --name=torbox-media-center \ |
| 45 | + --restart=always \ |
| 46 | + --init \ |
| 47 | + -v /home/$(whoami)/torbox:/torbox \ |
| 48 | + -e TORBOX_API_KEY=<EDIT_THIS_KEY> \ |
| 49 | + -e MOUNT_METHOD=strm \ |
| 50 | + -e MOUNT_PATH=/torbox \ |
| 51 | + ghcr.io/torbox-app/torbox-media-center:main |
| 52 | +``` |
| 53 | +## Docker Run Command Changing Location Of Files On Local System (STRM) |
| 54 | + |
| 55 | +This config below changes where on the local system the files are mounted. Instead of in the home directory, it is now mounted in the `/mnt/torbox` directory, which is where you would be able to find your mounted files. |
| 56 | + |
| 57 | +```bash |
| 58 | +docker run -it -d \ |
| 59 | + --name=torbox-media-center \ |
| 60 | + --restart=always \ |
| 61 | + --init \ |
| 62 | + -v /mnt/torbox:/torbox \ |
| 63 | + -e TORBOX_API_KEY=<EDIT_THIS_KEY> \ |
| 64 | + -e MOUNT_METHOD=strm \ |
| 65 | + -e MOUNT_PATH=/torbox \ |
| 66 | + anonymoussystems/torbox-media-center:main |
| 67 | +``` |
| 68 | + |
| 69 | +## Docker Run Command Changing Location Of Files In Container (STRM) |
| 70 | + |
| 71 | +This config below changes where on the Docker side where the files are stored. This isn't exactly necessary, but some people may want to change it, so here is a sample where the local system sees the mounted files at `/mnt/torbox` but inside the container, the files are now located at `/data`. Keep in mind that the `MOUNT_PATH` changed to reflect this. |
| 72 | + |
| 73 | +```bash |
| 74 | +docker run -it -d \ |
| 75 | + --name=torbox-media-center \ |
| 76 | + --restart=always \ |
| 77 | + --init \ |
| 78 | + -v /mnt/torbox:/data \ |
| 79 | + -e TORBOX_API_KEY=<EDIT_THIS_KEY> \ |
| 80 | + -e MOUNT_METHOD=strm \ |
| 81 | + -e MOUNT_PATH=/data \ |
| 82 | + anonymoussystems/torbox-media-center:main |
| 83 | +``` |
0 commit comments