pigallery2/docker

PiGallery2 docker installation

You can use docker to run PiGallery2. See all available docker tags here: https://hub.docker.com/r/bpatrik/pigallery2/tags/ We support multiple architectures, including amd64, arm32v7, arm64v8.

0. Install docker

Official installation guide here, but this will most likely do the trick (source):

curl -sSL https://get.docker.com | sh

I. Docker compose

It is recommended to use docker-compose to run pigallery2.

I.0 Install docker-compose

Official dokcer-compose installation guide here, but this will most likely do the trick (source): Install dependencies:

sudo apt-get install libffi-dev libssl-dev
sudo apt-get install -y python python-pip
sudo apt-get remove python-configparser

Install docker-compose:

sudo pip install docker-compose

You can check if it was successful with docker-compose --version.

I.1 get docker-compose.yml file

Download docker-compose/default/docker-compose.yml and docker-compose/default/nginx.conf.

Edit docker-compose.yml to point the volumes to the right image and tmp directories. Edit nginx.conf by replacing yourdomain.com to you domain address.

Note: We are using nginx as reverse proxy to handle https and do proper HTTP queuing, gzipping, etc. Full nginx-based docker-compose tutorial here.

Note 2: You can skip nginx, by using docker-compose/pigallery2-only/docker-compose.yml.

I.1.a get SSL certificate with certbot

Install certbot: https://certbot.eff.org/. (Certbot uses letsencrypt to get free certificate). Than get your certificate:

certbot certonly --standalone -d yourdomain.com

I.1.a start docker-compose

In the folder that has docker-compose.yml:

docker-compose up -d

-d runs it as a daemon. Remove it, so you will see the logs.

After the containers are up and running, you go to yourdomain.com and log in with user: admin pass: admin and set up the page in the settings.

Note: docker-compose.yml contains restart:always, so the containers will be automatically started after reboot (read more here).

II. Without docker-compose

If you want to run the container by yourself, here you go:

docker run \
   -p 80:80 \
   -e NODE_ENV=production \
   -v <path to your config file folder>/config.json:/app/data/config/config.json \
   -v <path to your db file folder>:/app/data/db \
   -v <path to your images folder>:/app/data/images \
   -v <path to your temp folder>:/app/data/tmp \
   bpatrik/pigallery2:nightly-stretch

After the container is up and running, you go to http://localhost and log in with user: admin pass: admin and set up the page in the settings.

Note: even with memory db, pigallery2 creates a db file for storing user credentials (if enabled), so mounting (with -v) the /app/data/db folder is recommended.

II.a before v1.7.0

There was a breaking change in Docker files after v1.7.0. Use this to run earlier versions:

docker run \
   -p 80:80 \
   -e NODE_ENV=production \
   -v <path to your config file folder>/config.json:/pigallery2-release/config.json \
   -v <path to your db file folder>/sqlite.db:/pigallery2-release/sqlite.db \
   -v <path to your images folder>:/pigallery2-release/demo/images \
   -v <path to your temp folder>:/pigallery2-release/demo/TEMP \
   bpatrik/pigallery2:1.7.0-stretch

Make sure that a file at <path to your config file folder>/config.json and sqlite.db files exists before running it.

You do not need the <path to your db file folder>/sqlite.db line if you don't use the sqlite database.

Build the Docker image on your own

You can clone the repository and build the image, or you can just use the 'self-contained' Dockerfile: debian-stretch/selfcontained/Dockerfile