The LinuxServer.io team brings you another container release featuring :-

• regular and timely application updates
• easy user mappings (PGID, PUID)
• custom base image with s6 overlay
• weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
• regular security updates

Find us at:

• Discord - realtime support / chat with the community and the team.
• IRC - on freenode at #linuxserver.io. Our primary support channel is Discord.
• Blog - all the things you can do with our containers including How-To guides, opinions and much more!

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

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

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

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

Compatible with docker-compose v2 schemas.

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

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

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)

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

• 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

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.

Below are the instructions for updating containers:

• Update the image: docker pull linuxserver/piwigo
• Stop the running container: docker stop piwigo
• Delete the container: docker rm piwigo
• Recreate a new container with the same docker create parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
• Start the new container: docker start piwigo
• You can also remove the old dangling images: docker image prune

• Update all images: docker-compose pull
  • or update a single image: docker-compose pull piwigo
• Let compose update all containers as necessary: docker-compose up -d
  • or update a single container: docker-compose up -d piwigo
• You can also remove the old dangling images: docker image prune

• Pull the latest image at its tag and replace it with the same env variables in one run:

  docker run --rm \
  -v /var/run/docker.sock:/var/run/docker.sock \
  containrrr/watchtower \
  --run-once piwigo
  

• You can also remove the old dangling images: docker image prune

If you want to make local modifications to these images for development purposes or just to customize the logic:

git clone https://github.com/linuxserver/docker-piwigo.git
cd docker-piwigo
docker build \
  --no-cache \
  --pull \
  -t linuxserver/piwigo:latest .

The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static

docker run --rm --privileged multiarch/qemu-user-static:register --reset

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

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