Closed tylerreckart closed 6 years ago
Hi There
The error below shown in the Docker log is usually due to settings within the php.ini either being invalid or missing.
basic_string::_M_construct null not valid
It is actually something I am working on for the next release, ensuring it it gives a more detailed response.
The default Pattern settings for the php.ini are: (leaving the property list empty returns them all)
extension=/path/to/module/FiftyOneDegreesPatternV3.so
FiftyOneDegreesPatternV3.data_file=path/to/51Degrees/data/file.dat
FiftyOneDegreesPatternV3.property_list=
FiftyOneDegreesPatternV3.cache_size=10000
FiftyOneDegreesPatternV3.pool_size=20
Take a look and let me know how you get on.
@JoshGrew51D Thanks for the quick response. This was due to my misunderstanding of how to configure FiftyOneDegreesPatternV3.property_list=
Hello,
I am currently having issues installing the PHP extension API inside of a Dockerized environment running
php-fpm
.Here is the system I'm working in:
Unlike the other PHP7 issues that I've researched while trying to debug this, I'm not hitting any errors when running
make install
. A few warnings are generated (see below), but the extension is still compiled and installed into the correct directory. We have been able to observe an error when PHP loads the extension (also below) that causes the container to terminate itself on startup because of a thrown instance ofstd::logic_error
.I've tried installing and compiling swig from the source as mentioned in previous PHP7 issues. I am able to verify that version
4.0.0
is installed into/usr/local/share/swig/[swig version]/
, however even with version 4, I can still observe the warnings being generated duringmake install
and the container still terminates.Build Process
Warnings
Docker Logs
Thoughts on what I might be missing here?