Installation failed - Docker, Linux about shopsys

[PetrHeinz]

Hello @rapemer,

thanks for reporting this issue. The issue is caused by our php-fpm image, which is based on phpdockerio/php72-fpm:latest. In the latest release there was a BC breaking change and it cannot be installed at the moment. We're already working on the solution by switching to a more stable image. You can see the WIP in https://github.com/shopsys/shopsys/compare/mc-docker-images-switch.

I will create a PR in a few hours, you're welcome to join in with comments.

There is also a hotfix 36df504 which makes the appliaction buildable, but acceptance tests fail, you can use it if you want to build the application.

[MattCzerner]

Hello @rapemer,

we just commited modifications to our docker images to make it work, you can see it in this commit,
013978d

Please read changelog since there could be important informations for you to upgrade on new php-fpm image.

[PetrHeinz]

There were actually more changes related to changing the Docker image, see c2e767d...54408aa. I would advise using current master branch. We'll release 7.0.0-alpha2 till the end of the month.

Did you manage to get it working?

[rapemer]

@PetrHeinz thanks for quick response and informations - I can wait for PR merge ;)

[rapemer]

@MattCzerner, @PetrHeinz thanks, I'm going to try it ..

[rapemer]

@PetrHeinz after commands: git checkout master and git pull there is command composer install under sudo - it's very dangerous to run composer under sudo, see https://getcomposer.org/root

it's in file .git/hooks/post-merge at line 21: check_run composer "sudo composer install"

[rapemer]

@PetrHeinz, @MattCzerner docker-compose up -d --build at current master done without errors, thanks a lot ;)

[PetrHeinz]

@rapemer Are you sure you don't have any local custom settings of git hooks? Composer warns about executing under superuser privileges and there is no warning on either my machine nor on our CI.

In the image we used earlier, there was only user root, so composer was indeed run by root user (this was one of the reasons for switching the Docker image). But not using a githook.

[rapemer]

@PetrHeinz sorry, of course it's my local hook and I don't know how it could get there ..