Correction: the UID is not the problem. For some reason the mounting of the docker volumes is still not working correctly and suffering some permission errors on bitbucket.
In order to cache the composer folder i was mounting ./.composer to /home/composer/.composer .
- ./.composer:/home/composer/.composer
This was causing permission errors, so changed it so that the current folder is also mounted at /home/composer but this is also not working.
- ./:/home/composer/
I have also added step
- "ls -la .composer/cache/repo"
in the pipeline file to debug what is happening and this is failing.
<span>+ ls -la .composer/cache/repo</span><span>Creating build_composer_1 ... </span><span>done</span><span>ls: .composer/cache/repo: No such file or directory</span>
And also it is clear from composer install that the container is not able to write to the cache:
<span>Cannot create cache directory /home/composer/.composer/cache/repo/https---repo.packagist.org/, or directory is not writable. Proceeding without cache</span><span>Cannot create cache directory /home/composer/.composer/cache/files/, or directory is not writable. Proceeding without cache</span><span>Loading composer repositories with package information</span><span>Installing dependencies (including require-dev) from lock file</span>
How am i supposed to leverage the composer caching as shown on this document if my container cannot write the files to the host?
Original post below
--------------------------------
Problem, when running a build on bitbucket the runner has not UID and thus volumes cannot be mounted correctly, See step output :
<span>+ export UID && echo " UID: $UID "</span><span><br>UID: 0</span>
Mounting a container volume with the right UID is necessary so that new files can be mounted and written back to the volume.
In my case this is stopping composer (php) when creating files back to the volume and so the vendor folder needs to be recreated from connecting back to packagist every time. I could also try to cache manually the vendor folder but Bitbucket is a very different and not standard environment so I cannot really play too much with it also because of the 50 minutes build time limit on a monthly basis.
In a similar article but back from time it looks like docker was able to write files back as the container user which is usually root but without a UID mapping this cannot be achieved with the correct permissions.
https://community.atlassian.com/t5/Bamboo-questions/Bamboo-docker-Could-not-remove-working-directory-for-plan/qaq-p/66819
Can someone suggest how to achieve a correct UID mapping on bitbucket?
here is also an extract of the bitbucket pipelines yml file
options:
docker: true
pipelines:
default:
- step:
caches:
- docker
- composer
script:
- "export UID && echo \" UID: $UID \""
- "export UID && make tests_ci"
definitions:
caches:
composer: ./.composer
