Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for read-only volumes #14

Open
fatflyingpigs opened this issue Jul 29, 2021 · 2 comments
Open

Support for read-only volumes #14

fatflyingpigs opened this issue Jul 29, 2021 · 2 comments

Comments

@fatflyingpigs
Copy link

Not sure why goaccess would need write or execute access to my logs. Trying to run the volume as read-only results with:

...
chown: /opt/log/error.log.14.gz: Read-only file system
...```

At the very end it will give a `nginx: [alert] could not open error log file: open() "/var/lib/nginx/logs/error.log" failed (13: Permission denied)`
@GregYankovoy
Copy link
Owner

GregYankovoy commented Jul 30, 2021

GoAccess does not require write access to the logs. However, nginx is used in tandem with goaccess in this container to centralize goaccess services through a single port, and fix some strange websockets behavior. I believe nginx attempts to create an error.log file if it does not exist, and/or make sure it can write to it.

@masterwishx
Copy link

masterwishx commented Dec 7, 2021

GoAccess does not require write access to the logs. However, nginx is used in tandem with goaccess in this container to centralize goaccess services through a single port, and fix some strange websockets behavior. I believe nginx attempts to create an error.log file if it does not exist, and/or make sure it can write to it.

What is path in unraid docker should be for /opt/log im using NginxProxyManager ?
im having same error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants