Bitnami DokuWiki

You've loaded an old revision of the document! If you save it, you will create a new version with this data.

In using docker compose to modernize some of my apps (including this wiki) I discovered some network awkwardness. The first problem I experienced was when I was setting up a new Wordpress, using the following docker-compose.yml:

<file yaml docker-compose.yml>
version: '3.3'

services:
   db:
     image: mysql:5.7
     volumes:
       - db_data:/var/lib/mysql
     restart: always
     environment:
       MYSQL_ROOT_PASSWORD: **********
       MYSQL_DATABASE: wordpress
       MYSQL_USER: wordpress
       MYSQL_PASSWORD: **********
   wordpress:
     depends_on:
       - db
     image: wordpress:latest
     ports:
       - "8000:80"
     restart: always
     environment:
       WORDPRESS_DB_HOST: db:3306
       WORDPRESS_DB_USER: wordpress
       WORDPRESS_DB_PASSWORD: **********
volumes:
    db_data:
</file>

<file yaml docker-compose.yml>
version: '3.3'

services:
   db:
     image: mysql:5.7
     networks:
       default:
         aliases:
           - wordpress.internal.com
     volumes:
       - db_data:/var/lib/mysql
     restart: always
     environment:
       MYSQL_ROOT_PASSWORD: **********
       MYSQL_DATABASE: wordpress
       MYSQL_USER: wordpress
       MYSQL_PASSWORD: **********
   wordpress:
     depends_on:
       - db
     image: wordpress:latest
     networks:
       default:
         aliases:
           - wordpress.internal.com
     ports:
       - "8000:80"
     restart: always
     environment:
       WORDPRESS_DB_HOST: db:3306
       WORDPRESS_DB_USER: wordpress
       WORDPRESS_DB_PASSWORD: **********
volumes:
    db_data:

networks:
  default:
    driver: bridge
    ipam:
      driver: default
      config:
      - subnet: 10.255.254.0/24
</file>

Edit summary

Note: By editing this page you agree to license your content under the following license: CC Attribution-Share Alike 4.0 International