Is there an existing issue for this?
Current Behavior
Without ext-tokenizer as php extension in the container image, commands like composer install -o to install dev packages or even composer update --no-dev -o to update no-dev packages will result in an error message:
root@c923b8db0924:/# cd /app/www/public/
root@c923b8db0924:/app/www/public# composer update --no-dev
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires phpunit/phpunit ^12.5 -> satisfiable by phpunit/phpunit[12.5.8, 12.5.9, 12.5.10].
- phpunit/phpunit[12.5.8, ..., 12.5.10] require staabm/side-effects-detector ^1.0.5 -> satisfiable by staabm/side-effects-detector[1.0.5].
- staabm/side-effects-detector 1.0.5 requires ext-tokenizer * -> it is missing from your system. Install or enable PHP's tokenizer extension.
...
Running update with --no-dev does not mean require-dev is ignored, it just means the packages will not be installed. If dev requirements are blocking the update you have to resolve those problems.
Expected Behavior
Allow image users to install dev packages or update no-dev packages
Steps To Reproduce
# cd /app/www/public/
# composer update --no-dev
...
See error message above
#
Environment
- OS: N/A
- How docker service was installed: N/A
CPU architecture
x86-64
Docker creation
Container logs
Is there an existing issue for this?
Current Behavior
Without ext-tokenizer as php extension in the container image, commands like
composer install -oto install dev packages or evencomposer update --no-dev -oto update no-dev packages will result in an error message:Expected Behavior
Allow image users to install dev packages or update no-dev packages
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs