Open jrevillard opened 4 years ago
Hi there, Sorry about this happening. This is an issue with Docker Hub building images ahead of when it actually should. There were some changes with the base images which affected every descendent, and they are still in the process. It should be another day or so for Docker Hub to finally finish the builds and remove that error. In the meantime, I recommend using the previously tagged release.
This image has rebuilt, but now I'm seeing a different issue where it looks like this templated file is not being updated correctly
[INFO] ** [nginx] Starting nginx 1.18.0
+ exec nginx
nginx: [emerg] invalid port in upstream ":" in /etc/nginx/nginx.conf.d/php-fpm.conf:1
bash-4.4# cat /etc/nginx/nginx.conf.d/php-fpm.conf
fastcgi_pass :;
fastcgi_read_timeout ;
Edit: nope, looks like it's still not rebuilt correctly
[cont-init.d] 20-php-fpm: executing...
+ prepare_service
/var/run/s6/etc/cont-init.d/20-php-fpm: line 4: prepare_service: command not found
+ PROCESS_NAME=php-fpm
+ case "$CONTAINER_MODE" in
+ var_true
+ '[' '' = TRUE ']'
+ '[' '' = true ']'
+ sed -i -e 's#<PHP_LISTEN_PORT>##g' /etc/php7/php-fpm.conf
+ sed -i -e 's#<MAX_CHILDREN>##g' /etc/php7/php-fpm.conf
+ sed -i -e 's#<MAX_EXECUTION_TIME>##g' /etc/php7/php-fpm.conf
+ sed -i -e 's#<MAX_REQUESTS>##g' /etc/php7/php-fpm.conf
+ sed -i -e 's#<MAX_SPARE_SERVERS>##g' /etc/php7/php-fpm.conf
+ sed -i -e 's#<MAX_START_SERVERS>##g' /etc/php7/php-fpm.conf
+ sed -i -e 's#<MIN_SPARE_SERVERS>##g' /etc/php7/php-fpm.conf
+ sed -i -e 's#<PHP_HOST>#>#g' /etc/nginx/conf.d/default.conf
+ sed -i -e 's#<PHP_HOST>##g' /etc/nginx/nginx.conf.d/php-fpm.conf
+ sed -i -e 's#<PHP_LISTEN_PORT>##g' /etc/nginx/nginx.conf.d/php-fpm.conf
+ sed -i -e 's#<PHP_LOG_LOCATION>##g' /etc/php7/php-fpm.conf
+ sed -i -e 's#<PHP_LOGFILE>##g' /etc/php7/php-fpm.conf
+ sed -i -e 's#<PHP_MEMORY_LIMIT>##g' /etc/php7/php-fpm.conf
+ sed -i -e 's#<PHP_TIMEOUT>##g' /etc/nginx/nginx.conf.d/php-fpm.conf
+ sed -i -e 's#<POST_MAX_SIZE>##g' /etc/php7/php-fpm.conf
+ sed -i -e 's#<PROCESS_MANAGER>##g' /etc/php7/php-fpm.conf
+ sed -i -e 's#<UPLOAD_MAX_SIZE>##g' /etc/php7/php-fpm.conf
+ sed -i -e 's#apc.shm_size.*#apc.shm_size=#g' /etc/php7/conf.d/apcu.ini
+ sed -i -e 's#opcache.memory_consumption.*#opcache.memory_consumption=#g' /etc/php7/conf.d/00_opcache.ini
+ sed -i -e 's#memory_limit = .*#memory_limit = #g' /etc/php7/php.ini
+ sed -i -e 's#max_input_time = .*#max_input_time = #g' /etc/php7/php.ini
+ sed -i -e 's#default_socket_timeout = .*#default_socket_timeout = #g' /etc/php7/php.ini
+ sed -i -e 's#post_max_size = .*#post_max_size = #g' /etc/php7/php.ini
+ sed -i -e 's#upload_max_filesize = .*#upload_max_filesize = #g' /etc/php7/php.ini
+ '[' '' = 0 ']'
+ '[' '' = 0 ']'
+ var_true
+ '[' '' = TRUE ']'
+ '[' '' = true ']'
+ var_true
+ '[' '' = TRUE ']'
+ '[' '' = true ']'
+ echo 'sendmail_path="/usr/bin/msmtp -C /etc/msmtprc -t "'
++ cat /etc/timezone
+ echo date.timezone=UTC
++ cat /etc/timezone
+ sed -i -e 's#date.timezone = .*#date.timezone = UTC#g' /etc/php7/php.ini
+ sed -i -e 's/<PHP_LOG_LEVEL>//g' /etc/php7/php-fpm.conf
+ mkdir -p
BusyBox v1.29.3 (2019-01-24 07:45:07 UTC) multi-call binary.
Usage: mkdir [OPTIONS] DIRECTORY...
Create DIRECTORY
-m MODE Mode
-p No error if exists; make parent directories as needed
+ chown -R nginx:www-data
BusyBox v1.29.3 (2019-01-24 07:45:07 UTC) multi-call binary.
Usage: chown [-RhLHPcvf]... USER[:[GRP]] FILE...
Change the owner and/or group of each FILE to USER and/or GRP
-R Recurse
-h Affect symlinks instead of symlink targets
-L Traverse all symlinks to directories
-H Traverse symlinks on command line only
-P Don't traverse symlinks (default)
-c List changed files
-v List all files
-f Hide errors
+ sed -i -e 's#<PHP_LOG_LOCATION>##g' /etc/logrotate.d/php-fpm
Still the same thing- Docker Hub is still rebuilding and seems to be on a loop. This is the slowest it's ever been.
Since version 2.4.0, when I start fusiondirectory, I get the following error:
Here are the logs:
Best,