@ajeetraina @falconcr do you think it might be worth having a section about logging in this guide?

I understand the concern, but my recommendation is to follow modern best practices for logging in containerized environments:

1. Use stdout and stderr for logs: This is the industry standard for containerized applications. It simplifies log collection and analysis with observability systems.

2. Volumes for specific cases: If your application strictly requires access to the filesystem, consider mounting an external volume to store log files.

3. Redirect logs to external systems: Configure Logback to send logs to a centralized logging solution (e.g., Elastic Stack or CloudWatch) rather than writing to local files.

Granting write permissions to the container’s filesystem is not recommended due to security concerns. Allowing the container to modify its own directories could create exploitable vulnerabilities. I suggest reviewing how your project could adopt these modern practices, aligned with Docker security principles.

CC @dvdksn @rogeriofrsouza

@falconcr thanks for these recommendations.

The project budget and logs output is rather low, seems like using a centralized logging stack isn't viable at the moment.
I tried to configure the Docker Compose volume but had the same permission error, could you recommend some configuration?