- \n
- A server running Ubuntu 24.04 <\/a>or any Linux OS<\/li>\n\n\n\n
- User privileges: root or non-root user with sudo privileges<\/li>\n\n\n\n
- Domain name with A record pointed to the server IP address<\/li>\n<\/ul>\n\n\n\n
Step 1. Update the System<\/h2>\n\n\n\n
We assume that you have a fresh Ubuntu 24.04 OS. Before we start with installing any dependencies we need to update the system packages. To do that execute the following command:<\/p>\n\n\n\n
sudo apt update -y && sudo apt upgrade -y<\/pre>\n\n\n\n
Step 2. Install Docker<\/h2>\n\n\n\n
There are a couple of steps for us can install the Docker and start its service. Firstly, we need to install the Docker dependencies:<\/p>\n\n\n\n
sudo apt install software-properties-common apt-transport-https ca-certificates -y<\/pre>\n\n\n\n
Secondly, we need to add the Docker GPG key:<\/p>\n\n\n\n
curl -fsSL https:\/\/download.docker.com\/linux\/ubuntu\/gpg | sudo gpg --dearmor -o \/usr\/share\/keyrings\/docker-archive-keyring.gpg<\/pre>\n\n\n\n
Thirdly, after the key is added we need to add the repo:<\/p>\n\n\n\n
echo \"deb [arch=amd64 signed-by=\/usr\/share\/keyrings\/docker-archive-keyring.gpg] https:\/\/download.docker.com\/linux\/ubuntu $(lsb_release -cs) stable\" | sudo tee \/etc\/apt\/sources.list.d\/docker.list > \/dev\/null<\/pre>\n\n\n\n
Once the repo is added, update the system and install Docker:<\/p>\n\n\n\n
\nsudo apt update -y\n\nsudo apt install docker-ce docker-ce-cli containerd.io -y\n<\/pre>\n\n\n\n
After the installation start and enable the Docker service:<\/p>\n\n\n\n
sudo systemctl start docker && sudo systemctl enable docker<\/pre>\n\n\n\n
To check the status of the Docker service execute the command below:<\/p>\n\n\n\n
sudo systemctl status docker<\/pre>\n\n\n\n
If you did everything correctly, you should get the following output:<\/p>\n\n\n\n
root@host:~# sudo systemctl status docker\n\u25cf docker.service - Docker Application Container Engine\n Loaded: loaded (\/usr\/lib\/systemd\/system\/docker.service; enabled; preset: enabled)\n Active: active (running) since Fri 2024-12-06 18:43:10 CST; 5min ago\nTriggeredBy: \u25cf docker.socket\n Docs: https:\/\/docs.docker.com\n Main PID: 9781 (dockerd)\n Tasks: 9\n Memory: 20.4M (peak: 21.1M)\n CPU: 889ms\n CGroup: \/system.slice\/docker.service\n \u2514\u25009781 \/usr\/bin\/dockerd -H fd:\/\/ --containerd=\/run\/containerd\/containerd.sock\n<\/pre>\n\n\n\n
Step 3. Install Docker Compose<\/h2>\n\n\n\n
Docker Composer is a tool for managing multi-container Docker applications. We need this feature since this installation will be with two different containers. One is for WordPress application using the WordPress Docker Image and the other is for MySQL database using the MySQL docker image.<\/p>\n\n\n\n
To install Docker Compose execute the command below:<\/p>\n\n\n\n
sudo curl -L \"https:\/\/github.com\/docker\/compose\/releases\/download\/v2.24.7\/docker-compose-$(uname -s)-$(uname -m)\" -o \/usr\/local\/bin\/docker-compose<\/pre>\n\n\n\n
Now, grant permissions to all users for the docker-compose to be executable:<\/p>\n\n\n\n
sudo chmod +x \/usr\/local\/bin\/docker-compose<\/pre>\n\n\n\n
If everything is OK, check the docker-compose version with the command below:<\/p>\n\n\n\n
docker-compose --version<\/pre>\n\n\n\n
You should get output similar to this:<\/p>\n\n\n\n
root@host:~# docker-compose --version\nDocker Compose version v2.24.7\n<\/pre>\n\n\n\n
Step 4. Install WordPress with Docker Compose<\/h2>\n\n\n\n
Firstly, we need to create WordPress directory<\/strong>, and navigate to that directory. In that directory, we will place all docker files.<\/p>\n\n\n\n
cd \/opt\n\nmkdir wordpress\/\n\ncd wordpress\/\n<\/pre>\n\n\n\n
Once the wordpress directory is created, inside it create the following directory and file:<\/p>\n\n\n\n
mkdir nginx-conf\n\ntouch nginx-conf\/nginx.conf\n<\/pre>\n\n\n\n
Open the nginx.conf<\/strong> file with your favorite editor and paste the following lines of code:<\/p>\n\n\n\n
server {\n listen 80;\n listen [::]:80;\n\n server_name docker.rosehostingtest.com;\n\n index index.php index.html index.htm;\n\n root \/var\/www\/html;\n\n location ~ \/.well-known\/acme-challenge {\n allow all;\n root \/var\/www\/html;\n }\n\n location \/ {\n try_files $uri $uri\/ \/index.php$is_args$args;\n }\n\n location ~ \\.php$ {\n try_files $uri =404;\n fastcgi_split_path_info ^(.+\\.php)(\/.+)$;\n fastcgi_pass wordpress:9000;\n fastcgi_index index.php;\n include fastcgi_params;\n fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;\n fastcgi_param PATH_INFO $fastcgi_path_info;\n }\n\n location ~ \/\\.ht {\n deny all;\n }\n\n location = \/favicon.ico {\n log_not_found off; access_log off;\n }\n location = \/robots.txt {\n log_not_found off; access_log off; allow all;\n }\n location ~* \\.(css|gif|ico|jpeg|jpg|js|png)$ {\n expires max;\n log_not_found off;\n }\n}\n<\/pre>\n\n\n\nDo not forget to change our domain docker.rosehostingtest.com<\/strong> in the server_name<\/strong> directive with your domain name.<\/p>\n\n\n\n
Next is to create a Docker Compose YAML file that will contain WordPress docker image<\/strong>, MySQL docker image<\/strong>, and Webserver Docker Image<\/strong>. To do that execute the command below:<\/p>\n\n\n\n
touch docker-compose.yml<\/pre>\n\n\n\n
Open the file with yout favorite editor and paste the following lines of code:<\/p>\n\n\n\n
version: '3'
services:
db:
image: mysql:8.0
container_name: db
restart: unless-stopped
environment:
- MYSQL_ROOT_PASSWORD=MySQLRootPassword
- MYSQL_USER=wpuser
- MYSQL_PASSWORD=YourStrongPasswordHere
- MYSQL_DATABASE=wpdb
volumes:
- dbdata:\/var\/lib\/mysql
command: '--default-authentication-plugin=mysql_native_password'
networks:
- app-network
wordpress:
depends_on:
- db
image: wordpress:php8.3-fpm-alpine
container_name: wordpress
restart: unless-stopped
environment:
- WORDPRESS_DB_HOST=db:3306
- WORDPRESS_DB_USER=wpuser
- WORDPRESS_DB_PASSWORD=YourStrongPasswordHere
- WORDPRESS_DB_NAME=wpdb
volumes:
- wordpress:\/var\/www\/html
networks:
- app-network
webserver:
depends_on:
- wordpress
image: nginx:1.15.12-alpine
container_name: webserver
restart: unless-stopped
ports:
- \"80:80\"
volumes:
- wordpress:\/var\/www\/html
- .\/nginx-conf:\/etc\/nginx\/conf.d
networks:
- app-network
volumes:
wordpress:
dbdata:
networks:
app-network:
driver: bridge
<\/pre>\n\n\n\nSave the file and close it.<\/p>\n\n\n\n
Next step is to start the service with the following command:<\/p>\n\n\n\n
sudo docker-compose up -d<\/pre>\n\n\n\n
![\"\"](\"https:\/\/www.linuxcloudvps.com\/blog\/wp-content\/uploads\/2024\/12\/dock1-970x772.png\")
<\/a><\/figure>\n\n\n\nOnce, the images and volumes are created you should receive the following output:<\/p>\n\n\n\n
![\"\"](\"https:\/\/www.linuxcloudvps.com\/blog\/wp-content\/uploads\/2024\/12\/dock2-970x148.png\")
<\/a><\/figure>\n\n\n\nTo check the started containers with more info you can execute the following command:<\/p>\n\n\n\n
docker ps<\/pre>\n\n\n\n
You should receive the followiong output:<\/p>\n\n\n\n
root@host:\/opt\/wordpress# docker ps\nCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES\n2ba8f3b94cdf nginx:1.15.12-alpine \"nginx -g 'daemon of\u2026\" 4 minutes ago Up 4 minutes 0.0.0.0:80->80\/tcp, :::80->80\/tcp, 0.0.0.0:443->443\/tcp, :::443->443\/tcp webserver\ned8416fecb34 wordpress:php8.3-fpm-alpine \"docker-entrypoint.s\u2026\" 4 minutes ago Up 4 minutes 9000\/tcp wordpress\n5148e233d9ed mysql:8.0 \"docker-entrypoint.s\u2026\" 4 minutes ago Up 4 minutes 3306\/tcp, 33060\/tcp\n<\/pre>\n\n\n\n
Step 5. Finish the WordPress Installation<\/h2>\n\n\n\n
To finish the WordPress installation access your domain in the browser you set in Step. 4 In our blog post we need to access the http:\/\/docker.rosehostingtest.com<\/strong><\/p>\n\n\n\n
![\"\"](\"https:\/\/www.linuxcloudvps.com\/blog\/wp-content\/uploads\/2024\/12\/dock3.png\")
<\/a><\/figure>\n\n\n\nSelect your language anc click on the Continue<\/strong>. On the next window, create WordPress credentials for future use.<\/p>\n\n\n\n
![\"\"](\"https:\/\/www.linuxcloudvps.com\/blog\/wp-content\/uploads\/2024\/12\/dock4.png\")
<\/a><\/figure>\n\n\n\nOnce done, click on Install WordPress<\/strong>. Once the installation is complete you will receive the following output:<\/p>\n\n\n\n
![\"\"](\"https:\/\/www.linuxcloudvps.com\/blog\/wp-content\/uploads\/2024\/12\/dock5.png\")
<\/a><\/figure>\n\n\n\nClick on Log In<\/strong> and fill the credentials you set before:<\/p>\n\n\n\n
![\"\"](\"https:\/\/www.linuxcloudvps.com\/blog\/wp-content\/uploads\/2024\/12\/dock6.png\")
<\/a><\/figure>\n\n\n\nOnce logged in you will be redirected to the WordPress admin dashboard:<\/p>\n\n\n\n
![\"\"](\"https:\/\/www.linuxcloudvps.com\/blog\/wp-content\/uploads\/2024\/12\/dock7-970x457.png\")
<\/a><\/figure>\n\n\n\nStep 6. Install SSL certificate with Certbot Image<\/h2>\n\n\n\n
This step is optional, since the website may work without an SSL certificate. But if you want to access it securely via HTTPS protocol, follow the steps below.<\/p>\n\n\n\n
We need to make changes into the docker-compose.yml<\/strong> and nginx-conf\/nginx.conf<\/strong> files.<\/p>\n\n\n\n
Into the docker-compose.yml<\/strong> we need to add a new block for the certbot image, assign volume for that image, and modify the webserver block. To that open the docker-compose.yml file add the – certbot-etc:\/etc\/letsencrypt<\/strong> in the webserver volumes list and the volumes block. It should look like this:<\/p>\n\n\n\n
webserver:
depends_on:
- wordpress
image: nginx:1.15.12-alpine
container_name: webserver
restart: unless-stopped
ports:
- \"80:80\"
volumes:
- wordpress:\/var\/www\/html
- .\/nginx-conf:\/etc\/nginx\/conf.d
- certbot-etc:\/etc\/letsencrypt<\/strong>
networks:
- app-network
certbot:
depends_on:
- webserver
image: certbot\/certbot
container_name: certbot
volumes:
- certbot-etc:\/etc\/letsencrypt
- wordpress:\/var\/www\/html
command: certonly --webroot --webroot-path=\/var\/www\/html --email admin@docker.rosehostingtest.com --agree-tos --no-eff-email --dry-run -d docker.rosehostingtest.com<\/strong>
volumes:
certbot-etc:<\/strong>
wordpress:
dbdata:
<\/pre>\n\n\n\nSave the file, and close it.<\/p>\n\n\n\n
Since the changes are made in the webserver (wordpress docker image) and a new certbot block is added we need to reload the webserver and start the newly added certbot image. To do that we can execute this simple command:<\/p>\n\n\n\n
docker-compose up -d --force-recreate --no-deps webserver certbot<\/pre>\n\n\n\n
![\"\"](\"https:\/\/www.linuxcloudvps.com\/blog\/wp-content\/uploads\/2024\/12\/dock8-970x234.png\")
<\/a><\/figure>\n\n\n\nOnce the webserver container is recreated and the certbot container is created, we need to check the log of the newly created container:<\/p>\n\n\n\n
docker logs certbot<\/pre>\n\n\n\n
If the container is up and runnnig and the –dry-run is successfull (usually the process may take up to 1 minute) you should get the following output:<\/p>\n\n\n\n
root@host:\/opt\/wordpress# docker logs certbot\nSaving debug log to \/var\/log\/letsencrypt\/letsencrypt.log\nSimulating a certificate request for docker.rosehostingtest.com\nThe dry run was successful.\n<\/pre>\n\n\n\n
Now, we can remove the –dry-run<\/strong> option from the certbot image to generate an SSL certificate for our domain. The line in the certbot image should look like this:<\/p>\n\n\n\n
command: certonly --webroot --webroot-path=\/var\/www\/html --email admin@docker.rosehostingtest.com --agree-tos --no-eff-email -d docker.rosehostingtest.com<\/strong>
<\/pre>\n\n\n\nSave the file, close it and recreate the certbot image.<\/p>\n\n\n\n
docker-compose up -d --force-recreate --no-deps certbot<\/pre>\n\n\n\n
Check the logs of the certbot image again:<\/p>\n\n\n\n
docker logs certbot<\/pre>\n\n\n\n
If everything is OK, with the SSL certificate you should get the following output:<\/p>\n\n\n\n
root@host:\/opt\/wordpress# docker logs certbot\nSaving debug log to \/var\/log\/letsencrypt\/letsencrypt.log\nAccount registered.\nRequesting a certificate for docker.rosehostingtest.com\nroot@host:\/opt\/wordpress# docker logs certbot\nSaving debug log to \/var\/log\/letsencrypt\/letsencrypt.log\nAccount registered.\nRequesting a certificate for docker.rosehostingtest.com\n\nSuccessfully received certificate.\nCertificate is saved at: \/etc\/letsencrypt\/live\/docker.rosehostingtest.com\/fullchain.pem\nKey is saved at: \/etc\/letsencrypt\/live\/docker.rosehostingtest.com\/privkey.pem\nThis certificate expires on 2025-03-08.\nThese files will be updated when the certificate renews.\nNEXT STEPS:\n- The certificate will need to be renewed before it expires. Certbot can automatically renew the certificate in the background, but you may need to take steps to enable that functionality. See https:\/\/certbot.org\/renewal-setup for instructions.\n\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\nIf you like Certbot, please consider supporting our work by:\n * Donating to ISRG \/ Let's Encrypt: https:\/\/letsencrypt.org\/donate\n * Donating to EFF: https:\/\/eff.org\/donate-le\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n<\/pre>\n\n\n\n
This means, that the SSL certificate is generated, and the key along with the certificate is located at:<\/p>\n\n\n\n
Certificate is saved at: \/etc\/letsencrypt\/live\/docker.rosehostingtest.com\/fullchain.pem\nKey is saved at: \/etc\/letsencrypt\/live\/docker.rosehostingtest.com\/privkey.pem\n<\/pre>\n\n\n\n
Now, we need to make some changes into the nginx-conf\/nginx.conf<\/strong> file. First execute the following command to get the recommend Nginx security parameter for certbot:<\/p>\n\n\n\n
curl -sSLo nginx-conf\/options-ssl-nginx.conf https:\/\/raw.githubusercontent.com\/certbot\/certbot\/master\/certbot-nginx\/certbot_nginx\/_internal\/tls_configs\/options-ssl-nginx.conf<\/pre>\n\n\n\n
Next open the nginx-conf\/nginx.conf file to add the server block for port 443 along with the SSL certificate paths. The content should look like this:<\/p>\n\n\n\n
server {\n listen 80;\n listen [::]:80;\n\n server_name docker.rosehostingtest.com;\n\n location ~ \/.well-known\/acme-challenge {\n allow all;\n root \/var\/www\/html;\n }\n\n location \/ {\n rewrite ^ https:\/\/$host$request_uri? permanent;\n }\n}\n\nserver {\n listen 443 ssl http2;\n listen [::]:443 ssl http2;\n server_name docker.rosehostingtest.com;\n\n index index.php index.html index.htm;\n\n root \/var\/www\/html;\n\n server_tokens off;\n\n ssl_certificate \/etc\/letsencrypt\/live\/docker.rosehostingtest.com\/fullchain.pem;\n ssl_certificate_key \/etc\/letsencrypt\/live\/docker.rosehostingtest.com\/privkey.pem;\n\n include \/etc\/nginx\/conf.d\/options-ssl-nginx.conf;\n <\/strong>\n add_header X-Frame-Options \"SAMEORIGIN\" always;\n add_header X-XSS-Protection \"1; mode=block\" always;\n add_header X-Content-Type-Options \"nosniff\" always;\n add_header Referrer-Policy \"no-referrer-when-downgrade\" always;\n add_header Content-Security-Policy \"default-src * data: 'unsafe-eval' 'unsafe-inline'\" always;\n # add_header Strict-Transport-Security \"max-age=31536000; includeSubDomains; preload\" always;\n # enable strict transport security only if you understand the implications\n\n location \/ {\n try_files $uri $uri\/ \/index.php$is_args$args;\n }\n\n location ~ \\.php$ {\n try_files $uri =404;\n fastcgi_split_path_info ^(.+\\.php)(\/.+)$;\n fastcgi_pass wordpress:9000;\n fastcgi_index index.php;\n include fastcgi_params;\n fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;\n fastcgi_param PATH_INFO $fastcgi_path_info;\n }\n\n location ~ \/\\.ht {\n deny all;\n }\n\n location = \/favicon.ico {\n log_not_found off; access_log off;\n }\n location = \/robots.txt {\n log_not_found off; access_log off; allow all;\n }\n location ~* \\.(css|gif|ico|jpeg|jpg|js|png)$ {\n expires max;\n log_not_found off;\n }\n}\n<\/pre>\n\n\n\nSave the file and close it.<\/p>\n\n\n\n