If you need to build a community forum, try phpBB. First released in 2000, phpBB is a bulletin board solution that allows you to create forums and subforums. phpBB supports the notion of users and groups, file attachments, full-text search, notifications and more. Hundreds of modifications are available including themes, communications add-ons, spam management and more.

https://www.phpbb.com/

$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-phpbb/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d

• Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
• With Bitnami images the latest bug fixes and features are available as soon as possible.
• Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
• All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading linux distribution.
• Bitnami container images are released daily with the latest distribution packages available.

This CVE scan report contains a security report with all open CVEs. To get the list of actionable security issues, find the "latest" tag, click the vulnerability report link under the corresponding "Security scan" field and then select the "Only show fixable" filter on the next page.

Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the Bitnami phpBB Chart GitHub repository.

Bitnami containers can be used with Kubeapps for deployment and management of Helm Charts in clusters.

NOTE: Debian 8 images have been deprecated in favor of Debian 9 images. Bitnami will not longer publish new Docker images based on Debian 8.

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.

• 3-ol-7, 3.2.5-ol-7-r19 (3/ol-7/Dockerfile)
• 3-debian-9, 3.2.5-debian-9-r17, 3, 3.2.5, 3.2.5-r17, latest (3/debian-9/Dockerfile)

Subscribe to project updates by watching the bitnami/phpbb GitHub repo.

To run this application you need Docker Engine 1.10.0. Docker Compose is recomended with a version 1.6.0 or later.

Running phpBB with a database server is the recommended way. You can either use docker-compose or run the containers manually.

This is the recommended way to run phpBB. You can use the following docker compose template:

version: '2'
services:
  mariadb:
    image: 'bitnami/mariadb:latest'
    environment:
      - ALLOW_EMPTY_PASSWORD=yes
      - MARIADB_USER=bn_phpbb
      - MARIADB_DATABASE=bitnami_phpbb
    volumes:
      - 'mariadb_data:/bitnami'
  phpbb:
    image: 'bitnami/phpbb:3'
    labels:
      kompose.service.type: nodeport
    environment:
      - MARIADB_HOST=mariadb
      - MARIADB_PORT_NUMBER=3306
      - PHPBB_DATABASE_USER=bn_phpbb
      - PHPBB_DATABASE_NAME=bitnami_phpbb
      - ALLOW_EMPTY_PASSWORD=yes
    ports:
      - '80:80'
      - '443:443'
    volumes:
      - 'phpbb_data:/bitnami'
    depends_on:
      - mariadb
volumes:
  mariadb_data:
    driver: local
  phpbb_data:
    driver: local

If you want to run the application manually instead of using docker-compose, these are the basic steps you need to run:

1. Create a new network for the application and the database:

$ docker network create phpbb_network

2. Create a volume for MariaDB persistence and create a MariaDB container

$ docker volume create --name mariadb_data
$ docker run -d --name mariadb \
  -e ALLOW_EMPTY_PASSWORD=yes \
  -e MARIADB_USER=bn_phpbb \
  -e MARIADB_DATABASE=bitnami_phpbb \
  --net phpbb-tier \
  --volume mariadb_data:/bitnami \
  bitnami/mariadb:latest

Note: You need to give the container a name in order to phpBB to resolve the host

3. Create volumes for phpBB persistence and launch the container

$ docker volume create --name phpbb_data
$ docker run -d --name phpbb -p 80:80 -p 443:443 \
  -e ALLOW_EMPTY_PASSWORD=yes \
  -e PHPBB_DATABASE_USER=bn_phpbb \
  -e PHPBB_DATABASE_NAME=bitnami_phpbb \
  --net phpbb-tier \
  --volume phpbb_data:/bitnami \
  bitnami/phpbb:latest

Access your application at http://your-ip/

If you remove the container all your data and configurations will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.

For persistence you should mount a volume at the /bitnami path. Additionally you should mount a volume for persistence of the MariaDB data.

The above examples define docker volumes namely mariadb_data and phpbb_data. The phpBB application state will persist as long as these volumes are not removed.

To avoid inadvertent removal of these volumes you can mount host directories as data volumes. Alternatively you can make use of volume plugins to host the volume data.

This requires a minor change to the docker-compose.yml template previously shown:

version: '2'

services:
  mariadb:
    image: 'bitnami/mariadb:latest'
    environment:
      - ALLOW_EMPTY_PASSWORD=yes
      - MARIADB_USER=bn_phpbb
      - MARIADB_DATABASE=bitnami_phpbb
    volumes:
      - '/path/to/your/local/mariadb_data:/bitnami'
  phpbb:
    image: 'bitnami/phpbb:latest'
    depends_on:
      - mariadb
    ports:
      - '80:80'
      - '443:443'
    environment:
      - PHPBB_DATABASE_USER=bn_phpbb
      - PHPBB_DATABASE_NAME=bitnami_phpbb
      - ALLOW_EMPTY_PASSWORD=yes
    volumes:
      - '/path/to/phpbb-persistence:/bitnami'

In this case you need to specify the directories to mount on the run command. The process is the same than the one previously shown:

1. Create a network (if it does not exist):

$ docker network create phpbb-tier

2. Create a MariaDB container with host volume:

$ docker run -d --name mariadb \
  -e ALLOW_EMPTY_PASSWORD=yes \
  -e MARIADB_USER=bn_phpbb \
  -e MARIADB_DATABASE=bitnami_phpbb \
  --net phpbb-tier \
  --volume /path/to/mariadb-persistence:/bitnami \
  bitnami/mariadb:latest

Note: You need to give the container a name in order to phpBB to resolve the host

3. Create the phpBB container with host volumes:

$ docker run -d --name phpbb -p 80:80 -p 443:443 \
  -e ALLOW_EMPTY_PASSWORD=yes \
  -e PHPBB_DATABASE_USER=bn_phpbb \
  -e PHPBB_DATABASE_NAME=bitnami_phpbb \
  --net phpbb-tier \
  --volume /path/to/phpbb-persistence:/bitnami \
  bitnami/phpbb:latest

Bitnami provides up-to-date versions of MariaDB and phpBB, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container. We will cover here the upgrade of the phpBB container. For the MariaDB upgrade see https://github.com/bitnami/bitnami-docker-mariadb/blob/master/README.md#upgrade-this-image

1. Get the updated images:

$ docker pull bitnami/phpbb:latest

2. Stop your container

• For docker-compose: $ docker-compose stop phpbb
• For manual execution: $ docker stop phpbb

3. Take a snapshot of the application state

$ rsync -a /path/to/phpbb-persistence /path/to/phpbb-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)

Additionally, snapshot the MariaDB data

You can use these snapshots to restore the application state should the upgrade fail.

4. Remove the currently running container

• For docker-compose: $ docker-compose rm -v phpbb
• For manual execution: $ docker rm -v phpbb

5. Run the new image

• For docker-compose: $ docker-compose up phpbb
• For manual execution (mount the directories if needed): docker run --name phpbb bitnami/phpbb:latest

When you start the phpbb image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the docker run command line. If you want to add a new environment variable:

• For docker-compose add the variable name and value under the application section:

phpbb:
  image: bitnami/phpbb:latest
  ports:
    - 80:80
  environment:
    - PHPBB_PASSWORD=my_password

• For manual execution add a -e option with each variable and value:

 $ docker run -d -p 80:80 -p 443:443 --name phpbb \
  -e PHPBB_PASSWORD=my_password \
  --net phpbb-tier \
  --volume /path/to/phpbb-persistence:/bitnami \
  bitnami/phpbb:latest

Available variables:

• PHPBB_USERNAME: phpBB application username. Default: user
• PHPBB_PASSWORD: phpBB application password. Default: bitnami
• PHPBB_FIRST_NAME: Fist name of the user of the application. Default: User
• PHPBB_LAST_NAME: Last name of the user of the application. Default: Name
• PHPBB_FORUM_NAME: Forum Name. Default: My forum
• PHPBB_FORUM_DESCRIPTION: Forum Description. Default: A little text to describe your forum
• PHPBB_EMAIL: phpBB application email. Default: [email protected]
• PHPBB_HOST: phpBB application email. No defaults.

• MARIADB_HOST: Hostname for MariaDB server. Default: mariadb
• MARIADB_PORT_NUMBER: Port used by MariaDB server. Default: 3306
• PHPBB_DATABASE_NAME: Database name that phpBB will use to connect with the database. Default: bitnami_phpbb
• PHPBB_DATABASE_USER: Database user that phpBB will use to connect with the database. Default: bn_phpbb
• PHPBB_DATABASE_PASSWORD: Database password that Phpbb will use to connect with the database. No defaults.
• ALLOW_EMPTY_PASSWORD: It can be used to allow blank passwords. Default: no

• MARIADB_HOST: Hostname for MariaDB server. Default: mariadb
• MARIADB_PORT_NUMBER: Port used by MariaDB server. Default: 3306
• MARIADB_ROOT_USER: Database admin user. Default: root
• MARIADB_ROOT_PASSWORD: Database password for the MARIADB_ROOT_USER user. No defaults.
• MYSQL_CLIENT_CREATE_DATABASE_NAME: New database to be created by the mysql client module. No defaults.
• MYSQL_CLIENT_CREATE_DATABASE_USER: New database user to be created by the mysql client module. No defaults.
• MYSQL_CLIENT_CREATE_DATABASE_PASSWORD: Database password for the MYSQL_CLIENT_CREATE_DATABASE_USER user. No defaults.
• ALLOW_EMPTY_PASSWORD: It can be used to allow blank passwords. Default: no

To configure phpBB to send email using SMTP you can set the following environment variables:

• SMTP_HOST: SMTP host.
• SMTP_PORT: SMTP port.
• SMTP_USER: SMTP account user.
• SMTP_PASSWORD: SMTP account password.
• SMTP_PROTOCOL: SMTP protocol.

This would be an example of SMTP configuration using a GMail account:

• docker-compose:

  phpbb:
    image: bitnami/phpbb:latest
    ports:
      - 80:80
      - 443:443
    environment:
      - PHPBB_DATABASE_USER=bn_phpbb
      - PHPBB_DATABASE_NAME=bitnami_phpbb
      - SMTP_HOST=smtp.gmail.com
      - SMTP_PORT=587
      - [email protected]
      - SMTP_PASSWORD=your_password

• For manual execution:

$ docker run -d  -p 80:80 -p 443:443 --name phpbb \
  -e PHPBB_DATABASE_USER=bn_phpbb \
  -e PHPBB_DATABASE_NAME=bitnami_phpbb \
  -e SMTP_HOST=smtp.gmail.com \
  -e SMTP_PORT=587 \
  -e [email protected] \
  -e SMTP_PASSWORD=your_password
  --net phpbb-tier \
  --volume /path/to/phpbb-persistence:/bitnami \
  bitnami/phpbb:latest

We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.

If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:

• Host OS and version
• Docker version ($ docker version)
• Output of $ docker info
• Version of this container ($ echo $BITNAMI_IMAGE_VERSION inside the container)
• The command you used to run the container, and any relevant output you saw (masking any sensitive information)

Copyright 2016-2019 Bitnami

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.