akeneo / Dockerfiles

DEPRECATED for PIM 4.0 and above - Official Dockerfiles for Akeneo development and testing
https://hub.docker.com/r/akeneo/
MIT License
49 stars 34 forks source link

Dockerfile for fpm #356

Open heojee1 opened 4 years ago

heojee1 commented 4 years ago

I have a question regarding fpm Dockerfile.

I have community-standard PIM with Docker and I want to install PHP-client inside this Docker as well. I found out that PHP-client requires ext-apcu. So I copied fpm Dockerfile to the root directory and added a line to install apcu. Then I let in docker-compose.yml, I let fpm container build from that Dockerfile. However, if I do this, fpm container exits immediately after $docker-compose up -d and I cannot access Akeneo website at localhost:8080.

Screen Shot 2020-04-30 at 18 32 33

I am not sure how to deal with Dockerfile. I am quite new to all these so I would really appreciate your help. Thank you in advance :)

damien-carcel commented 4 years ago

Hello @heojee1.

Can you please tell me which version of Akeneo are you using? Remember this repository only concerns Akeneo 3.2 and prior versions. Akeneo 4.0 comes with its own Docker images, with Dockerfiles present in the akeneo/pim-community-dev GitHub repository directly.

That being said, you saoi you copied the Dockerfile. Which Dockerfile are you talking about? And concerning apcu, it is enabled for both FPM and CLI by default, both in the images of this repository and in the one of akeno/pim-community-dev 4.0.

Finally, looking at the error you posted a screenshot of, I think you may have an issue with Apache not being able to talk with FPM. Something is wrong either in your FPM custom configuration, or in the Apache configuration. By default, httpd Docker images don't have mod_proxy enabled, and it is mandatory for Apache to talk to FPM. But here too, the default configurations provided with Akeneo PIM is already OK.

Best regards, Damien.