Portainer Templates logo

Portainer Templates

Plesk Plesk

Container

CMS

WebOps platform and hosting control panel

Image details

Pulls: 827k
Architecture: amd64
Image size: 676 MB
Latest: 18.0
User: plesk
Created: Aug 21, 2015
Updated: 1 day ago
Status: active

Configuration

Type
Container
Platform
linux
Image
plesk/plesk:latest
Ports
21/tcp80/tcp443/tcp8880/tcp8443/tcp8447/tcp

Template by mikestraney

Notes

Default credentials: admin / changeme

Standalone Install

Select an install method, to see config/commands for deploying Plesk

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 Plesk, fill in any config options, and hit Deploy

Template Import URL

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

More install options in our documentation.

Plesk provides web administrators, application developers, web professionals, hosting service providers, and infrastructure providers a ready-to-code environment to build targeted solutions on.
  • Manage plans, subscriptions, accounts, and resellers
  • Create domains, sub-domains, and domain aliases
  • Easily set up email addresses, email forwarding, and email filters
  • Configure databases from a simple web interface
  • One-click install and mass-management of WordPress.
  • Use port mapped to 8880 to access the control panel.
  • Access a scalable and flexible platform
  • Migrate legacy platforms
  • Standardize shared hosting infrastructure
  • Unify User Experience and enable Mobile

To create a container based on Plesk Obsidian for evaluation purposes use the following command: 
docker run -d --tmpfs /tmp --tmpfs /run --tmpfs /run/lock -v /sys/fs/cgroup:/sys/fs/cgroup:ro -p 8880:8880 plesk/plesk

Use Docker host IP address and 8880 port for URL to open it in the browser. E.g. http://localhost:8880
Default administrator credentials: admin / changeme1Q
Create a container with typical port mapping:
docker run -d --tmpfs /tmp --tmpfs /run --tmpfs /run/lock -v /sys/fs/cgroup:/sys/fs/cgroup:ro -p 80:80 -p 443:443 -p 8880:8880 -p 8443:8443 -p 8447:8447 plesk/plesk

Automatic port mapping can be used to publish all exposed ports to random ports with high numbers:
docker run -d --tmpfs /tmp --tmpfs /run --tmpfs /run/lock -v /sys/fs/cgroup:/sys/fs/cgroup:ro -P plesk/plesk

Original Dockerfiles - https://github.com/plesk/docker
Official Plesk documentation - https://docs.plesk.com

Serve Plesk on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying plesk.example.com to http://plesk:80

Add this to your Caddyfile

plesk.example.com {
	reverse_proxy http://plesk:80
}

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.

Published on a random port

This template exposes 21/tcp without setting a host port, so Docker picks a random free one on every deploy.

  • Find it in the Ports column of Portainer's container list, or with docker port <container>

Image won't pull

Test the pull directly on the host: docker pull plesk/plesk: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.

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

Data disappears when the container is recreated

This template doesn't define any volumes, so everything the app saves lives inside the container and is lost on update or recreate.

  • Add a volume mapping for the app's data folder before storing anything you care about.

Raise an issue

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

A single container

Plesk runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything Plesk needs bundled into one download. This template pulls plesk/plesk:latest, which Docker fetches once (about 676 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Plesk's comes from Docker Hub, published by plesk.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 18.0. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, so it runs on regular x86 PCs and servers, though not ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. Here the app exposes a port but leaves the host side blank, so Docker picks a free one for you. It opens:

  • 21, published on a random host port
  • 80, published on a random host port
  • 443, published on a random host port
  • 8880, published on a random host port
  • 8443, published on a random host port
  • 8447, published on a random host port

No stored data

This template doesn't mount any storage, so whatever Plesk writes stays inside the container and is wiped if it's recreated or updated. That's fine for something stateless, but add a volume before trusting it with anything you want to keep.

Networking

Nothing custom is set, so Plesk sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

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 Plesk up. Add the template list to Portainer once, then deploying Plesk is a click rather than a wall of config.