luisgulo/photoprism
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Docker: Update ARM64 docs

Browse source 
Signed-off-by: Michael Mayer <michael@liquidbytes.net>
This commit is contained in:
Michael Mayer 2021-12-25 20:40:57 +01:00
parent 781d8e8a03
commit ef4fde9ca8
2 changed files with 14 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docker/examples/arm64/README
View file

@ -13,7 +13,16 @@ servers apply:
To ensure compatibility with 64-bit Docker images, your Raspberry Pi 3 / 4 must boot with the "arm_64bit=1"
flag in its config.txt file (https://www.raspberrypi.org/documentation/installation/installing-images/README.md).
An "exec format" or "no matching manifest" error will occur otherwise.
An "exec format" error will occur otherwise.
### No Matching Manifest ###
Try explicitly pulling the ARM64 version if you've booted your device with the "arm_64bit=1" flag
and you see the "no matching manifest" error on Raspberry Pi OS (Raspbian):
docker pull --platform=arm64 photoprism/photoprism:latest
It may also help to set the DOCKER_DEFAULT_PLATFORM environment variable to "linux/arm64".
Alternatively, you can run your device with [UbuntuDockerPi](https://github.com/guysoft/UbuntuDockerPi).
It's a 64-bit Ubuntu Server with Docker pre-configured.

4
docker/examples/arm64/docker-compose.yml
View file

@ -4,7 +4,9 @@ version: '3.5'
#
# Note:
# - You have to boot your Raspberry Pi 3/4 with the parameter "arm_64bit=1" in config.txt to use our ARM64 (64-bit) image.
# An "exec format" or "no matching manifest" error will occur otherwise.
# An "exec format" error will occur otherwise.
# - Try explicitly pulling the ARM64 version if you've booted your device with the "arm_64bit=1" flag and you see
# the "no matching manifest" error on Raspberry Pi OS (Raspbian). See documentation for details.
# - Use https://dl.photoprism.app/docker/armv7/docker-compose.yml for running PhotoPrism on ARMv7-based (32-bit) devices.
# - Running PhotoPrism on a server with less than 4 GB of swap space or setting a memory/swap limit can cause unexpected
# restarts ("crashes"), especially when the indexer temporarily needs more memory to process large files.