You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When running docker compose as root on a server, I would get permission denied errors that bayanat didn't have access to the logs volume where it writes app.log.
I also had a warning message that the version directive is no longer relevant and that the media volume was missing. Fixed by mounting whatever I named the media volume as to a declaration at the bottom. Could fix perms errors by making bayanat run as root, i.e .setting USER:ROOT in the compose yaml but this has negative security implications.
On a server with 1GB RAM and 1CPU I ran into CPU spikes that caused application to crash too when running flask install. Would be helpful to state box requirements for production usage of docker compose to avoid a situation like this.
To Reproduce
Steps to reproduce the behavior:
Login to server as root
Pull down repo
Install docker
docker compose up -d
Expected behavior
Compose should launch without errors on a fresh install.
The text was updated successfully, but these errors were encountered:
Describe the bug
When running docker compose as root on a server, I would get permission denied errors that bayanat didn't have access to the
logs
volume where it writesapp.log
.I also had a warning message that the version directive is no longer relevant and that the media volume was missing. Fixed by mounting whatever I named the media volume as to a declaration at the bottom. Could fix perms errors by making bayanat run as root, i.e .setting
USER:ROOT
in the compose yaml but this has negative security implications.On a server with 1GB RAM and 1CPU I ran into CPU spikes that caused application to crash too when running
flask install
. Would be helpful to state box requirements for production usage of docker compose to avoid a situation like this.To Reproduce
Steps to reproduce the behavior:
docker compose up -d
Expected behavior
Compose should launch without errors on a fresh install.
The text was updated successfully, but these errors were encountered: