Dockerized Portainer

Why?

This is a dockerized version of Portainer that can be trivially run.

App templates include forms to facilitate managing deployment parameters (unlike custom app templates)

Reverse proxy versions of some public services are provided to facilitate domain mapping and SSL certificate management.

This is a fairly new repo and will be updated frequently. The goal is to establish a set of core templates for rapid containerized development or production deployments.

Running Portianer

Prerequisites: You will need docker installed and either curl/wget or git.

1. Run directly

   To run portianer directly without cloning this repository, navigate to the folder where you want to base your container mounts and run:

   # Download the Docker Compose file from the specified URL
   curl -o docker-compose.yml https://raw.githubusercontent.com/Mugane/Portainer/main/docker-compose.yml
   
   # Run Docker Compose using the downloaded file
   docker compose up -d
   

2. Clone & Run

   # Clone the repository
   git clone https://github.com/Mugane/Portainer.git
   
   # Change directory to the cloned repository
   cd Portainer
   
   # Run Docker Compose
   docker compose up -d
   

Portainer Stack templates

This repo contains custom portainer templates, you can install them after running Portainer by switching the App Templates URL (under Settings) to (https://mugane.github.io/Portainer/templates.json)

Commits to the main branch automatically trigger the collate.sh script to generate and publish the final templates.json file to GitHub Pages. templates.json is not present in the main branch to avoid confusion when making source updates.

While templates are being developed and customized, you might find additional useful templates using this URL for the templates target: https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json

Modifying the templates

See Portainer Documentation for format descriptions.

Edit the json and optional docker-compose.yml files under the templates folder. To test locally, run the collate.sh script to regenerate the template.json file with the full list of templates. On windows you can set up a watch by running the monitor.ps1 script in PowerShell: - Open PowerShell as Administrator, navigate to the Portainer repo folder and run: docker run -d -v ${PWD}:/usr/share/nginx/html -p 8080:80 --name portemp nginx:latest Set-ExecutionPolicy RemoteSigned -Scope Process .\monitor.ps1 - Use http://localhost:8080/templates.json for the templates url in your local Portainer settings.

By convention the ./templates/name.json file and the optional ./templates/name/docker-compose.yml folder use the same name for clarity. It is dash-separated, lowercase and describes the primary nature of the template contents.

Wish list

The following containers would be nice to have.

Lissy: Caddy, CrateDB, Drupal, Elasticsearch, Ghost, Httpd, Jenkins, Ironfunctions, Joomla, Magento, Minio, Mongo, Plone, PostgreSQL, Redis, Registry, Scality S3, Solr, Urbackup, Blender, Boinc, Gitqlient, Ubuntu, OPC router, softing edgeConnector containers Apache Httpd, influxdb, freescout, wger, dockge, Activepieces, Plane PM, Flowise AI, Ory Kratos, umami.is, mamoto,

Other: Geany, Home Assistant