Supported tags and respective
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
docker stack deploy or
version: '3.1' services: wordpress: image: wordpress ports: - 8080:80 environment: WORDPRESS_DB_PASSWORD: example mysql: image: mysql:5.7 environment: MYSQL_ROOT_PASSWORD: example
docker stack deploy -c stack.yml wordpress (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
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:
it seems like tag php7.1-fpm is not upgraded to latest 4.7.5 any ideas?
I don't really understand your question. I fire up a separate mariadb container for each app instance that requires one (Wordpress, Nextcloud, etc.). The performance hit is negligible. nginx-proxy and letsencrypt only require one instance each to handle everything.
IMO, it is best to do it this way even though you may end up with many mariadb containers. Plus, backups are easy -- just copy the compose directory somewhere, then you can restore to a fresh docker install anywhere with everything right where you left off.
thanks for your fast reply.
Iam wondering what is the difference? I am running already a mariadb container, letsencrypt container (both from linuxserver) connected to wordpress container.
So i really like your approach but it would mean to have some functions doubled. Can I find somewhere what is added/changed to make it working?
To clarify on my previous post in case it wasn't obvious, that's using jwilder/nginx-proxy and jrcs/letsencrypt-nginx-proxy-companion.
version: '2' services: db-wordpress: image: mariadb container_name: db-wordpress volumes: - ./db-wordpress:/var/lib/mysql environment: - MYSQL_ROOT_PASSWORD=wordpress - MYSQL_DATABASE=wordpress - MYSQL_USER=wordpress - MYSQL_PASSWORD=wordpress networks: - proxy-tier restart: always wordpress: depends_on: - db-wordpress image: wordpress container_name: wordpress environment: - WORDPRESS_DB_HOST=db-wordpress:3306 - WORDPRESS_DB_PASSWORD=wordpress - VIRTUAL_HOST=www.example.com - LETSENCRYPT_HOST=www.example.com - LETSENCRYPT_EMAILfirstname.lastname@example.org networks: - proxy-tier restart: always networks: proxy-tier: external: name: nginx_proxy_network_whatever_its_called
Do you have a configuration example for running your worpress docker behind a nginx reverse proxy?
Would be nice to have use of SSL and port 443 as default. One should never run Wordpress on port 80 anyway, and there are issues with reverse-proxying from 80->443.
It sucks that no where in this documentation it mentions that you actually have to link the image to a previously setup mysql package. This needs a more detailed breakdown.
Users interested in running WordPress with Docker may like to check out Fabrica Dev Kit, a complete local development environment and toolkit. Its setup script automatically configures the required Docker containers as well as installing build, watch and deployment tools: https://github.com/fabrica-wp/fabrica-dev-kit
For de MAX_UPLOAD use:
Whit the content:
file_uploads = On
memory_limit = 256M
upload_max_filesize = 256M
post_max_size = 300M
max_execution_time = 600