Currently, the development container for the musicbrainz service mounts the local working copy of musicbrainz-server with root user. Everything also runs as root inside the container. This makes any file produced by script/compile_resources.sh and such to be owned by root on the host as well. It would be much handier to have these files owned by the user running the docker-compose commands instead.

A first step would be to create a musicbrainz user inside the container to run everything with.

A second step would be to create this user with the same id and gid as the user running docker-compose, in development setup only.