Local dev startup fails if ~/.m2 directory hasn't been created already

[jakubfiala]

Context

When starting the service for the first time locally, the Maven installation fails because it can't read from the /home/akvo/.m2 directory.

Problem or idea

If the local system doesn't already have a ~/.m2 directory, Docker tries to create a write-only dir by default when mounting the volume. However, Maven expects to be able to read from the directory, so it fails.

Solution or next step

Either document this, or create the ~/.m2 directory automatically with read and write permissions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.