#Bitnami magento stack varnish logs how to#
I thought about running the above commands within the containers readinessProbe however not sure if it would work as not 100% on the state of Magento when that is first called, alongside it seeming very hacky.Īny advice on how to best set up custom modules within a bitnami/magento container would be much appreciated. We have by far the largest RPM repository with NGINX module packages and VMODs for Varnish.
This gives me a functioning container, however, kubernetes is not able to rebuild this container as I am manually running a bunch of commands after Magento has installed. The first sorts the magento set up issue, the second ensures the next time an http request comes in Magento is able to correctly generate any directories and files it needs. $ chown -R bitnami:daemon /opt/bitnami/magento/htdocs Therefore to get things working I have to open a shell to the container and run some commands: $ php /opt/bitnami/magento/htdocs/bin/magento setup:upgrade The pod logs show that Magento installs correctly but it doesn't know what to do with the custom module:Įxception #0 (UnexpectedValueException): Setup version for module 'Foo_Bar' is not specified magento_data/code /opt/bitnami/magento/htdocs/app/codeĪfter building and running this image the site pings back a 500 error. magento_data/code contains the module, i.e. # add magento_code directory to the bitnami magento install I am currently trying to install the module from a local dir into the containers Dockerfile: # run bitnami's magento container I have a custom module that I want to install on a container running the bitnami/magento docker image within a kubernetes cluster.
0 kommentar(er)
