Infrastructure/imageproxy
0
Fork 0
mirror of https://github.com/willnorris/imageproxy.git synced 2024-12-16 21:56:43 -05:00
Code Issues Activity

readme: add note about docker bind-mounts

Browse source 
when we changed the container to run as a non-root user, it broke some
imageproxy instances that were relying on the default docker user and
file permissions.  Users running dockerized imageproxy with a
bind-mounted on-disk cache now need to make sure the user and file
permissions line up.

fixes #198
This commit is contained in:
Will Norris 2019-09-13 12:39:48 +00:00
parent 785c5bddd6
commit fb937ccd1b
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
README.md
View file

@ -334,6 +334,11 @@ Or in your Dockerfile:
ENTRYPOINT ["/app/imageproxy", "-addr 0.0.0.0:8080"] ENTRYPOINT ["/app/imageproxy", "-addr 0.0.0.0:8080"]
``` ```
If running imageproxy inside docker with a bind-mounted on-disk cache, make sure
the container is running as a user that has write permission to the mounted host
directory. See more details in
[#198](https://github.com/willnorris/imageproxy/issues/198).
### nginx ### ### nginx ###
Use the `proxy_pass` directive to send requests to your imageproxy instance. Use the `proxy_pass` directive to send requests to your imageproxy instance.