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

Docker Compose Tweaks #38

Open
zhabiba24 opened this issue Sep 28, 2024 · 2 comments
Open

Docker Compose Tweaks #38

zhabiba24 opened this issue Sep 28, 2024 · 2 comments

Comments

@zhabiba24
Copy link

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:

  1. Login to server as root
  2. Pull down repo
  3. Install docker
  4. docker compose up -d

Expected behavior
Compose should launch without errors on a fresh install.

@sjacgit
Copy link
Member

sjacgit commented Sep 28, 2024

We're aware of this issue, it will be fixed in the upcoming version expected on Monday. Sit tight!

@sjacgit
Copy link
Member

sjacgit commented Oct 5, 2024

Please let us know if this is fixed with the latest release so we can close this issue.

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

2 participants