-
Notifications
You must be signed in to change notification settings - Fork 192
Open
Description
Prerequisites
- I understand and accept the project's code of conduct.
- I have already searched in existing issues and found no previous report of this bug.
Describe the bug and add attachments
Something went really wrong with the image update you did yesterday.
When we start the prestashop/prestashop:8.2.2-fpm image (clean CI env), we're greeted with a version 9 backoffice (top left says still version 8.2.2).
Sure there is other better ways to verify this, but just looking at the number of modules in/var/www/html/modules from the image before and after the update:
# Pull using sha hash from the older image
~ $ docker run --rm -it prestashop/prestashop:8.2.2-fpm@sha256:15dcc00c589c727ed549441994a3ad4c9cac7625865af5e9bafe4f3677b4ac8c ls -la modules | wc -l
71
# Pull using the current version of the tag
~ $ docker run --rm -it prestashop/prestashop:8.2.2-fpm ls -la modules | wc -l
84This is an easy way to verify locally that the image has changed in a big way.
This happens with :8.2.4-fpm too.
Steps to reproduce
- Run:
docker run --rm -it prestashop/prestashop:8.2.2-fpm@sha256:15dcc00c589c727ed549441994a3ad4c9cac7625865af5e9bafe4f3677b4ac8c ls -la modules | wc -l
- Run:
docker run --rm -it prestashop/prestashop:8.2.2-fpm ls -la modules | wc -l
Expected behavior
Module count would be the same before and after the update. Also for the image to not update v9 when I'm asking for v8.
Actual Result
Source code for Prestashop v9 is installed.
PrestaShop version where the bug happens
8.2.2
Module version where the bug happens
8.2.2
PHP version(s) where the bug happened
8.1
Your company or customer's name goes here (if applicable).
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels