GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Docker Pulls Docker Stars Jenkins Build LSIO CI

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 and our announcement here.

Simply pulling 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:









Application Setup

Docker image update and recreation of container alone won't update Piwigo version. In order to update Piwigo version, firstly make sure you are using the latest docker image, then go to Admin->Tools->Updates and use the app updater.

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


To help you get started creating a container from this image you can either use docker-compose or the docker cli.

version: "2.1"
container_name: piwigo
- PUID=1000
- PGID=1000
- TZ=Europe/London
- </path/to/appdata/config>:/config
- </path/to/appdata/gallery>:/gallery
- 80:80
restart: unless-stopped

docker run -d \
--name=piwigo \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Europe/London \
-p 80:80 \
-v </path/to/appdata/config>:/config \
-v </path/to/appdata/gallery>:/gallery \
--restart unless-stopped \


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)




Application WebUI

Environment Variables (-e)




for UserID - see below for explanation


for GroupID - see below for explanation


Specify a timezone to use EG Europe/London.

Volume Mappings (-v)




Configuration files.


Image, plugin, & theme storage for Piwigo

Environment variables from files (Docker secrets)

You can set any environment variable from a file by using a special prepend FILE__.

As an example:

-e FILE__PASSWORD=/run/secrets/mysecretpassword

Will set the environment variable PASSWORD based on the contents of the /run/secrets/mysecretpassword file.

Umask for running applications

For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.

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=1000 and PGID=1000, to find yours use id user as below:

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

Docker Mods

Docker Mods Docker Universal Mods

We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.

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" }}'


  • 29.06.21: - Rebase to 3.14, Add php7-zip package

  • 20.05.21: - Create separate volume for image data

  • 23.01.21: - Rebasing to alpine 3.13.

  • 12.12.20: - Increased upload_max_filesize in php.ini

  • 01.06.20: - Rebasing to alpine 3.12.

  • 19.12.19: - Rebasing to alpine 3.11.

  • 28.06.19: - Rebasing to alpine 3.10.

  • 12.06.19: - Add ffmpeg and other deps as needed by popular plugins.

  • 23.03.19: - Switching to new Base images, shift to arm32v7 tag.

  • 01.03.19: - Add php-ctype & php-curl.

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