Updated docker-compose.yml to restrict capabilities and privileges of containers - #48
Updated docker-compose.yml to restrict capabilities and privileges of containers#48zaniyah wants to merge 3 commits into
Conversation
|
I merged the latest OCW changes into my fork and re-opened the draft PR. Currently this is the error I am seeing with things as they are: But I had that before I made these changes, so I do not think it is related. |
|
Indeed, something is not right with file ownership, and this causes the write issues. |
Log directory needs to have same permissions as docker container, I think that's the cause. If you do chown -R 5000:5000 for log dir |
|
I think the |
|
Alternatively we could use userid/groupid variables in .env so that the local user matches. |
|
This error does not affect the changes to |
|
Hi. Tested the change, nothing seems broken and it's working overall. One thing if you could do, regarding carwings directory. For push notifications (and future-proofing), APNS needs a certificate file. The old way was to keep it in carwings directory. Now that only settings is mounted, could there be another mounted directory (named resources, files, or something else) for this exact purpose? Otherwise it's looking good! |
I have added the statements that I believe are needed, but have not had time to test it properly, yet.