Reputation: 4783
I would like to run nginx and php-fpm on container start, however I can't seem to do that. Here is my Dockerfile
:
FROM php:7-fpm-alpine
EXPOSE 9080 8000
EXPOSE 9088 80
WORKDIR /var/www
COPY . .
RUN apk add nginx composer php7-fpm && \
composer install --no-progress && \
mkdir -p /etc/nginx /etc/nginx/sites-available /etc/nginx/sites-enabled /run/nginx && \
ln -s /etc/nginx/sites-available/default.conf /etc/nginx/sites-enabled/default.conf && \
cp nginx.conf /etc/nginx/conf.d/default.conf
CMD ["nginx", "-g", "daemon off;"]
Container comes up and running, however when I run ps aux
nginx is nowhere to be seen until I run nginx
command (configuration is okay, nginx -t
returns okay, and running it through open container does start the service).
I've tried to chain RUN php-fpm7 && nginx
but that does nothing.
Also using entrypoint like ENTRYPOINT ["nginx"]
did nothing for me.
How can I make sure those processes are running upon creating the container?
Upvotes: 4
Views: 10389
Reputation: 60074
Both answers are awesome, but As mentioned by @Efrat supervisorsd is more suitable for such cases.
One thing that I hate about copying thing during Docker build process, Dockerfile should be independent for copying thing I believe. It should be Dockerfile only that will build the Docker image, not other stuff they need to be copied. Just Extending @Efrat answer. Here you go with all configuration inside Dockerfile.
FROM php:7-fpm-alpine
WORKDIR /var/www
RUN apk add nginx composer php7-fpm supervisor && \
mkdir -p /etc/nginx /etc/nginx/sites-available /etc/nginx/sites-enabled /run/nginx && \
ln -s /etc/nginx/sites-available/default.conf /etc/nginx/sites-enabled/default.conf && \
# cp nginx.conf /etc/nginx/conf.d/default.conf && \
mkdir -p /etc/supervisord.d/
#supervisord basic config file
RUN echo $'[supervisord] \n\
[unix_http_server] \n\
file = /tmp/supervisor.sock \n\
chmod = 0777 \n\
chown= nobody:nogroup \n\
[supervisord] \n\
logfile = /tmp/supervisord.log \n\
logfile_maxbytes = 50MB \n\
logfile_backups=10 \n\
loglevel = info \n\
pidfile = /tmp/supervisord.pid \n\
nodaemon = true \n\
umask = 022 \n\
identifier = supervisor \n\
[supervisorctl] \n\
serverurl = unix:///tmp/supervisor.sock \n\
[rpcinterface:supervisor] \n\
supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface \n\
[include] \n\
files = /etc/supervisord.d/*.conf' >> /etc/supervisord.conf
# nginx supervisord Config
RUN echo $'[supervisord] \n\
nodaemon=true \n\
[program:nginx] \n\
command= /usr/sbin/nginx -g \'daemon off;\' \n\
stdout_logfile=/dev/fd/1 \n\
stdout_logfile_maxbytes=0MB \n\
stderr_logfile_maxbytes = 0 \n\
stderr_logfile=/dev/fd/2 \n\
redirect_stderr=true \n\
autorestart=false \n\
startretries=0 \n\
exitcodes=0 ' >> /etc/supervisord.d/nginx.conf
# php-fpm7
RUN echo $'[supervisord] \n\
nodaemon=true \n\
[program:php-fpm] \n\
command= /usr/sbin/php-fpm7 -F \n\
stdout_logfile=/dev/fd/1 \n\
stdout_logfile_maxbytes=0MB \n\
stderr_logfile_maxbytes = 0 \n\
stderr_logfile=/dev/fd/2 \n\
redirect_stderr=true \n\
autorestart=false \n\
startretries=0 \n\
exitcodes=0 ' >> /etc/supervisord.d/php-fpm.conf
EXPOSE 9080 8000 9088 80
ENTRYPOINT ["supervisord", "--nodaemon", "--configuration", "/etc/supervisord.conf"]
Upvotes: 1
Reputation: 5632
running 2 processes in the same container is not a docker best practice, but i assume it is the correct approach for your specific use-case. luckily docker has a solution for you.:
use a management tool - supervisord.
supervisord is designed for orchestrating multiple processes, and i consider it better than a shell script because its offering you the management and logging abilities. create a supervisord.conf
:
[supervisord]
nodaemon=true
logfile=/tmp/supervisord.log
childlogdir=/tmp
pidfile = /tmp/supervisord.pid
[program:php-fpm]
command=php-fpm7 -F
stdout_logfile=/dev/stdout
stdout_logfile_maxbytes=0
stderr_logfile=/dev/stderr
stderr_logfile_maxbytes=0
autorestart=false
startretries=0
[program:nginx]
command=nginx -g 'daemon off;'
stdout_logfile=/dev/stdout
stdout_logfile_maxbytes=0
stderr_logfile=/dev/stderr
stderr_logfile_maxbytes=0
autorestart=false
startretries=0
then install & copy it to your Dockerfile
:
RUN apk add supervisor
COPY ./supervisord.conf /etc/
now your entrypoint should be:
ENTRYPOINT /usr/bin/supervisord -c /etc/supervisord.conf
Upvotes: 9
Reputation: 18608
you can add a script and use it in your CMD
:
script :
#!/bin/bash
service nginx start
php-fpm7
add the script to your Dockerfile
:
COPY /PATH/TO/script.sh /path/in/container/script.sh
RUN chmod +x /path/in/container/script.sh
CMD ["/path/in/container/script.sh"]
Upvotes: 4