diff options
author | Angristan <Angristan@users.noreply.github.com> | 2018-03-23 14:34:01 +0100 |
---|---|---|
committer | Chocobozzz <me@florianbigard.com> | 2018-03-23 14:34:01 +0100 |
commit | 03ae9d887ae46bef62cfd2b46c1d6b0836bea246 (patch) | |
tree | a51020c0638b26c6374d5bdd0ecad28985427bdd /support/doc | |
parent | c7574e8661d62982516ac21c661964b49adbc850 (diff) | |
download | PeerTube-03ae9d887ae46bef62cfd2b46c1d6b0836bea246.tar.gz PeerTube-03ae9d887ae46bef62cfd2b46c1d6b0836bea246.tar.zst PeerTube-03ae9d887ae46bef62cfd2b46c1d6b0836bea246.zip |
Add permissions instructions for the data volume (#387)
* Add permissions instructions for the data volume
* Remove useless newline
Diffstat (limited to 'support/doc')
-rw-r--r-- | support/doc/docker.md | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/support/doc/docker.md b/support/doc/docker.md index e0c03a1dc..3d25d06c4 100644 --- a/support/doc/docker.md +++ b/support/doc/docker.md | |||
@@ -50,6 +50,18 @@ balancer, although any HTTP reverse proxy will work fine. See the example | |||
50 | Nginx configuration `support/nginx/peertube` file to get an idea of | 50 | Nginx configuration `support/nginx/peertube` file to get an idea of |
51 | recommendations and requirements to run PeerTube the most efficiently. | 51 | recommendations and requirements to run PeerTube the most efficiently. |
52 | 52 | ||
53 | When starting the containers for the first time, you will get permissions errors for the data volume, like this one: | ||
54 | |||
55 | ``` | ||
56 | Error: EACCES: permission denied, mkdir '/data/logs' | ||
57 | ``` | ||
58 | |||
59 | The peertube user inside the container has a UID and GID of 991 so you have to change the folder's owner, in the case you're using `./data`: | ||
60 | |||
61 | ``` | ||
62 | chown -R 991:991 data/ | ||
63 | ``` | ||
64 | |||
53 | **Important**: note that you'll get the initial `root` user password from the | 65 | **Important**: note that you'll get the initial `root` user password from the |
54 | program output, so check out your logs to find them. | 66 | program output, so check out your logs to find them. |
55 | 67 | ||