5.4 KiB

Executable File

Czysty Wina Historia

linuxserver/piwigo

Piwigo is a photo gallery software for the web that comes with powerful features to publish and manage your collection of pictures.

Supported Architectures

Our images support multiple architectures such as x86-64, arm64 and armhf. We utilise the docker manifest for multi-platform awareness. More information is available from docker here.

Simply pulling linuxserver/piwigo should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

Architecture	Tag
x86-64	amd64-latest
arm64	arm64v8-latest
armhf	arm32v6-latest

Usage

Here are some example snippets to help you get started creating a container from this image.

docker

docker create \
  --name=piwigo \
  -e PUID=1001 \
  -e PGID=1001 \
  -e TZ=Europe/London \
  -p 80:80 \
  -v </path/to/appdata/config>:/config \
  --restart unless-stopped \
  linuxserver/piwigo

docker-compose

Compatible with docker-compose v2 schemas.

---
version: "2"
services:
  piwigo:
    image: linuxserver/piwigo
    container_name: piwigo
    environment:
      - PUID=1001
      - PGID=1001
      - TZ=Europe/London
    volumes:
      - </path/to/appdata/config>:/config
    ports:
      - 80:80
    mem_limit: 4096m
    restart: unless-stopped

Parameters

Docker images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.

Ports (`-p`)

Parameter	Function
`80`	Application WebUI

Environment Variables (`-e`)

Env	Function
`PUID=1001`	for UserID - see below for explanation
`PGID=1001`	for GroupID - see below for explanation
`TZ=Europe/London`	Specify a timezone to use EG Europe/London.

Volume Mappings (`-v`)

Volume	Function
`/config`	Configuration files.

User / Group Identifiers

When using volumes (-v flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=1001 and PGID=1001, to find yours use id user as below:

  $ id username
    uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)

Application Setup

You must create a user and database for piwigo to use in a mysql/mariadb server.
In the setup page for database, use the ip address rather than hostname.
A basic nginx configuration file can be found in /config/nginx/site-confs, edit the file to enable ssl (port 443 by default), set servername etc.
Self-signed keys are generated the first time you run the container and can be found in /config/keys, if needed, you can replace them with your own.
The easiest way to edit the configuration file is to enable local files editor from the plugins page and use it to configure email settings etc.

Support Info

Shell access whilst the container is running:
- docker exec -it piwigo /bin/bash
To monitor the logs of the container in realtime:
- docker logs -f piwigo
Container version number
- docker inspect -f '{{ index .Config.Labels "build_version" }}' piwigo
Image version number
- docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/piwigo

Versions

22.02.19: - Rebasing to alpine 3.9, add php-ldap.
28.01.19: - Rebase to alpine linux 3.8 , add pipeline logic and multi arch.
25.01.18: - Rebase to alpine linux 3.7.
25.05.17: - Rebase to alpine linux 3.6.
03.05.17: - Use repo pinning to better solve dependencies, use repo version of php7-imagick.
20.04.17: - Add php7-exif package, thanks iiska
23.02.17: - Rebase to alpine linux 3.5 and nginx.
14.10.16: - Add version layer information.
10.09.16: - Add layer badges to README.
29.08.15: - Initial Release.

5.4 KiB Executable File Czysty Wina Historia