-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Wrong DB being used for indexing #3503
Replies: 1 comment · 5 replies
-
What do you see when you run |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Beta Was this translation helpful? Give feedback.
All reactions
-
And what do you see when you enter the command |
Beta Was this translation helpful? Give feedback.
All reactions
-
mariadb has address 172.22.0.2 |
Beta Was this translation helpful? Give feedback.
All reactions
-
Could there be multiple photoprism instances? Did you properly restart as shown in our docs? |
Beta Was this translation helpful? Give feedback.
All reactions
-
Nope, single instance, docker pruned regularly to clean up stuff. Standard docker compose down, pull, up -d sequence. |
Beta Was this translation helpful? Give feedback.
-
Photoprism version: Build [230625-17242fb07] running in docker.
I switched from mysql to mariadb a few months ago.
I have both mariadb and mysql running in their own docker containers on the same virtual network as the photoprism container.
mariadb has IP 172.22.0.2 and hostname maruiadb.
mysql has IP 172.22.0.4 and hostname db.
My docker-compose.yml file explixitly refers to the mariadb host:
When I run
docker-compose exec photoprism photoprism index
I get the following errors at the end of the process:
Is there some config file somewhere that I need to update to make the indexing process hit the right database?
Beta Was this translation helpful? Give feedback.
All reactions