What is Joomla?

Joomla! is a PHP content management system (CMS) for publishing web content. It includes features such as page caching, RSS feeds, printable versions of pages, news flashes, blogs, search, and support for non-english languages.

https://www.joomla.org/

TL;DR;

Docker Compose

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

Why use Bitnami Images?

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.
All Bitnami images available in Docker Hub are signed with Docker Content Trust (DTC). You can use DOCKER_CONTENT_TRUST=1 to verify the integrity of the images.
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.

How to deploy Joomla in Kubernetes?

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 Joomla Chart GitHub repository.

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

Supported tags and respective `Dockerfile` links

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.

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

Prerequisites

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

How to use this image

Run Joomla with a Database Container

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

Run the application using Docker Compose

The main folder of this repository contains a functional docker-compose.yml file. Run the application using it as shown below:

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

Run the application manually

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

Create a new network for the application and the database:

$ docker network create joomla-tier

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_joomla \
  -e MARIADB_DATABASE=bitnami_joomla \
  --net joomla-tier \
  --volume mariadb_data:/bitnami \
  bitnami/mariadb:latest

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

Create volumes for Joomla persistence and launch the container

$ docker volume create --name joomla_data
$ docker run -d --name joomla -p 80:80 -p 443:443 \
  -e ALLOW_EMPTY_PASSWORD=yes \
  -e JOOMLA_DATABASE_USER=bn_joomla \
  -e JOOMLA_DATABASE_NAME=bitnami_joomla \
  --net joomla-tier \
  --volume joomla_data:/bitnami \
  bitnami/joomla:latest

Then you can access your application at http://your-ip/

Persisting your application

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 joomla_data. The Joomla 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.

Mount host directories as data volumes with Docker Compose

This requires a minor change to the docker-compose.yml file present in this repository:

mariadb:
  ...
  volumes:
    - '/path/to/mariadb_persistence:/bitnami'
  ...
joomla:
  ...
  volumes:
    - '/path/to/joomla-persistence:/bitnami'
  ...

Mount host directories as data volumes using the Docker command line

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:

Create a network (if it does not exist):

$ docker network create joomla-tier

Create a MariaDB container with host volume:

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

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

Create the Joomla container with host volumes:

$ docker run -d --name joomla -p 80:80 -p 443:443 \
  -e ALLOW_EMPTY_PASSWORD=yes \
  -e JOOMLA_DATABASE_USER=bn_joomla \
  -e JOOMLA_DATABASE_NAME=bitnami_joomla \
  --net joomla-tier \
  --volume /path/to/joomla-persistence:/bitnami \
  bitnami/joomla:latest

Upgrade this application

Bitnami provides up-to-date versions of MariaDB and Joomla, 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 Joomla container. For the MariaDB upgrade see https://github.com/bitnami/bitnami-docker-mariadb/blob/master/README.md#upgrade-this-image

Get the updated images:

$ docker pull bitnami/joomla:latest

Stop your container

For docker-compose: $ docker-compose stop joomla
For manual execution: $ docker stop joomla

Take a snapshot of the application state

$ rsync -a /path/to/joomla-persistence /path/to/joomla-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.

Remove the currently running container

For docker-compose: $ docker-compose rm -v joomla
For manual execution: $ docker rm -v joomla

Run the new image

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

You need to complete the upgrade from the browser to get latest Joomla version.

Configuration

Environment variables

When you start the Joomla! 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.

User and Site configuration

JOOMLA_USERNAME: Joomla application username. Default: user
JOOMLA_PASSWORD: Joomla application password. Default: bitnami
JOOMLA_EMAIL: Joomla application email. Default: [email protected]

Use an existing database

MARIADB_HOST: Hostname for MariaDB server. Default: mariadb
MARIADB_PORT_NUMBER: Port used by MariaDB server. Default: 3306
JOOMLA_DATABASE_NAME: Database name that Joomla! will use to connect with the database. Default: bitnami_joomla
JOOMLA_DATABASE_USER: Database user that Joomla! will use to connect with the database. Default: bn_joomla
JOOMLA_DATABASE_PASSWORD: Database password that Joomla! will use to connect with the database. No defaults.
ALLOW_EMPTY_PASSWORD: It can be used to allow blank passwords. Default: no

Create a database for Joomla! using mysql-client

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

If you want to add a new environment variable:

For Docker Compose add the variable name and value under the application section:

joomla:
  ...
  environment:
    - JOOMLA_PASSWORD=my_password
  ...

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

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

SMTP Configuration

To configure Joomla 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:

Modify the docker-compose.yml file present in this repository:

  joomla:
  ...
    environment:
      - MARIADB_HOST=mariadb
      - MARIADB_PORT_NUMBER=3306
      - JOOMLA_DATABASE_USER=bn_joomla
      - JOOMLA_DATABASE_NAME=bitnami_joomla
      - SMTP_HOST=smtp.gmail.com
      - SMTP_PORT=587
      - [email protected]
      - SMTP_PASSWORD=your_password
  ...

For manual execution:

$ docker run -d --name joomla -p 80:80 -p 443:443 \
  -e MARIADB_HOST=mariadb \
  -e MARIADB_PORT_NUMBER=3306 \
  -e JOOMLA_DATABASE_USER=bn_joomla \
  -e JOOMLA_DATABASE_NAME=bitnami_joomla \
  -e SMTP_HOST=smtp.gmail.com \
  -e SMTP_PORT=587 \
  -e [email protected] \
  -e SMTP_PASSWORD=your_password
  --net joomla-tier \
  --volume /path/to/joomla-persistence:/bitnami \
  bitnami/joomla:latest

Customize this image

The Bitnami Joomla! Docker image is designed to be extended so it can be used as the base image for your custom web applications.

Extend this image

Before extending this image, please note there are certain configuration settings you can modify using the original image:

Settings that can be adapted using environment variables. For instance, you can change the ports used by Apache for HTTP and HTTPS, by setting the environment variables APACHE_HTTP_PORT_NUMBER and APACHE_HTTPS_PORT_NUMBER respectively.
Adding custom virtual hosts.
Replacing the 'httpd.conf' file.
Using custom SSL certificates.

If your desired customizations cannot be covered using the methods mentioned above, extend the image. To do so, create your own image using a Dockerfile with the format below:

FROM bitnami/joomla
## Put your customizations below
...

Here is an example of extending the image with the following modifications:

Install the vim editor
Modify the Apache configuration file
Modify the ports used by Apache

FROM bitnami/joomla
LABEL maintainer "Bitnami <[email protected]>"

## Install 'vim'
RUN install_packages vim

## Enable mod_ratelimit module
RUN sed -i -r 's/#LoadModule ratelimit_module/LoadModule ratelimit_module/' /opt/bitnami/apache/conf/httpd.conf

## Modify the ports used by Apache by default
# It is also possible to change these environment variables at runtime
ENV APACHE_HTTP_PORT_NUMBER=8181 
ENV APACHE_HTTPS_PORT_NUMBER=8143
EXPOSE 8181 8143

Based on the extended image, you can use a Docker Compose file like the one below to add other features:

version: '2'
services:
  mariadb:
    image: 'bitnami/mariadb:10.1'
    environment:
      - MARIADB_USER=bn_joomla
      - MARIADB_DATABASE=bitnami_joomla
      - ALLOW_EMPTY_PASSWORD=yes
    volumes:
      - 'mariadb_data:/bitnami'
  joomla:
    build: .
    environment:
      - MARIADB_HOST=mariadb
      - MARIADB_PORT_NUMBER=3306
      - JOOMLA_DATABASE_USER=bn_joomla
      - JOOMLA_DATABASE_NAME=bitnami_joomla
      - ALLOW_EMPTY_PASSWORD=yes
    ports:
      - '80:8181'
      - '443:8143'
    volumes:
      - 'joomla_data:/bitnami'
    depends_on:
      - mariadb
volumes:
  mariadb_data:
    driver: local
  joomla_data:
    driver: local

Notable Changes

3.9.6-debian-9-r12 and 3.9.6-ol-7-r14

This image has been adapted so it's easier to customize. See the Customize this image section for more information.
The Apache configuration volume (/bitnami/apache) has been deprecated, and support for this feature will be dropped in the near future. Until then, the container will enable the Apache configuration from that volume if it exists. By default, and if the configuration volume does not exist, the configuration files will be regenerated each time the container is created. Users wanting to apply custom Apache configuration files are advised to mount a volume for the configuration at /opt/bitnami/apache/conf, or mount specific configuration files individually.
The PHP configuration volume (/bitnami/php) has been deprecated, and support for this feature will be dropped in the near future. Until then, the container will enable the PHP configuration from that volume if it exists. By default, and if the configuration volume does not exist, the configuration files will be regenerated each time the container is created. Users wanting to apply custom PHP configuration files are advised to mount a volume for the configuration at /opt/bitnami/php/conf, or mount specific configuration files individually.
Enabling custom Apache certificates by placing them at /opt/bitnami/apache/certs has been deprecated, and support for this functionality will be dropped in the near future. Users wanting to enable custom certificates are advised to mount their certificate files on top of the preconfigured ones at /certs.

Contributing

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.

Issues

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)

License

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.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

What is Joomla?

TL;DR;

Docker Compose

Why use Bitnami Images?

How to deploy Joomla in Kubernetes?

Supported tags and respective `Dockerfile` links

Prerequisites

How to use this image

Run Joomla with a Database Container

Run the application using Docker Compose

Run the application manually

Persisting your application

Mount host directories as data volumes with Docker Compose

Mount host directories as data volumes using the Docker command line

Upgrade this application

Configuration

Environment variables

User and Site configuration

Use an existing database

Create a database for Joomla! using mysql-client

SMTP Configuration

Customize this image

Extend this image

Notable Changes

3.9.6-debian-9-r12 and 3.9.6-ol-7-r14

Contributing

Issues

License

About

Releases

Packages

Languages

Name		Name	Last commit message	Last commit date
Latest commit History 1,174 Commits
.github		.github
3		3
LICENSE		LICENSE
README.md		README.md
docker-compose.yml		docker-compose.yml

License

anibal-aguila/bitnami-docker-joomla

Folders and files

Latest commit

History

Repository files navigation

What is Joomla?

TL;DR;

Docker Compose

Why use Bitnami Images?

How to deploy Joomla in Kubernetes?

Supported tags and respective Dockerfile links

Prerequisites

How to use this image

Run Joomla with a Database Container

Run the application using Docker Compose

Run the application manually

Persisting your application

Mount host directories as data volumes with Docker Compose

Mount host directories as data volumes using the Docker command line

Upgrade this application

Configuration

Environment variables

User and Site configuration

Use an existing database

Create a database for Joomla! using mysql-client

SMTP Configuration

Customize this image

Extend this image

Notable Changes

3.9.6-debian-9-r12 and 3.9.6-ol-7-r14

Contributing

Issues

License

About

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Languages

Supported tags and respective `Dockerfile` links

Packages