@@ -19,7 +19,7 @@ The port is 3306. It exists inside the docker network so you can connect via `ma
1919
2020Before starting the stack, edit the ` docker-compose.yml ` file and check your environment variables. In particular:
2121
22- ``` yaml
22+ ```
2323 environment:
2424 - TZ=Etc/UTC
2525 - MYSQL_ROOT_PASSWORD=
@@ -36,7 +36,7 @@ You only get the opportunity to change the `MQSL_` prefixed environment variable
3636
3737 * Stop the container and remove the persistent storage area:
3838
39- ` ` ` console
39+ ```
4040 $ cd ~/IOTstack
4141 $ docker-compose rm --force --stop -v mariadb
4242 $ sudo rm -rf ./volumes/mariadb
@@ -45,7 +45,7 @@ You only get the opportunity to change the `MQSL_` prefixed environment variable
4545 * Edit `docker-compose.yml` and change the variables.
4646 * Bring up the container:
4747
48- ` ` ` console
48+ ```
4949 $ docker-compose up -d mariadb
5050 ```
5151
@@ -57,7 +57,7 @@ You only get the opportunity to change the `MQSL_` prefixed environment variable
5757
5858You can open a terminal session within the mariadb container via:
5959
60- ` ` ` console
60+ ```
6161$ docker exec -it mariadb bash
6262```
6363
@@ -98,7 +98,7 @@ Portainer's *Containers* display contains a *Status* column which shows health-c
9898
9999You can also use the ` docker ps ` command to monitor health-check results. The following command narrows the focus to mariadb:
100100
101- ` ` ` console
101+ ``` bash
102102$ docker ps --format " table {{.Names}}\t{{.Status}}" --filter name=mariadb
103103```
104104
@@ -169,7 +169,7 @@ You can customise the operation of the health-check agent by editing the `mariad
169169
170170To update the ` mariadb ` container:
171171
172- ` ` ` console
172+ ```
173173$ cd ~/IOTstack
174174$ docker-compose build --no-cache --pull mariadb
175175$ docker-compose up -d mariadb
0 commit comments