Docker: Provide multi-arch images

[nfbyte]

Currently there are two separate PhotoPrism repositories on Docker Hub for amd64 and arm64 under different names (photoprism and photoprism-arm64). This sucks for me especially because I use both arm64 and amd64 systems and I can't match deployment configuration between them due to this.

See:

• Docker documentation
• Multi-arch build and images

[lastzero]

So you need to deploy the same docker-compose.yml file on two different servers using different architectures? What if you put common config values in an extra .env file?

See https://docs.docker.com/compose/environment-variables/

[nfbyte]

It's not really about me, I know there are various band-aids that I can apply (and I do) but that still doesn't change the fact that configuration will be architecture-specific for no good reason.

Most software (all that I've encountered so far) uses multi-arch images.

[lastzero]

We have limited resources and it was easier for us to set it up like that. As it turns out, it didn't cause real issues to anyone so far - including you. That's great :)

We don't have time to change our infrastructure and docs on a daily basis. That's a good enough reason to do this later, when we have time & better funding. There's more than enough other items on our roadmap right now.

[kvalev]

If you are willing to switch to GitHub actions, I have a PR which already enables multi-arch builds. However the performance takes a hit as it is roughly 50% slower than your drone CI worker.

Anyway, multi-arch images are usually just a cosmetic thing, as there a usually other configuration parameters, which are architecture-specific, so you cant get around of using docker-compose overrides.

[nfbyte]

That's a good enough reason to do this later, when we have time & better funding.

That sounds perfectly reasonable.

as there a usually other configuration parameters, which are architecture-specific

This has not been true in my experience.

[yscialom]

Testing on my Raspberry Pi model 4B 2GB RAM.

Overall I'm pleased with PhotoPrism and havn't met major bug yet. Here is my docker-compose.yml for reference. Hope it helps. Let me know if you'd like some specifics on my experience.

version: "2"
services:
  photoprism:
    image: photoprism/photoprism:preview
    container_name: photoprism
    restart: unless-stopped
    security_opt:
      - seccomp:unconfined
      - apparmor:unconfined
    environment:
      UID: 1001
      GID: 1001
      TZ: "Europe/Paris"
      PHOTOPRISM_HTTP_COMPRESSION: "none"            # Improves transfer speed and bandwidth utilization (none or gzip)
      PHOTOPRISM_WORKERS: 2                          # Limits the number of indexing workers to reduce system load
      PHOTOPRISM_DEBUG: "false"                      # Run in debug mode (shows additional log messages)
      PHOTOPRISM_PUBLIC: "true"                      # No authentication required (disables password protection)
      PHOTOPRISM_READONLY: "true"                    # Don't modify originals directory (reduced functionality)
      PHOTOPRISM_EXPERIMENTAL: "false"               # Enables experimental features
      PHOTOPRISM_DISABLE_WEBDAV: "true"              # Disables built-in WebDAV server
      PHOTOPRISM_DISABLE_SETTINGS: "true"            # Disables Settings in Web UI
      PHOTOPRISM_DISABLE_TENSORFLOW: "true"          # Disables using TensorFlow for image classification
      PHOTOPRISM_DARKTABLE_PRESETS: "true"           # Enables Darktable presets and disables concurrent RAW conversion
      PHOTOPRISM_DETECT_NSFW: "false"                # Flag photos as private that MAY be offensive
      PHOTOPRISM_DATABASE_DRIVER: "sqlite"           # SQLite is an embedded database that doesn't require a server
      PHOTOPRISM_SITE_URL: "https://portfolio.(redacted)/"  # Public PhotoPrism URL
      PHOTOPRISM_SITE_TITLE: "Portfolio"
      PHOTOPRISM_SITE_AUTHOR: "Yankel Scialom"
    volumes:
      - "/media/raid1/applications/photoprism/data/var/lib/photoprism:/var/lib/photoprism"
      - "/media/raid1/applications/nextcloud/data/yscialom/files/Portfolio:/photoprism/originals/Portfolio:ro"
      - "/media/raid1/applications/photoprism/data/storage:/photoprism/storage"
    networks:
      - proxy
    dns:
      - 172.18.0.5
    labels:
      - "traefik.docker.network=proxy"
      - "traefik.enable=true"
      - "traefik.http.middlewares.photoprism-https-redirect.redirectscheme.scheme=https"
      - "traefik.http.routers.photoprism-secure.entrypoints=https"
      - "traefik.http.routers.photoprism-secure.middlewares=authelia@docker"
      - "traefik.http.routers.photoprism-secure.rule=Host(`portfolio.(redacted)`)"
      - "traefik.http.routers.photoprism-secure.service=photoprism"
      - "traefik.http.routers.photoprism-secure.tls=true"
      - "traefik.http.routers.photoprism.entrypoints=http"
      - "traefik.http.routers.photoprism.middlewares=photoprism-https-redirect"
      - "traefik.http.routers.photoprism.rule=Host(`portfolio.(redacted)`)"
      - "traefik.http.services.photoprism.loadbalancer.server.port=2342"

networks:
  proxy:
    external:
      name: proxy

[lastzero]

New multi-arch development base image available soon! Comes with Go 1.17. I've also improved related config files and build scripts to fix potential issues.

Developers must pull the latest image and rebuild their container(s): The database service has been renamed from photoprism-db to mariadb, to match our production examples. The default config values and Makefile may be incompatible otherwise.

docker-compose stop
docker-compose pull
docker-compose build
docker-compose up