Volume Permissions

[philipp-paland]

I ran into a problem with volume permissions with this image. I think Atlassian used to have the same thing in their bitbucket image, they describe a solution like this:

https://hub.docker.com/r/atlassian/bitbucket-server/

"For other versions (older than 4.12)"

Set permissions for the data directory so that the runuser can write to it:

$> docker run -u root -v /data/bitbucket:/var/atlassian/application-data/bitbucket atlassian/bitbucket-server chown -R daemon /var/atlassian/application-data/bitbucket"

And with that I was able to solve the problem. In the newer versions of the image, they introduced an entrypoint script that takes care of the issue automatically:

https://bitbucket.org/atlassian/docker-atlassian-bitbucket-server/src/8f2d89f4a904ef0ac2ce0d4afaf49b2bbccb28ac/entrypoint.sh?at=base-5&fileviewer=file-view-default

Maybe a script like that could be introduced here, too.

[nitrocode]

@therealppa I believe the same issue affects this bamboo dockerfile when upgrading.

Edit: Looks like docker bamboo has its own entrypoint script similar to the one above.

This is biting me right now. I'm trying to upgrade from 5.14 to 6.7.1 and I noticed that the user changed from daemon to bamboo in the docker container. We have 2 bamboo servers and I fixed one of them by chowning the bamboo directories to daemon:daemon but still seeing issues with the other bamboo service which has a lot more directories.

Has anyone else run into this problem? If so, how did you solve it?