armhf organization is deprecated in favor of the more-specific
arm32v6 organizations, as per https://github.com/docker-library/official-images#architectures-other-than-amd64. Please adjust your usages accordingly.
Supported tags and respective
THESE IMAGES ARE VERY EXPERIMENTAL; THEY ARE PROVIDED ON A BEST-EFFORT BASIS WHILE docker-library/official-images#2289 IS STILL IN-PROGRESS (which is the first step towards proper multiarch images)
PLEASE DO NOT USE THEM FOR IMPORTANT THINGS
This image is built from the source of the official image of the same name (
wordpress). Please see that image's description for links to the relevant
If you are curious about specifically how this image differs, see the Jenkins Groovy DSL scripts in the
tianon/jenkins-groovy GitHub repository, which are responsible for creating the Jenkins jobs which build them.
Where to file issues:
the Docker Community
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
What is WordPress?
WordPress is a free and open source blogging tool and a content management system (CMS) based on PHP and MySQL, which runs on a web hosting service. Features include a plugin architecture and a template system. WordPress is used by more than 22.0% of the top 10 million websites as of August 2013. WordPress is the most popular blogging system in use on the Web, at more than 60 million websites. The most popular languages used are English, Spanish and Bahasa Indonesia.
How to use this image
$ docker run --name some-wordpress --link some-mysql:mysql -d wordpress
The following environment variables are also honored for configuring your WordPress instance:
-e WORDPRESS_DB_HOST=...(defaults to the IP and port of the linked
-e WORDPRESS_DB_USER=...(defaults to "root")
-e WORDPRESS_DB_PASSWORD=...(defaults to the value of the
MYSQL_ROOT_PASSWORDenvironment variable from the linked
-e WORDPRESS_DB_NAME=...(defaults to "wordpress")
-e WORDPRESS_TABLE_PREFIX=...(defaults to "", only set this when you need to override the default table prefix in wp-config.php)
-e WORDPRESS_NONCE_SALT=...(default to unique random SHA1s)
WORDPRESS_DB_NAME specified does not already exist on the given MySQL server, it will be created automatically upon startup of the
wordpress container, provided that the
WORDPRESS_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-wordpress --link some-mysql:mysql -p 8080:80 -d wordpress
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
WORDPRESS_DB_HOST along with the password in
WORDPRESS_DB_PASSWORD and the username in
WORDPRESS_DB_USER (if it is something other than
$ docker run --name some-wordpress -e WORDPRESS_DB_HOST=10.1.2.3:3306 \ -e WORDPRESS_DB_USER=... -e WORDPRESS_DB_PASSWORD=... -d wordpress
version: '2' services: wordpress: image: wordpress ports: - 8080:80 environment: WORDPRESS_DB_PASSWORD: example mysql: image: mariadb environment: MYSQL_ROOT_PASSWORD: example
docker-compose up, wait for it to initialize completely, and visit
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
wordpress 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: