- Saved searches
- Use saved searches to filter your results more quickly
- Installing the exif (or other php) extensions #371
- Installing the exif (or other php) extensions #371
- Comments
- Saved searches
- Use saved searches to filter your results more quickly
- Reading Exif data is not supported by this PHP installation. #362
- Reading Exif data is not supported by this PHP installation. #362
- Comments
Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing the exif (or other php) extensions #371
Installing the exif (or other php) extensions #371
Comments
I’m working on a project that requires exiftool (and the php extension). By default, neither of those is installed in the php container. I was able to figure out the docker commands to add the php extension; however, I am still not able to get it to show up in the web config.
name: project recipe: pantheon config: framework: drupal env: dev site: project id: my-project-id services: appserver: extras: - "apt-get -yqq update" - "apt-get -yqq install exiftool" - "docker-php-ext-configure exif" - "docker-php-ext-install exif" - "docker-php-ext-enable exif"
The text was updated successfully, but these errors were encountered:
It does, yes. The site I’m working on is hosted on pantheon.
As a side note, I’m currently getting around this by first creating a dockerfile with the following:
FROM devwithlando/pantheon-appserver:7.0-fpm RUN apt-get -yqq update RUN apt-get -yqq install exiftool RUN docker-php-ext-configure exif RUN docker-php-ext-install exif RUN docker-php-ext-enable exif
I ended up publishing the image to dockerhub and can use it within my team with:
name: project recipe: pantheon config: framework: drupal env: dev site: project id: my-project-id services: appserver: overrides: services: image: btmash/pantheon-appserver
Interesting. I was just thinking if Pantheon supports that extension, maybe it could be included in the Lando image eventually?
That would be nice. Though my main thinking with this would be that if there is a way to flexibly add other php extensions (esp due to having support for laravel and the like) that would be better than including additional php extensions into the core image.
@uberhacker @btmash this isn’t listed in the Pantheon docs but it is def loaded in their appserver so we should add it at least into their appserver.
@btmash i definitely agree with you re: php extensions in general. It would be great if there was an easy way to specify different php extensions in the .lando.yml . That said, the easiest and most reliable reliable way to set this up, at least for now, is to probably have at least the dependencies required for most of commonly used php extensions installed and then some lando.yml config to basically toggle config files on and off.
I realize this is not exactly a complete or comprehensive solution but i think i’d rather take a larger and stabler core image with more php extensions compiled (even if most are turned off) than having lando install teh deps and compile the extensions in some pre-run step.
Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reading Exif data is not supported by this PHP installation. #362
Reading Exif data is not supported by this PHP installation. #362
Comments
I’m running into this issue with a docker container I’m using laradocks that I suspect is comping from here. From what I understand some extensions depend on others to load properly. http://php.net/manual/en/exif.installation.php
The text was updated successfully, but these errors were encountered:
laradock builds its docker file using compose so here’s the relevent section
##################################### # Exif: ##################################### ARG INSTALL_EXIF=false RUN if [ $ = true ]; then \ # Enable Exif PHP extentions requirements docker-php-ext-install exif && \ docker-php-ext-enable exif \ ;fi
that get called from here
### PHP-FPM Container ####################################### php-fpm: build: context: ./php-fpm args: - INSTALL_XDEBUG=false - INSTALL_SOAP=false - INSTALL_MONGO=false - INSTALL_ZIP_ARCHIVE=false - INSTALL_BCMATH=false - INSTALL_MEMCACHED=false - INSTALL_OPCACHE=false - INSTALL_EXIF=true - INSTALL_AEROSPIKE_EXTENSION=false - CODEIGNITER=false dockerfile: Dockerfile-70 volumes_from: - applications expose: - "9000" links: - workspace extra_hosts: # IMPORTANT: Replace with your Docker Host IP (will be appended to /etc/hosts) - "dockerhost:10.0.75.1" environment: # IMPORTANT: Set the Remote Interpreter entry matching name to `laravel` - PHP_IDE_CONFIG=serverName=laravel
Yeah, except that docker-php-ext-install already invokes docker-php-ext-enable (
Service ‘php-fpm’ failed to build: One or more build-args [INSTALL_EXIF] were not consumed, failing build.
This really seems like an issue you are having with using laradock, but I’ll see what I can help with.
@suncoastkid are you perchance using their 5.6 Dockerfile? I noticed that it does not contain any reference to an arg of INSTALL_EXIF while the 7.0 Dockerfile does; which could account for the failed build where the «build-arg [was] not consumed». I’m not sure why their Dockerfiles differ since you can install exif in the php:5 image:
$ docker run -it --rm php:5 bash root@352df2afc52c:/# docker-php-ext-install exif + cd exif + phpize Configuring for: PHP Api Version: 20131106 Zend Module Api No: 20131226 Zend Extension Api No: 220131226 + ./configure checking for grep that handles long lines and -e. /bin/grep checking for egrep. /bin/grep -E checking for a sed that does not truncate output. /bin/sed checking for cc. cc checking whether the C compiler works. yes checking for C compiler default output file name. a.out checking for suffix of executables. checking whether we are cross compiling. no checking for suffix of object files. o checking whether we are using the GNU C compiler. yes checking whether cc accepts -g. yes checking for cc option to accept ISO C89. none needed checking how to run the C preprocessor. cc -E checking for icc. no checking for suncc. no checking whether cc understands -c and -o together. yes checking for system library directory. lib checking if compiler supports -R. no checking if compiler supports -Wl,-rpath. yes checking build system type. x86_64-unknown-linux-gnu checking host system type. x86_64-unknown-linux-gnu checking target system type. x86_64-unknown-linux-gnu checking for PHP prefix. /usr/local checking for PHP includes. -I/usr/local/include/php -I/usr/local/include/php/main -I/usr/local/include/php/TSRM -I/usr/local/include/php/Zend -I/usr/local/include/php/ext -I/usr/local/include/php/ext/date/lib checking for PHP extension directory. /usr/local/lib/php/extensions/no-debug-non-zts-20131226 checking for PHP installed headers prefix. /usr/local/include/php checking if debug is enabled. no checking if zts is enabled. no checking for re2c. re2c checking for re2c version. 0.13.5 (ok) checking for gawk. no checking for nawk. nawk checking if nawk is broken. no checking whether to enable EXIF (metadata from images) support. yes, shared checking for ld used by cc. /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld. yes checking for /usr/bin/ld option to reload object files. -r checking for BSD-compatible nm. /usr/bin/nm -B checking whether ln -s works. yes checking how to recognize dependent libraries. pass_all checking for ANSI C header files. yes checking for sys/types.h. yes checking for sys/stat.h. yes checking for stdlib.h. yes checking for string.h. yes checking for memory.h. yes checking for strings.h. yes checking for inttypes.h. yes checking for stdint.h. yes checking for unistd.h. yes checking dlfcn.h usability. yes checking dlfcn.h presence. yes checking for dlfcn.h. yes checking the maximum length of command line arguments. 1572864 checking command to parse /usr/bin/nm -B output from cc object. ok checking for objdir. .libs checking for ar. ar checking for ranlib. ranlib checking for strip. strip checking if cc supports -fno-rtti -fno-exceptions. no checking for cc option to produce PIC. -fPIC checking if cc PIC flag -fPIC works. yes checking if cc static flag -static works. no checking if cc supports -c -o file.o. yes checking whether the cc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries. yes checking whether -lc should be explicitly linked in. no checking dynamic linker characteristics. GNU/Linux ld.so checking how to hardcode library paths into programs. immediate checking whether stripping libraries is possible. yes checking if libtool supports shared libraries. yes checking whether to build shared libraries. yes checking whether to build static libraries. no creating libtool appending configuration tag "CXX" to libtool configure: creating ./config.status config.status: creating config.h /bin/bash /usr/src/php/ext/exif/libtool --mode=compile cc -I. -I/usr/src/php/ext/exif -DPHP_ATOM_INC -I/usr/src/php/ext/exif/include -I/usr/src/php/ext/exif/main -I/usr/src/php/ext/exif -I/usr/local/include/php -I/usr/local/include/php/main -I/usr/local/include/php/TSRM -I/usr/local/include/php/Zend -I/usr/local/include/php/ext -I/usr/local/include/php/ext/date/lib -fstack-protector-strong -fpic -fpie -O2 -DHAVE_CONFIG_H -fstack-protector-strong -fpic -fpie -O2 -c /usr/src/php/ext/exif/exif.c -o exif.lo mkdir .libs cc -I. -I/usr/src/php/ext/exif -DPHP_ATOM_INC -I/usr/src/php/ext/exif/include -I/usr/src/php/ext/exif/main -I/usr/src/php/ext/exif -I/usr/local/include/php -I/usr/local/include/php/main -I/usr/local/include/php/TSRM -I/usr/local/include/php/Zend -I/usr/local/include/php/ext -I/usr/local/include/php/ext/date/lib -fstack-protector-strong -fpic -fpie -O2 -DHAVE_CONFIG_H -fstack-protector-strong -fpic -fpie -O2 -c /usr/src/php/ext/exif/exif.c -fPIC -DPIC -o .libs/exif.o /bin/bash /usr/src/php/ext/exif/libtool --mode=link cc -DPHP_ATOM_INC -I/usr/src/php/ext/exif/include -I/usr/src/php/ext/exif/main -I/usr/src/php/ext/exif -I/usr/local/include/php -I/usr/local/include/php/main -I/usr/local/include/php/TSRM -I/usr/local/include/php/Zend -I/usr/local/include/php/ext -I/usr/local/include/php/ext/date/lib -fstack-protector-strong -fpic -fpie -O2 -DHAVE_CONFIG_H -fstack-protector-strong -fpic -fpie -O2 -Wl,-O1 -Wl,--hash-style=both -pie -o exif.la -export-dynamic -avoid-version -prefer-pic -module -rpath /usr/src/php/ext/exif/modules exif.lo cc -shared .libs/exif.o -Wl,-O1 -Wl,--hash-style=both -Wl,-soname -Wl,exif.so -o .libs/exif.so creating exif.la (cd .libs && rm -f exif.la && ln -s ../exif.la exif.la) /bin/bash /usr/src/php/ext/exif/libtool --mode=install cp ./exif.la /usr/src/php/ext/exif/modules cp ./.libs/exif.so /usr/src/php/ext/exif/modules/exif.so cp ./.libs/exif.lai /usr/src/php/ext/exif/modules/exif.la PATH="$PATH:/sbin" ldconfig -n /usr/src/php/ext/exif/modules ---------------------------------------------------------------------- Libraries have been installed in: /usr/src/php/ext/exif/modules If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the `LD_LIBRARY_PATH' environment variable during execution - add LIBDIR to the `LD_RUN_PATH' environment variable during linking - use the `-Wl,--rpath -Wl,LIBDIR' linker flag - have your system administrator add LIBDIR to `/etc/ld.so.conf' See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. ---------------------------------------------------------------------- Build complete. Don't forget to run 'make test'. Installing shared extensions: /usr/local/lib/php/extensions/no-debug-non-zts-20131226/ find . -name \*.gcno -o -name \*.gcda | xargs rm -f find . -name \*.lo -o -name \*.o | xargs rm -f find . -name \*.la -o -name \*.a | xargs rm -f find . -name \*.so | xargs rm -f find . -name .libs -a -type d|xargs rm -rf rm -f libphp.la modules/* libs/* root@352df2afc52c:/#