You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The example docker-compose.yaml file at this link does not work out of the box. I ran into the following errors and had to make the following non-obvious changes to get this server running with docker compose:
Photoprism can't connect to mariadb - connection is refused
To fix this you have to log into mariadb and create the photoprism user, since that is the user that appears in docker-compose.yaml
# When prompted for a password, just press enter without entering anything/
docker compose exec mariadb mariadb -u root -p
CREATE USER 'photoprism'@'%' IDENTIFIED BY 'insecure;
GRANT ALL PRIVILEGES ON *.* TO 'photoprism'@'%';
FLUSH PRIVILEGES;
Photoprism fails to startup with error: "unknown database 'photoprism'".
If you log into mariadb and run SHOW DATABASES; you'll notice there's no photoprism database. This is probably a bug in mariadb
as photoprism's mariadb configuration in docker-compose.yaml file does contain the environment variable: MARIADB_DATABASE=photoprism but it seems this is completely ignored by mariadb. I am not sure if this is the correct solution, but I got this to work by changing this line, so that photoprism uses the existing mysql database:
# OLDPHOTOPRISM_DATABASE_NAME: "photoprism"# MariaDB or MySQL database schema name# NEWPHOTOPRISM_DATABASE_NAME: "mysql"# MariaDB or MySQL database schema name
After these steps I'm able to navigate to localhost:2342 and see photoprism's landing page.
The text was updated successfully, but these errors were encountered:
1. What is not working as documented?
The example docker-compose.yaml file at this link does not work out of the box. I ran into the following errors and had to make the following non-obvious changes to get this server running with docker compose:
To fix this you have to log into mariadb and create the
photoprism
user, since that is the user that appears indocker-compose.yaml
If you log into mariadb and run
SHOW DATABASES;
you'll notice there's nophotoprism
database. This is probably a bug in mariadbas photoprism's
mariadb
configuration indocker-compose.yaml
file does contain the environment variable:MARIADB_DATABASE=photoprism
but it seems this is completely ignored by mariadb. I am not sure if this is the correct solution, but I got this to work by changing this line, so that photoprism uses the existingmysql
database:After these steps I'm able to navigate to localhost:2342 and see photoprism's landing page.
The text was updated successfully, but these errors were encountered: