Introducing our new CEO Don Johnson - Read More

bitnami/joomla

Verified Publisher

By VMware

Updated 7 months ago

🛑 DEPRECATED Bitnami container image for Joomla!

Image
Content Management System
26

1M+

Bitnami package for Joomla!

🛑 Deprecation Notice

The Joomla! container is now deprecated. This image will no longer be released in our catalog, but already-released container images will persist in the registries.

After some months, this repository will be removed in favor of bitnami/joomla-archived where all existing images can be found.

What is Joomla!?

Joomla! is an award winning open source CMS platform for building websites and applications. It includes page caching, page compression and Let's Encrypt auto-configuration support.

Overview of Joomla! Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.

TL;DR

Docker Compose
curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/joomla/docker-compose.yml > docker-compose.yml
docker-compose up -d

Warning: This quick setup is only intended for development environments. You are encouraged to change the insecure default credentials and check out the available configuration options in the Environment Variables section for a more secure deployment.

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 that gives you a small base container image and the familiarity of a leading Linux distribution- or scratch -an explicitly empty image-.
  • All Bitnami images available in Docker Hub are signed with Notation. Check this post to know how to verify the integrity of the images.
  • Bitnami container images are released on a regular basis with the latest distribution packages available.

Looking to use Joomla! in production? Try VMware Tanzu Application Catalog, the commercial edition of the Bitnami catalog.

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.

Why use a non-root container?

Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers in our docs.

Supported tags and respective Dockerfile links

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

You can see the equivalence between the different tags by taking a look at the tags-info.yaml file present in the branch folder, i.e bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml.

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

Get this image

The recommended way to get the Bitnami Joomla! Docker Image is to pull the prebuilt image from the Docker Hub Registry.

docker pull bitnami/joomla:latest

To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.

docker pull bitnami/joomla:[TAG]

If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the docker build command. Remember to replace the APP, VERSION and OPERATING-SYSTEM path placeholders in the example command below with the correct values.

git clone https://github.com/bitnami/containers.git
cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .
How to use this image

Joomla! requires access to a MySQL or MariaDB database to store information. We'll use the Bitnami Docker Image for MariaDB for the database requirements.

Using the Docker Command Line

Step 1: Create a network
docker network create joomla-network
Step 2: Create a volume for MariaDB persistence and create a MariaDB container
$ docker volume create --name mariadb_data
docker run -d --name mariadb \
  --env ALLOW_EMPTY_PASSWORD=yes \
  --env MARIADB_USER=bn_joomla \
  --env MARIADB_PASSWORD=bitnami \
  --env MARIADB_DATABASE=bitnami_joomla \
  --network joomla-network \
  --volume mariadb_data:/bitnami/mariadb \
  bitnami/mariadb:latest
Step 3: Create volumes for Joomla! persistence and launch the container
$ docker volume create --name joomla_data
docker run -d --name joomla \
  -p 8080:8080 -p 8443:8443 \
  --env ALLOW_EMPTY_PASSWORD=yes \
  --env JOOMLA_DATABASE_USER=bn_joomla \
  --env JOOMLA_DATABASE_PASSWORD=bitnami \
  --env JOOMLA_DATABASE_NAME=bitnami_joomla \
  --network joomla-network \
  --volume joomla_data:/bitnami/joomla \
  bitnami/joomla:latest

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

Run the application using Docker Compose

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

Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated Bitnami Helm chart.

If you detect any issue in the docker-compose.yaml file, feel free to report it or contribute with a fix by following our Contributing Guidelines.

Persisting your application

If you remove the container all your data 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 directory at the /bitnami/joomla path. If the mounted directory is empty, it will be initialized on the first run. Additionally you should mount a volume for persistence of the MariaDB data.

The above examples define the Docker volumes named mariadb_data and joomla_data. The Joomla! application state will persist as long as volumes are not removed.

To avoid inadvertent removal of 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:
-      - 'mariadb_data:/bitnami/mariadb'
+      - /path/to/mariadb-persistence:/bitnami/mariadb
   ...
   joomla:
     ...
     volumes:
-      - 'joomla_data:/bitnami/joomla'
+      - /path/to/joomla-persistence:/bitnami/joomla
   ...
-volumes:
-  mariadb_data:
-    driver: local
-  joomla_data:
-    driver: local

NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID 1001.

Mount host directories as data volumes using the Docker command line

Step 1: Create a network (if it does not exist)
docker network create joomla-network
Step 2. Create a MariaDB container with host volume
docker run -d --name mariadb \
  --env ALLOW_EMPTY_PASSWORD=yes \
  --env MARIADB_USER=bn_joomla \
  --env MARIADB_PASSWORD=bitnami \
  --env MARIADB_DATABASE=bitnami_joomla \
  --network joomla-network \
  --volume /path/to/mariadb-persistence:/bitnami/mariadb \
  bitnami/mariadb:latest
Step 3. Create the Joomla! container with host volumes
docker run -d --name joomla \
  -p 8080:8080 -p 8443:8443 \
  --env ALLOW_EMPTY_PASSWORD=yes \
  --env JOOMLA_DATABASE_USER=bn_joomla \
  --env JOOMLA_DATABASE_PASSWORD=bitnami \
  --env JOOMLA_DATABASE_NAME=bitnami_joomla \
  --network joomla-network \
  --volume /path/to/joomla-persistence:/bitnami/joomla \
  bitnami/joomla:latest

Configuration

Environment variables

Customizable environment variables

NameDescriptionDefault Value
JOOMLA_DATA_TO_PERSISTFiles to persist relative to the Joomla! installation directory. To provide multiple values, separate them with a whitespace.$JOOMLA_BASE_DIR
JOOMLA_LOAD_SAMPLE_DATALoad Joomla sample data.yes
JOOMLA_SKIP_BOOTSTRAPWhether to perform initial bootstrapping for the application.nil
JOOMLA_USERNAMEJoomla! user name.user
JOOMLA_PASSWORDJoomla! user password.bitnami
JOOMLA_EMAILJoomla! user e-mail address.user@example.com
JOOMLA_SITE_NAMEJoomla! site name$JOOMLA_DEFAULT_SITE_NAME
JOOMLA_SECRETSecret value for data encryption (auto-generated if not provided)nil
JOOMLA_SMTP_HOSTJoomla! SMTP server host.nil
JOOMLA_SMTP_PORT_NUMBERJoomla! SMTP server port number.nil
JOOMLA_SMTP_USERJoomla! SMTP server user.nil
JOOMLA_SMTP_PASSWORDJoomla! SMTP server user password.nil
JOOMLA_SMTP_PROTOCOLJoomla! SMTP server protocol.nil
JOOMLA_SMTP_SENDER_EMAILJoomla! SMTP Sender email.nil
JOOMLA_SMTP_SENDER_NAMEJoomla! SMTP Sender name.nil
JOOMLA_DEFAULT_DATABASE_PORT_NUMBERDatabase server port.3306
JOOMLA_DATABASE_HOSTDatabase server host.$JOOMLA_DEFAULT_DATABASE_HOST
JOOMLA_DATABASE_PORT_NUMBERDatabase server port.$JOOMLA_DEFAULT_DATABASE_PORT_NUMBER
JOOMLA_DATABASE_NAMEDatabase name.bitnami_joomla
JOOMLA_DATABASE_USERDatabase user name.bn_joomla
JOOMLA_DATABASE_PASSWORDDatabase user password.nil

Read-only environment variables

NameDescriptionValue
JOOMLA_BASE_DIRJoomla! installation directory.${BITNAMI_ROOT_DIR}/joomla
JOOMLA_TMP_DIRJoomla! installation directory.${JOOMLA_BASE_DIR}/tmp
JOOMLA_LOGS_DIRJoomla! installation directory.${JOOMLA_BASE_DIR}/logs
JOOMLA_CONF_FILEConfiguration file for Joomla!.${JOOMLA_BASE_DIR}/configuration.php
JOOMLA_VOLUME_DIRJoomla! directory for persisted data files.${BITNAMI_VOLUME_DIR}/joomla
JOOMLA_DEFAULT_SITE_NAMEJoomla! default site nameMy site
JOOMLA_DEFAULT_DATABASE_HOSTDefault database server host.mariadb
PHP_DEFAULT_MEMORY_LIMITDefault PHP memory limit.256M

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. If you want to add a new environment variable:

  • For docker-compose add the variable name and value under the application section in the docker-compose.yml file present in this repository:
joomla:
  ...
  environment:
    - JOOMLA_PASSWORD=my_password
  ...
  • For manual execution add a --env option with each variable and value:

    docker run -d --name joomla -p 80:8080 -p 443:8443 \
      --env JOOMLA_PASSWORD=my_password \
      --network joomla-tier \
      --volume /path/to/joomla-persistence:/bitnami \
      bitnami/joomla:latest
    

Example

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

  joomla:
    ...
    environment:
      - JOOMLA_DATABASE_USER=bn_joomla
      - JOOMLA_DATABASE_NAME=bitnami_joomla
      - ALLOW_EMPTY_PASSWORD=yes
      - JOOMLA_SMTP_HOST=smtp.gmail.com
      - JOOMLA_SMTP_PORT=587
      - JOOMLA_SMTP_USER=your_email@gmail.com
      - JOOMLA_SMTP_PASSWORD=your_password
      - JOOMLA_SMTP_PROTOCOL=tls
  ...
  • For manual execution:

    docker run -d --name joomla -p 80:8080 -p 443:8443 \
      --env JOOMLA_DATABASE_USER=bn_joomla \
      --env JOOMLA_DATABASE_NAME=bitnami_joomla \
      --env JOOMLA_SMTP_HOST=smtp.gmail.com \
      --env JOOMLA_SMTP_PORT=587 \
      --env JOOMLA_SMTP_USER=your_email@gmail.com \
      --env JOOMLA_SMTP_PASSWORD=your_password \
      --env JOOMLA_SMTP_PROTOCOL=tls \
      --network joomla-tier \
      --volume /path/to/joomla-persistence:/bitnami \
      bitnami/joomla:latest
    

Installing additional language packs

By default, this container packs a generic English version of Joomla!. Nevertheless, more Language Packs can be added to the default configuration using the in-platform Administration interface. In order to fully support a new Language Pack it is also a requirement to update the system's locales files. We highly recommend extending the default image and adding as many locales as needed: +Stop the currently running container using the command

FROM bitnami/joomla
RUN echo "es_ES.UTF-8 UTF-8" >> /etc/locale.gen && locale-gen

Bear in mind that in the example above es_ES.UTF-8 UTF-8 is the locale needed for the desired Language Pack to install. You may change this value to the locale corresponding to your pack.

Logging

The Bitnami Joomla! Docker image sends the container logs to stdout. To view the logs:

docker logs joomla

Or using Docker Compose:

docker-compose logs joomla

You can configure the containers logging driver using the --log-driver option if you wish to consume the container logs differently. In the default configuration docker uses the json-file driver.

Maintenance

Backing up your container

To backup your data, configuration and logs, follow these simple steps:

Step 1: Stop the currently running container
docker stop joomla

Or using Docker Compose:

docker-compose stop joomla
Step 2: Run the backup command

We need to mount two volumes in a container we will use to create the backup: a directory on your host to store the backup in, and the volumes from the container we just stopped so we can access the data.

docker run --rm -v /path/to/joomla-backups:/backups --volumes-from joomla busybox \
  cp -a /bitnami/joomla /backups/latest

Restoring a backup

Restoring a backup is as simple as mounting the backup as volumes in the containers.

For the MariaDB database container:

 $ docker run -d --name mariadb \
   ...
-  --volume /path/to/mariadb-persistence:/bitnami/mariadb \
+  --volume /path/to/mariadb-backups/latest:/bitnami/mariadb \
   bitnami/mariadb:latest

For the Joomla! container:

 $ docker run -d --name joomla \
   ...
-  --volume /path/to/joomla-persistence:/bitnami/joomla \
+  --volume /path/to/joomla-backups/latest:/bitnami/joomla \
   bitnami/joomla:latest

Upgrade this image

NOTE: Application upgrades should be done manually inside the docker container following the official documentation. As an alternative, you can try upgrading using an updated Docker image. However, any data from the Joomla! container will be lost and you will have to reinstall all the plugins and themes you manually added.

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/containers/tree/main/bitnami/mariadb#upgrade-this-image

Step 1: Get the updated image
docker pull bitnami/joomla:latest
Step 2: Stop the running container

Stop the currently running container using the command

docker-compose stop joomla
Step 3: Take a snapshot of the application state

Follow the steps in Backing up your container to take a snapshot of the current application state.

Step 4: Remove the currently running container

Remove the currently running container by executing the following command:

docker-compose rm -v joomla
Step 5: Run the new image

Update the image tag in docker-compose.yml and re-create your container with the new image:

docker-compose up -d
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:

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

### Change user to perform privileged actions
USER 0
### Install 'vim'
RUN install_packages vim
### Revert to the original non-root user
USER 1001

### 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 update the docker-compose.yml file present in this repository to add other features:

   joomla:
-    image: bitnami/joomla:latest
+    build: .
     ports:
-      - '80:8080'
-      - '443:8443'
+      - '80:8181'
+      - '443:8143'
     environment:
       ...
+      - PHP_MEMORY_LIMIT=512m
     ...

Note: the README for this image is longer than the DockerHub length limit of 25000, so has been trimmed. The full README can be found at https://github.com/bitnami/containers/blob/main/bitnami/joomla/README.md

Docker Pull Command

docker pull bitnami/joomla
Bitnami