Docker Compose - Deploying WordPress to AWS

bogotobogo.com site search:

Introduction

In this post, we'll deploy Wordpress via docker-composer onto AWS EC2 instance (t2.micro) and access it with domain name (pykey.com) defined in Route53.

Docker install

These steps install Docker Community Edition (CE) using the official Ubuntu repositories (Install Docker Engine on Ubuntu).

Update the apt package index and make sure we have the necessary packages to allow the use of Docker's repository:

$ sudo apt-get update
    
$ sudo apt install apt-transport-https ca-certificates curl software-properties-common gnupg

Add Docker’s GPG key::

$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
OK

Verify that you now have the key with the fingerprint 9DC8 5822 9FC7 DD38 854A E2D8 8D81 803C 0EBF CD88, by searching for the last 8 characters of the fingerprint.:

$ sudo apt-key fingerprint 0EBFCD88
pub   4096R/0EBFCD88 2017-02-22
      Key fingerprint = 9DC8 5822 9FC7 DD38 854A  E2D8 8D81 803C 0EBF CD88
uid                  Docker Release (CE deb) <docker@docker.com>
sub   4096R/F273FCD8 2017-02-22

Add the stable Docker repository:

$ sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"

The "lsb_release -cs" sub-command below returns the name of your Ubuntu distribution, such as xenial.

To install Docker engine, we need to update the apt package index, and install the latest version of Docker Engine and containerd, or go to the next step to install a specific version:

$ sudo apt update
$ sudo apt-get install docker-ce docker-ce-cli containerd.io

Add a limited Linux user account to the "docker" group:

$ echo $USER 
ubuntu

$ sudo usermod -aG docker $USER

After entering the usermod command, we will need to close our SSH session and open a new one for this change to take effect. Then, check that the installation was successful by running the built-in "Hello World" program:

$ docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
0e03bdcc26d7: Pull complete 
Digest: sha256:4cf9c47f86df71d48364001ede3a4fcd85ae80ce02ebad74156906caff5378bc
Status: Downloaded newer image for hello-world:latest

Hello from Docker!
...

Install Docker Compose

Download the latest version of Docker Compose (Install Docker Compose). Run this command to download the current stable release of Docker Compose:

$ sudo curl -L "https://github.com/docker/compose/releases/download/1.27.4/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose

Apply executable permissions to the binary:

$ sudo chmod +x /usr/local/bin/docker-compose

Wordpress setup

Here is our docker-compose.yaml file:

version: '3.7'
services:
  db:
    image: mysql:8.0.19
    restart: always
    volumes:
      - db_data:/var/lib/mysql
    restart: always
    environment:
      - MYSQL_ROOT_PASSWORD=wordpress
      - MYSQL_DATABASE=wordpress
      - MYSQL_USER=wordpress
      - MYSQL_PASSWORD=wordpress
  wordpress:
    depends_on:
      - db
    image: wordpress:latest
    ports:
      - 80:80
    restart: always
    environment:
      - WORDPRESS_DB_HOST=db
      - WORDPRESS_DB_USER=wordpress
      - WORDPRESS_DB_PASSWORD=wordpress
      - WORDPRESS_DB_NAME=wordpress
volumes:
  db_data:

Start the docker containers:

$ docker-compose up -d  

$ docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                 NAMES
837ee8e228ca        wordpress:latest    "docker-entrypoint.s…"   About an hour ago   Up About an hour    0.0.0.0:80->80/tcp    wordpress_wordpress_1
a91d5df8c534        mysql:8.0.19        "docker-entrypoint.s…"   About an hour ago   Up About an hour    3306/tcp, 33060/tcp   wordpress_db_1

ubuntu@ip-172-31-24-196:/var/lib$

Wordpress

Access the Wordpress using the domain name, pykey.com:

Optional 1 - EIP

We may want to attach EIP to the instance.

Optional 2 - symlink for /var/lib/docker/volumes

We may want to persist DB data in a separate volume so that we can recover it in case for an accidental termination of the instance.

We need to format and mount it:

root@ip-172-31-24-196:~# lsblk
NAME    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
loop0     7:0    0 28.1M  1 loop /snap/amazon-ssm-agent/2012
loop1     7:1    0 96.6M  1 loop /snap/core/9804
loop2     7:2    0 55.3M  1 loop /snap/core18/1885
loop3     7:3    0 70.6M  1 loop /snap/lxd/16922
loop4     7:4    0 97.8M  1 loop /snap/core/10185
xvda    202:0    0    8G  0 disk 
└─xvda1 202:1    0    8G  0 part /
xvdf    202:80   0   10G  0 disk     

root@ip-172-31-24-196:~# fdisk -l
...
Disk /dev/xvdf: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

root@ip-172-31-24-196:~# mkfs.xfs /dev/xvdf
meta-data=/dev/xvdf              isize=512    agcount=4, agsize=655360 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=0
         =                       reflink=1
data     =                       bsize=4096   blocks=2621440, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
log      =internal log           bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0

root@ip-172-31-24-196:~# mkdir /vol
root@ip-172-31-24-196:~# mount /dev/xvdf /vol

root@ip-172-31-24-196:~# lsblk
NAME    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
loop0     7:0    0 28.1M  1 loop /snap/amazon-ssm-agent/2012
loop1     7:1    0 96.6M  1 loop /snap/core/9804
loop2     7:2    0 55.3M  1 loop /snap/core18/1885
loop3     7:3    0 70.6M  1 loop /snap/lxd/16922
loop4     7:4    0 97.8M  1 loop /snap/core/10185
xvda    202:0    0    8G  0 disk 
└─xvda1 202:1    0    8G  0 part /
xvdf    202:80   0   10G  0 disk /vol

root@ip-172-31-24-196:~# cp /etc/fstab /etc/fstab.orig

root@ip-172-31-24-196:~# echo "/dev/xvdf /vol auto noatime 0 0" | sudo tee -a /etc/fstab
/dev/xvdf /vol auto noatime 0 0

Then, we need to move it to the attached volume, and then create a symlink.

# cd /var/lib/docker

root@ip-172-31-24-196:/var/lib/docker# ls
builder  buildkit  containers  image  network  overlay2  plugins  runtimes  swarm  tmp  trust  volumes

root@ip-172-31-24-196:/var/lib/docker# mv volumes /vol/volumes

root@ip-172-31-24-196:/var/lib/docker# ln -s /vol/volumes volumes

root@ip-172-31-24-196:/var/lib/docker# ls -la
total 52
drwx--x--x 13 root root 4096 Oct 24 01:10 .
drwxr-xr-x 40 root root 4096 Oct 10 03:21 ..
drwx------  2 root root 4096 Oct 10 03:21 builder
drwx--x--x  4 root root 4096 Oct 10 03:21 buildkit
drwx------  3 root root 4096 Oct 24 00:45 containers
drwx------  3 root root 4096 Oct 10 03:21 image
drwxr-x---  3 root root 4096 Oct 10 03:21 network
drwx------ 38 root root 4096 Oct 24 00:45 overlay2
drwx------  4 root root 4096 Oct 10 03:21 plugins
drwx------  2 root root 4096 Oct 23 23:42 runtimes
drwx------  2 root root 4096 Oct 10 03:21 swarm
drwx------  2 root root 4096 Oct 23 23:42 tmp
drwx------  2 root root 4096 Oct 10 03:21 trust
lrwxrwxrwx  1 root root   12 Oct 24 01:10 volumes -> /vol/volumes

root@ip-172-31-24-196:/var/lib/docker# ls -la /vol/volumes
total 24
drwx------ 4 root root   122 Oct 24 03:29 .
drwxr-xr-x 3 root root    21 Oct 24 04:04 ..
drwxr-xr-x 3 root root    19 Oct 24 03:29 cc5fa27d07f934d0226730ff4e3a741cdd7bc0624786635fb80151fdb4119278
-rw------- 1 root root 32768 Oct 24 03:29 metadata.db
drwxr-xr-x 3 root root    19 Oct 24 03:28 wordpress_db_data

Let's check if the docker-compose works:

ubuntu@ip-172-31-24-196:~/WordPress$ ls -la
total 16
drwxrwxr-x 2 ubuntu ubuntu 4096 Oct 24 01:05 .
drwxr-xr-x 5 ubuntu ubuntu 4096 Oct 24 00:43 ..
-rw-rw-r-- 1 ubuntu ubuntu  653 Oct 24 00:41 docker-compose.yaml

ubuntu@ip-172-31-24-196:~/WordPress$ docker-compose up -d
Creating network "wordpress_default" with the default driver
Creating wordpress_db_1 ... done
Creating wordpress_wordpress_1 ... done