What goes wrong in the Bitbucket pipe when building a Laravel application?

Question

Composer

There is an application that works properly on the server. Even after transferring to another server through the banal git clone + composer install - everything is ok.
I tried for the first time in my life to set up a build through Bitbucket pipelines. Must do composer install and pack into container.
Here it packs in a container, but the installer does not work. Gives the following error:

+ composer install
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Your lock file does not contain a compatible set of packages. Please run composer update.
Problem 1
- php-amqplib/php-amqplib is locked to version v3.1.0 and an update of this package was not requested.
- php-amqplib/php-amqplib v3.1.0 requires ext-sockets * -> it is missing from your system. Install or enable PHP's sockets extension.
To enable extensions, verify that they are enabled in your .ini files:
- /usr/local/etc/php/php-cli.ini
- /usr/local/etc/php/conf.d/docker-php-ext- sodium.ini
- /usr/local/etc/php/conf.d/docker-php-ext-zip.ini
You can also run `php --ini` inside terminal to see which files are used by PHP in CLI mode.

On a normal server, I think I would correct php.ini or see what is there in general with ext-sockets. And with a cloud solution in the form of a bitbucket - xs what to do. I didn’t see such a problem on the Internet, although it’s strange, no one else uses bitbucket and amqplib? Or am I doing something very wrong

Answer 1

composer install --ignore-platform-reqs
Will deliver, ignoring the extension requirement