Updated Installation (markdown)
@@ -10,6 +10,7 @@ After running Overseerr for the first time, configure it by visiting the web UI
|
||||
* [FreeBSD / FreeNAS](#freebsd--freenas)
|
||||
* [ArchLinux](#archlinux) (Third party)
|
||||
|
||||
|
||||
## Docker
|
||||
|
||||
```
|
||||
@@ -22,6 +23,7 @@ docker run -d \
|
||||
sctx/overseerr
|
||||
```
|
||||
|
||||
|
||||
## Windows
|
||||
Docker for windows must be installed and WSL2 must all be enabled to be able to run the command below.
|
||||
|
||||
@@ -34,6 +36,7 @@ docker run -d -e LOG_LEVEL=info -e TZ=Asia/Tokyo -p 5055:3000 -v "/your/path/her
|
||||
```
|
||||
_Detail: Docker on Windows works differently than it does on Linux; it uses a VM to run a stripped-down Linux and then runs docker within that. The volume mounts are exposed to the docker in this VM via SMB mounts. While this is fine for media, it is unacceptable for the /config directory because SMB does not support file locking. This will eventually corrupt your database which can lead to slow behavior and crashes. If you must run in docker on Windows, you should put the /config directory mount inside the VM and not on the Windows host. It's worth noting that this warning also extends to other containers which use SQLite databases._
|
||||
|
||||
|
||||
## ArchLinux (Third party)
|
||||
|
||||
Built from tag: https://aur.archlinux.org/packages/overseerr/
|
||||
|
||||
Reference in New Issue
Block a user