Portainer Templates logo

Portainer Templates

Wordpress (stack) Wordpress (stack)

WordpressWeb

Wordpress setup with a MySQL database

Configuration

Type
Compose
Platform
linux
Env vars
WEB_SERVER_PORT=5080MYSQL_DATABASE_USER_NAME=wordpressMYSQL_DATABASE_PASSWORD=''MYSQL_DATABASE_ROOT_PASSWORD=''
Source
Repo

Template by novaspirit·Source

Notes

Template created by Pi-Hosted Series
Check our Github page: https://github.com/pi-hosted/pi-hosted

Official Webpage: https://wordpress.com/
Official Docker Documentation: https://github.com/docker-library/docs/tree/master/wordpress#-via-docker-stack-deploy-or-docker-compose

Pi-Hosted dedicated documentation: wordpress_installation.md




Deploys a Wordpress instance connected to a MySQL database.

Services

wordpress

Configuration

Image
wordpress:latest
Ports
${WEB_SERVER_PORT}:80
Volumes
/var/www/html : wordpress
Env vars
WORDPRESS_DB_HOST=db:3306WORDPRESS_DB_USER=${MYSQL_DATABASE_USER_NAME}WORDPRESS_DB_PASSWORD=${MYSQL_DATABASE_PASSWORD}WORDPRESS_DB_NAME=wordpress
Restart
unless-stopped

Image details

Pulls: 1.5B
User: stackbrew
Created: Jun 05, 2014
Updated: 3 days ago
Status: active

db

Configuration

Image
jc21/mariadb-aria:latest
Volumes
/var/lib/mysql : db
Env vars
MYSQL_DATABASE=wordpressMYSQL_USER=${MYSQL_DATABASE_USER_NAME}MYSQL_PASSWORD=${MYSQL_DATABASE_PASSWORD}MYSQL_ROOT_PASSWORD=${MYSQL_DATABASE_ROOT_PASSWORD}
Restart
unless-stopped

Image details

Pulls: 73.3M
User: jc21
Created: Nov 01, 2018
Updated: 10 months ago
Status: active

Standalone Install

Select an install method, to see config/commands for deploying Wordpress (stack)

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Wordpress (stack), fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

version: '3.1'

services:

  wordpress:
    image: wordpress:latest
    container_name: wordpress:latest
    restart: unless-stopped
    ports:
      - ${WEB_SERVER_PORT}:80
    environment:
      WORDPRESS_DB_HOST: db:3306
      WORDPRESS_DB_USER: ${MYSQL_DATABASE_USER_NAME}
      WORDPRESS_DB_PASSWORD: ${MYSQL_DATABASE_PASSWORD}
      WORDPRESS_DB_NAME: wordpress
    networks:
      - wordpress     
    volumes:
      - wordpress:/var/www/html

  db:
    image: jc21/mariadb-aria:latest
    restart: unless-stopped
    environment:
      MYSQL_DATABASE: wordpress
      MYSQL_USER: ${MYSQL_DATABASE_USER_NAME}
      MYSQL_PASSWORD: ${MYSQL_DATABASE_PASSWORD}
      MYSQL_ROOT_PASSWORD: ${MYSQL_DATABASE_ROOT_PASSWORD}
    networks:
      - wordpress     
    volumes:
      - db:/var/lib/mysql

volumes:
  wordpress:
  db:

networks:
  wordpress:

Or deploy it directly from the source:

git clone https://github.com/pi-hosted/pi-hosted
cd pi-hosted
docker compose -f stack/wordpress-stack.yml up -d

More install options in our documentation.

Container Documentation

wordpress Documentation

The WordPress rich content management system can utilize plugins, widgets, and themes.

db Documentation

Extension of the mariadb image that forces aria storage engine by default.

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Image won't pull

Test the pull directly on the host: docker pull wordpress:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect <container> --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

Wordpress (stack) is a Compose stack, a set of containers (2 of them) defined in one file and brought up together by Portainer, then started and stopped as a single app.

The services

This stack is built from 2 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:

  • wordpress runs wordpress:latest
  • db runs jc21/mariadb-aria:latest

Volumes

A volume is where Wordpress (stack) keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /var/www/html kept in the wordpress volume Docker manages
  • /var/lib/mysql kept in the db volume Docker manages

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Wordpress (stack) takes 8 of them, all with defaults you can leave alone or tweak:

  • WORDPRESS_DB_HOST, defaults to db:3306
  • WORDPRESS_DB_USER, pulled from your own environment
  • WORDPRESS_DB_PASSWORD, pulled from your own environment
  • WORDPRESS_DB_NAME, defaults to wordpress
  • MYSQL_DATABASE, defaults to wordpress
  • MYSQL_USER, pulled from your own environment
  • MYSQL_PASSWORD, pulled from your own environment
  • MYSQL_ROOT_PASSWORD, pulled from your own environment

Restart policy

The restart policy here is unless-stopped, so Docker restarts Wordpress (stack) after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Portainer puts these services on one shared private network, so they can find each other by name (like wordpress) while only the ports above are open to you.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Wordpress (stack) up. Add the template list to Portainer once, then deploying Wordpress (stack) is a click rather than a wall of config.