joomlaEstimated reading time: 7 minutes
Joomla! is an open source content management system.
GitHub repo: https://github.com/joomla/docker-joomla
Supported tags and respective
Where to file issues:
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
What is Joomla?
Joomla is a free and open-source content management system (CMS) for publishing web content. It is built on a model–view–controller web application framework that can be used independently of the CMS. Joomla is written in PHP, uses object-oriented programming (OOP) techniques and software design patterns, stores data in a MySQL, MS SQL, or PostgreSQL database, and includes features such as page caching, RSS feeds, printable versions of pages, news flashes, blogs, search, and support for language internationalization.
How to use this image
$ docker run --name some-joomla --link some-mysql:mysql -d joomla
The following environment variables are also honored for configuring your Joomla instance:
-e JOOMLA_DB_HOST=...(defaults to the IP and port of the linked
-e JOOMLA_DB_USER=...(defaults to “root”)
-e JOOMLA_DB_PASSWORD=...(defaults to the value of the
MYSQL_ROOT_PASSWORDenvironment variable from the linked
-e JOOMLA_DB_NAME=...(defaults to “joomla”)
JOOMLA_DB_NAME specified does not already exist on the given MySQL server, it will be created automatically upon startup of the
joomla container, provided that the
JOOMLA_DB_USER specified has the necessary permissions to create it.
If you’d like to be able to access the instance from the host without the container’s IP, standard port mappings can be used:
$ docker run --name some-joomla --link some-mysql:mysql -p 8080:80 -d joomla
Then, access it via
http://host-ip:8080 in a browser.
If you’d like to use an external database instead of a linked
mysql container, specify the hostname and port with
JOOMLA_DB_HOST along with the password in
JOOMLA_DB_PASSWORD and the username in
JOOMLA_DB_USER (if it is something other than
$ docker run --name some-joomla -e JOOMLA_DB_HOST=10.1.2.3:3306 \ -e JOOMLA_DB_USER=... -e JOOMLA_DB_PASSWORD=... -d joomla
docker stack deploy or
version: '3.1' services: joomla: image: joomla restart: always links: - joomladb:mysql ports: - 8080:80 environment: JOOMLA_DB_HOST: joomladb JOOMLA_DB_PASSWORD: example joomladb: image: mysql:5.6 restart: always environment: MYSQL_ROOT_PASSWORD: example
docker stack deploy -c stack.yml joomla (or
docker-compose -f stack.yml up), wait for it to initialize completely, and visit
http://host-ip:8080 (as appropriate).
Adding additional libraries / extensions
This image does not provide any additional PHP extensions or other libraries, even if they are required by popular plugins. There are an infinite number of possible plugins, and they potentially require any extension PHP supports. Including every PHP extension that exists would dramatically increase the image size.
If you need additional PHP extensions, you’ll need to create your own image
FROM this one. The documentation of the
php image explains how to compile additional extensions. Additionally, the
joomla Dockerfile has an example of doing this.
The following Docker Hub features can help with the task of keeping your dependent images up-to-date:
- Automated Builds let Docker Hub automatically build your Dockerfile each time you push changes to it.
joomla images come in many flavors, each designed for a specific use case.
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
This image is based on the popular Alpine Linux project, available in the
alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
This variant is highly recommended when final image size being as small as possible is desired. The main caveat to note is that it does use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libc requirements. However, most software doesn’t have an issue with this, so this variant is usually a very safe choice. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
To minimize image size, it’s uncommon for additional related tools (such as
bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the
alpine image description for examples of how to install packages if you are unfamiliar).
View license information for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the
As for any pre-built image usage, it is the image user’s responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.library, sample, joomla