I keep Getting a database error. Pls. help

[EmbraRoot]

I have tried the docker install my self and with linode and still i get the same error.

[drostangreen]

The path in the docs for postgres is incorrect with the latest release of postgres. Change the line in your docker compose from:

- pgdata:/var/lib/postgresql/data

to:

- pgdata:/var/lib/postgresql/

That fixed it for me. I saw a PR with someone with this fix as well.

[davidrunsfromtheyeti-maker]

I have changed the path to the correct one and even rebooted my server on linode. Still getting the same message as above. What else should I be looking for?

[davidrunsfromtheyeti-maker]

Something is broken... I just don't have a clue what it is. I'm new to linode but it shouldn't be this difficult.

[drostangreen]

I am not related to the team but I can try to help. Did you review the postgres container logs to see what is happening? That will likely point you in the right direction. You can also send your docker compose file and we can review it for anything obvious.

[emmettj2005]

I had this issue myself when setting up peppermint for the first time a just few days ago. Here's how I fixed it:

I'm getting a database error upon login, postgres logs show it crashes immediately upon starting, and peppermint logs show it sees nothing where the database should be (presumably because it never started)

docker compose down - take down everything related to peppermint
docker volume rm peppermint_pgdata - remove volume so we're starting from scratch next time we start it up
sudo nano docker-compose.yml - change pgdata from /var/lib/postgresql/data to /var/lib/postgresql

docker compose up -d - start peppermint
Still getting the same database error upon login, postgres logs now show it started properly, and peppermint logs still showing no database found

docker compose down
docker volume rm peppermint_pgdata
sudo nano docker-compose.yml - change pgdata back to /var/lib/postgresql/data, add new line PGDATA: /var/lib/postgresql/data under services: peppermint_postgres: environment:

docker compose up -d
Everything is the same as before: postgres works and peppermint has a database error. I believe this is better than the other postgres solution though, because if the default location changes yet again, your system will keep working as it did before rather than breaking.

docker compose down
docker volume rm peppermint_pgdata
sudo nano docker-compose.yml - after some research, I found out that the password needs to be stored with percent encoding on the peppermint side of things. Remember, leave it in plaintext under services: peppermint_postgres: environment: POSTGRES_PASSWORD: , only change it in services: peppermint: environment: DB_PASSWORD: For example, the password gh(fdj@dfj& should be stored as gh%28fdj%40dfj%26 in order for peppermint to access the database properly. See the Mozilla Percent Encoding Guide for a complete list of translations.

docker compose up -d
IT WORKS! IT FINALLY WORKS!!

[n1smithy]

Hello, as this topic is 2 months old the docker-compose.yml-code in the installation-manual still hasn't been updated. I had the same issue here and just could solve it after looking into the discussion-section on github (here). I guess, some people won't get along with peppermint if the docs won't be adjusted. Just my 2 cents

[Ludm3ister]

Hello! I had the same issue but I found a solution for it.

I used Docker Desktop to run this.

On the files, go to docker-compose (there's 3 files like that, choose the one that does not have .local or .dev in the end)

Open it with an editor (Notepad/VSCode etc)

Make this change:

Current -> image: postgres:latest
Update it to -> image: postgres:15

Save

Open PowerShell on the folder where you have saved the files (Shift + Right Click)

Restart everything ( docker compose down -v & docker compose up -d )

Verify it works

Run:

docker compose ps

You should see:

peppermint_postgres Up
peppermint Up

❌ NOT “Restarting”

Then open the app (For me it was http://localhost:1000; check on Docker on which port it has been assigned)

There it is :D

Hopefully it was somewhat helpful!