Closed alex1702 closed 4 years ago
The image run as an user called php
and do not have permission to write on the /root dir, but all sudo commands should run fine.
Yeah, OK. But that's being handled by gitlab-runner, not me. So how am I supposed to fix it if I can't control it?
from times to times the gitlab runners throws some weird errors like this one, try cleaning the gitlab ci cache by click on the UI button
Unfortunately, that didn't help either. Another idea? You can use gitlab-ci with your image?
hm, weird, can you share your full (ou relevant parts like before_script and such) .gitlab-ci.yml
?
Yeah, i use it in all my php projects
It is the yml in the first post. I just adjusted the path to the script, because this is not for the eyes of the public. But just as a hint. The path is in /var/www and is also rw mounted on the gitlab-runner server.
And in the past the configuration worked like this.
Okay, I found the problem. My docker on the gitlab-runner server uses the storage driver aufs, but it seems to be causing problems. I changed it to overlay2 and it works. The server still runs with Ubuntu 16.04, maybe that's the reason.
You can find out the current Storage Driver with docker info
.
Appropriate issue https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26618
And the instructions for changing the Storage Driver : https://docs.docker.com/storage/storagedriver/overlayfs-driver/
Oh i see, glad you found a solution!
I get the following error message: could not lock config file /root/.gitconfig: Operation not permitted
gitlab-ci.yml:
Gitlab Output:
Gitlab raw Output: