Portainer Templates logo

Portainer Templates

Mailpile Mailpile

Stack

Email

Mailpile is an e-mail client!/search engine and a personal webmail server/easy way to encrypt your e-mail/easy way to encrypt your e-mail

Image details

Pulls: 1.3M
Architecture: amd64
Image size: 52 MB
User: rroemhild
Created: Jun 02, 2015
Updated: 5 years ago
Status: archived

Configuration

Type
Compose
Platform
linux
Image
rroemhild/mailpile
Ports
33411:33411
Volumes
/root/.local/share/Mailpile : /portainer/Files/AppData/Config/mailpile/root/.gnupg : /portainer/Files/AppData/Config/mailpile/gnu
Source
Repo

Template by xneo1·Source

Standalone Install

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

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 Mailpile, 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:

services:
  mailpile:
    container_name: mailpile
    image: rroemhild/mailpile
    volumes:
      - /portainer/Files/AppData/Config/mailpile:/root/.local/share/Mailpile
      - /portainer/Files/AppData/Config/mailpile/gnu:/root/.gnupg
    ports:
      - '33411:33411'

Or deploy it directly from the source:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/mailpile.yml up -d

More install options in our documentation.

Mailpile Docker image

A minimal Mailpile Docker image based on Alpine Linux.

Usage

docker run -d --name mailpile -p 33411:33411 rroemhild/mailpile

Bind volume /root/.local/share/Mailpile and /root/.gnupg for persistent storage:
docker run -d --name mailpile -p 33411:33411 -v /some/local/path:/root/.local/share/Mailpile -v /another/local/path:/root/.gnupg rroemhild/mailpile

Docker-compose

version: '3'
services:
  mailpile:
    container_name: mailpile
    image: rroemhild/mailpile
    volumes:
      - '/some/local/path:/root/.local/share/Mailpile'
      - '/another/local/path:/root/.gnupg'
    ports:
      - '33411:33411'

Serve Mailpile 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 mailpile.example.com to http://mailpile:33411

Add this to your Caddyfile

mailpile.example.com {
	reverse_proxy http://mailpile:33411
}

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.

Port already in use

If deployment fails with "Bind for 0.0.0.0:33411 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :33411
  • Stop the other service, or pick a different host port. In 33411:33411 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:33411. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, mailpile can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 33411

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/mailpile (and the same for the other mapped folders)

Image won't pull

Test the pull directly on the host: docker pull rroemhild/mailpile

  • "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.

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

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

The app image

An image is the app packed up ready to go, everything Mailpile needs bundled into one download. This template pulls rroemhild/mailpile, which Docker fetches once (about 52 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. Mailpile's comes from Docker Hub, published by rroemhild.

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. 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. A mapping like 33411:33411 means it's reachable on port 33411 of your server, where the left number is yours to change and the right one belongs to the app. It opens:

  • 33411:33411

Volumes

A volume is where Mailpile 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:

  • /root/.local/share/Mailpile from /portainer/Files/AppData/Config/mailpile on the host
  • /root/.gnupg from /portainer/Files/AppData/Config/mailpile/gnu on the host

Networking

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

Container name

Once it's deployed, Portainer names the container mailpile. That's what you'll spot in the containers list and use in commands like docker logs mailpile.

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