Bobcares

Docker Nginx php-fpm Separate Containers | Guide

by | Jul 17, 2023

Learn more about Docker Nginx php-fpm Separate Containers from our experts. Our Docker Support team is here to help you with your questions and concerns.

Docker Nginx PHP-FPM Separate Containers | Guide

Containerization has changed the way we develop, deploy, and scale applications. Docker is a leading containerization platform. It lets us isolate applications into self-contained units with ease.

Docker Nginx PHP-FPM Separate Containers | Guide

Today, we are going to take a look at how to run NGINX and PHP-FPM in separate Docker containers. Let’s dive into the step-by-step process.

  1. First, we have to set up a Docker network by running the following command:

    docker network create newnetwork

  2. Next, we have to create a Dockerfile for the PHP-FPM container. Let’s take a look at an example:

    FROM php:latest
    RUN docker-php-ext-install mysqli pdo pdo_mysql
    COPY php-fpm.conf /usr/local/etc/php-fpm.d/www.conf

    The above example installs PHP and the necessary extensions. Additionally, it copies a custom PHP-FPM configuration file to the appropriate location.

  3. After that, we have to build the Docker image for the PHP-FPM container by running this command:

    docker build -t php-fpm .

  4. Then, we have to start the PHP-FPM container and attach it to the Docker network as seen below:

    docker run --name php-fpm --network=newnetwork -d php-fpm

  5. Next, we have to create an NGINX configuration file, nginx.conf, that points to the PHP-FPM container. Here’s an example of an nginx.conf file:


    nginx
    Copy code
    server {
    listen 80;
    server_name localhost;
    location / {
    proxy_pass http://php-fpm:9000;
    proxy_set_header Host $host;
    }
    }

  6. At this point, we have to start the NGINX container, map port 80, and attach it to the Docker network as seen below:

    docker run --name nginx --network=newnetwork -p 80:80 -v /path/to/nginx.conf:/etc/nginx/nginx.conf -d nginx

Now, we can check if the setup is working correctly by creating a PHP file with some PHP code to verify the connection between NGINX and PHP-FPM. Then, we have to place this file in a directory accessible by NGINX.

Now if everything is set up correctly, NGINX will pass the request to PHP-FPM, and the PHP code should execute successfully when we try to access the PHP file in a web browser using the IP or hostname of the Docker host.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Techs demonstrated how to run NGINX and PHP-FPM in separate Docker containers.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF