-
Notifications
You must be signed in to change notification settings - Fork 70
Extension not loaded #40
Comments
I ran into a surprisingly similar issue just yesterday. I guess the php.ini file is in the wrong directory. In the resulting lambda-layer it will be found under /opt/php.ini but the bootstrap will search for it somewhere else. I changed To Now extensions are beeing loaded (confimed via |
Hi there. So i bumped into the same issue also, trying to install a PHP layer on my dumb AWS lambda function(I needed the json and mbstring modules). In my case, the above solution didn't work, as I was getting a permission denied error:
The solution was to update the exec line to:
and add the php.ini file, that includes all the modules I need, at the top level of my lambda function folder, next to all the other files. As the lambda env runs at /var/task , setting the path at /var/task/php.ini worked for me. Extensions are loaded now. Hope this helps. All the best |
The extensions are not loaded for me either, and don't know how to approach this problem. I am getting the following error in the logs.
According to the docs, the modules should be there, but apparently they are not. Any ideas, suggestions? Thanks in advance! |
I am getting this error: "Use of undefined constant XML_PI_NODE - assumed 'XML_PI_NODE' (this will throw an Error in a future version of PHP)"
This seems to indicate that the xml extension is not loaded, but I have added it to php.ini
The text was updated successfully, but these errors were encountered: