Skip to main content

Run WordPress on Docker

What is WordPress?​

WordPress is the most widely used CMS on the web, powering a large share of all websites, from blogs to full e-commerce stores via WooCommerce. It is a PHP application backed by a MySQL (or MariaDB) database, served through a web server, and it benefits from Redis for object caching on busier sites.

Why run WordPress in Docker?​

Docker packages each of those pieces (NGINX, PHP-FPM, MySQL, Redis) into isolated containers that run the same on every machine. Instead of installing PHP and MySQL onto your laptop, where versions collide between sites and "works on my machine" starts, you run disposable containers that mirror production and vanish cleanly when you delete them. One site can run PHP 8.3 while another runs an older 7.4 plugin stack, on the same computer, with nothing installed globally.

The catch: wiring those containers together yourself (base images, PHP extensions, networking, permissions) is a week of fiddly Docker work. That is exactly what Laradock removes.

Why Laradock is the best fit for WordPress​

Unlike Laravel, WordPress has no official Docker tool or first-party runtime of its own, so a ready-made, no-lock-in environment matters even more. Here is why Laradock is the best fit:

  • You are never locked into one ecosystem. Laradock is framework-agnostic. Run WordPress today, add a Laravel API, a Symfony service, or a plain PHP script beside it tomorrow, all in the same environment with the same commands.
  • Far more flexibility. 100+ ready services and any PHP version from 5.6 to 8.5, so a legacy theme and a modern site each get exactly the runtime they need.
  • Nothing is hidden and you own everything. No generated files, no magic, no wrapper binary between you and Docker. Every Dockerfile and compose file is right there for you to read and edit.
  • Nothing new to learn. What you use is plain docker compose, knowledge that transfers straight to production. Our CLI is an optional nicety, never a requirement.

Concretely, for WordPress it gives you a production-style NGINX + PHP-FPM stack, MySQL/MariaDB and Redis already wired, a workspace container with WP-CLI, Composer and git installed, and any PHP version behind a single line of config.

Run WordPress on Docker with Laradock​

1. Add Laradock to your project​

cd my-wordpress-site
git clone https://github.com/laradock/laradock.git
cd laradock && cp .env.example .env

(No WordPress files yet? Clone Laradock first, then download WordPress from the workspace container in the next steps.)

2. Pick the services your site needs​

WordPress needs a web server and a database; add Redis for object caching. The web server pulls in PHP-FPM automatically:

docker compose up -d nginx mysql redis workspace

Prefer MariaDB over MySQL? Swap the name: docker compose up -d nginx mariadb redis workspace. The full catalog is here.

Prefer to be asked? The optional CLI walks you through the choices: ./laradock setup, then ./laradock up. It prints every real command it runs.

3. Point WordPress at the containers​

In your wp-config.php, use the service names as hostnames:

define( 'DB_HOST', 'mysql' );
define( 'DB_NAME', 'default' );
define( 'DB_USER', 'default' );
define( 'DB_PASSWORD', 'secret' );

The default database, user and password live in mysql/defaults.env; override any of them by adding the line to Laradock's .env (it always wins).

4. Install and run your site​

Enter the workspace container, where WP-CLI, Composer and git live, and set the site up:

docker compose exec workspace bash
wp core download          # only if you have no WordPress files yet
wp core install --url=http://localhost --title="My Site" \
  --admin_user=admin --admin_password=secret [email protected]

Then open http://localhost. That is a full WordPress site running on Docker.

Change the PHP version anytime​

This is where a native install hurts and Laradock shines. Set the version in Laradock's .env and rebuild:

PHP_VERSION=8.3
docker compose build php-fpm workspace

Anything from PHP 5.6 to 8.5 works, so a legacy site pinned to an old plugin and a brand-new build run side by side, each isolated, none of it installed on your machine.

Frequently Asked Questions​

Do I need to install PHP, MySQL or WP-CLI to run WordPress with Laradock?​

No. Everything lives inside the containers. WP-CLI, Composer, git and PHP are all provided; you never install them on your host.

Which services should I start for a typical WordPress site?​

nginx mysql redis workspace covers most sites: web server, database, object cache, and a shell. Swap mysql for mariadb if you prefer.

Can I run multiple WordPress sites on different PHP versions?​

Yes. Give each its own Laradock with a unique COMPOSE_PROJECT_NAME and DATA_PATH_HOST, set a different PHP_VERSION in each, and they run independently on the same machine.

Does this work the same on macOS, Windows and Linux?​

Yes. Laradock runs anywhere Docker runs. On macOS/Windows, file-sync speed depends on Docker Desktop (VirtioFS helps a lot); it is a Docker Desktop trait, not specific to Laradock.

Is this the same Docker setup I would use in production?​

The containers are production-style (real NGINX + PHP-FPM), so it is far closer to production than a native install. See Prepare Laradock for Production for the hardening steps.

Comparing local WordPress environments? See Laradock vs Local WP and the full Laradock vs Others breakdown. Ready to start? Getting Started takes about five minutes.