awesome-compose/nginx-golang-mysql
Madhu Kumar f51a8f8228
Update Dockerfile
Changes included in this PR
nginx-golang-mysql/backend/Dockerfile
I recommend upgrading to alpine:3.14, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Some of the most important vulnerabilities in your base image include:

Severity	Priority Score / 1000	Issue	Exploit Maturity
high severity	400	Improper Handling of Exceptional Conditions
SNYK-ALPINE312-BUSYBOX-1089799	No Known Exploit
high severity	400	Improper Handling of Exceptional Conditions
SNYK-ALPINE312-BUSYBOX-1089799	No Known Exploit
2022-02-19 22:01:55 +01:00
..
backend Update Dockerfile 2022-02-19 22:01:55 +01:00
db Move all samples to the root dir 2020-03-16 17:23:59 +01:00
proxy Move all samples to the root dir 2020-03-16 17:23:59 +01:00
docker-compose.yaml Arm64 and check Compose v2 support (#177) 2021-11-08 11:41:35 +01:00
README.md Arm64 and check Compose v2 support (#177) 2021-11-08 11:41:35 +01:00

Compose sample application

Go server with an Nginx proxy and a MySQL database

Project structure:

.
├── backend
│   ├── Dockerfile
│   ├── go.mod
│   └── main.go
├── db
│   └── password.txt
├── docker-compose.yaml
├── proxy
│   ├── conf
│   └── Dockerfile
└── README.md

docker-compose.yaml

services:
  backend:
    build: backend
    ...
  db:
    # We use a mariadb image which supports both amd64 & arm64 architecture
    image: mariadb:10.6.4-focal
    # If you really want to use MySQL, uncomment the following line
    #image: mysql:8.0.27
    ...
  proxy:
    build: proxy
    ports:
    - 80:80
    ...

The compose file defines an application with three services proxy, backend and db. When deploying the application, docker-compose maps port 80 of the proxy service container to port 80 of the host as specified in the file. Make sure port 80 on the host is not already being in use.

INFO
For compatibility purpose between AMD64 and ARM64 architecture, we use a MariaDB as database instead of MySQL.
You still can use the MySQL image by uncommenting the following line in the Compose file
#image: mysql:8.0.27

Deploy with docker-compose

$ docker-compose up -d
Creating network "nginx-golang-mysql_default" with the default driver
Building backend
Step 1/8 : FROM golang:1.13-alpine AS build
1.13-alpine: Pulling from library/golang
...
Successfully built 5f7c899f9b49
Successfully tagged nginx-golang-mysql_proxy:latest
WARNING: Image for service proxy was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
Creating nginx-golang-mysql_db_1 ... done
Creating nginx-golang-mysql_backend_1 ... done
Creating nginx-golang-mysql_proxy_1   ... done

Expected result

Listing containers must show three containers running and the port mapping as below:

$ docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                  NAMES
8906b14c5ad1        nginx-golang-mysql_proxy     "nginx -g 'daemon of…"   2 minutes ago       Up 2 minutes        0.0.0.0:80->80/tcp    nginx-golang-mysq
l_proxy_1
13e0e0a7715a        nginx-golang-mysql_backend   "/server"                2 minutes ago       Up 2 minutes        8000/tcp              nginx-golang-mysq
l_backend_1
ca8c5975d205        mysql:5.7                    "docker-entrypoint.s…"   2 minutes ago       Up 2 minutes        3306/tcp, 33060/tcp   nginx-golang-mysq
l_db_1

After the application starts, navigate to http://localhost:80 in your web browser or run:

$ curl localhost:80
["Blog post #0","Blog post #1","Blog post #2","Blog post #3","Blog post #4"]

Stop and remove the containers

$ docker-compose down