Pipeline Error: ERROR: Task deploy:vendors failed! (TYPO3)

Question

Hi there,

I am using deployer to deploy my TYPO3 project on the server. Since today I am getting this error: ERROR: Task deploy:vendors failed!

I changed absolutely nothing in my pipeline since the last time.

I get these informations:
I already checked, the php extension gd ist active for my domain: https://derkreiger.at/20240430_info.php#module_gd

Can anyone help?

Thanks and all the best,
Mylene

Theodora Boudale · Answer

Hi Mylene,

Assuming that you pinned locally in the Dockerfile the exact same image SHA from the last successful build, it doesn't look like this is related to the Docker image only. Considering the local failure, the issue is not specific to Pipelines either. I suspect there may have been a change in any of the tools you use during your build which makes the build fail now on that container.

I suggest reaching out to the support team or a forum specific to the tool you are using when you get this error for help with troubleshooting this. You need to have a build that works locally on a Docker container for it to work in Pipelines as well.

Kind regards,
Theodora

Mylene Kreiger · Answer

Hi Theodora,

the last successfull build doesn't work locally:

task deploy:lock

[localhost] run git config --get user.name

[localhost] run whoami

[localhost] root

[host25.ssl-net.net] run [ -f /.share_home/derkreiger_at/amitex/staging/.dep/deploy.lock ] && echo +locked || echo 'root' > /.share_home/derkreiger_at/amitex/staging/.dep/deploy.lock

[host25.ssl-net.net] +locked

[host25.ssl-net.net] run cat /.share_home/derkreiger_at/amitex/staging/.dep/deploy.lock

[host25.ssl-net.net] ci

[host25.ssl-net.net]  Deployer\Exception\GracefulShutdownException  in lock.php on line 14:

[host25.ssl-net.net]

[host25.ssl-net.net]   Deploy locked by ci.

[host25.ssl-net.net]   Execute "deploy:unlock" task to unlock.

[host25.ssl-net.net]

done deploy:lock 313ms

ERROR: Task deploy:lock failed!

I tried to rerun the same build in the pipeline and I get the same error. I am very confused... as you can see it is always a different error. How is this possible?

Kind regards,
Mylene

Theodora Boudale · Answer

Hi Mylene,

Based on the error you posted here, it looks like the package GLIBC is missing from the Docker container where the build runs. I suspect that may be caused by either a change in the Docker image you use as a build container or a change in your project's dependencies.

I would suggest following the link to debug locally the last successful build (in the Dockerfile, provide the exact same image SHA from the last successful pipeline). If that succeeds locally, then the error has to do with a change in the Docker image. You can then pin the image by digest in the bitbucket-pipelines.yml file (you can pin to the digest of the last successful build):

* https://support.atlassian.com/bitbucket-cloud/docs/use-docker-images-as-build-environments/#Pin-images-by-digest

Kind regards,
Theodora