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 .
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.
I have also added step
- "ls -la .composer/cache/repo"
in the pipeline file to debug what is happening and this is failing.
+ ls -la .composer/cache/repo
Creating build_composer_1 ... done
ls: .composer/cache/repo: No such file or directory
And also it is clear from composer install that the container is not able to write to the cache:
Cannot create cache directory /home/composer/.composer/cache/repo/https---repo.packagist.org/, or directory is not writable. Proceeding without cache
Cannot create cache directory /home/composer/.composer/cache/files/, or directory is not writable. Proceeding without cache
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
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 :
+ export UID && echo " UID: $UID "
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.
Can someone suggest how to achieve a correct UID mapping on bitbucket?
here is also an extract of the bitbucket pipelines yml file
- "export UID && echo \" UID: $UID \""
- "export UID && make tests_ci"
Take a look at the questions below that will help you debug this:
Having UID=0 is quite common when using docker, you can read about it here.
It is quite common indeed, all the issues i see about permissions on bitbucket pipelines are quite uncommon though as you can see maybe bitbucket clone dir subdirectories might not be mountable as shown here. I will try to refactor and see if it works
Hello Community! I hope you've been enjoying the 🍂Apptoberfestivities🍂 (I know I have!) The event is heating up next week with a series of virtual events that we're calling the 🍻🍂Partner App ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events