-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatibility with Magento >= 2.4.0 (Imagick missing) #357
Comments
Still no update on that issue? 😢 |
This issue is bothering me too 😞 |
Same issue here. Can you correct this? |
@magento-admin still no update on this? It's been almost a year now! |
I just ran into this issue, so I submitted PR #363 to fix it. Feel free to use that until it gets officially merged and new Docker images are uploaded. |
Oh, and for anyone who's interested: PR #363 also will add WebP support to the GD extension, as well. |
Can there be some movement on this issue? it's a tool that adobe cloud provides, but then the docker instance is not providing it? Making it difficult to test changes to the adapter... |
Preconditions
magento/magento-cloud-docker-php:8.1-fpm-1.3.5
andmagento/magento-cloud-docker-php:8.1-cli-1.3.5
Steps to reproduce
Try to upgrade to Magento 2.4.x by following the steps described in the Perform an upgrade guide:
docker-compose.yml
filecomposer require magento/composer-root-update-plugin ~2.0 --no-update
composer update
docker-compose.yml
file to use PHP 8.1-1.3.5 (or any other version like 1.3.1, 1.3.4 etc.)docker-compose up -d
bin/magento-docker bash
composer require-commerce magento/product-community-edition 2.4.4 --no-update
composer update
Expected result
composer update
command works fineActual result
bin/magento-docker bash
):composer update
command fails with the following errors:Additional information
This is a followup of the issue #344 that I closed thinking it was solved, but removing the
imagick
extension from the PHP_EXTENSION in thedocker-compose.yml
file doesn't load imagick in the Docker image.The text was updated successfully, but these errors were encountered: