Skip to content
Discussion options

You must be logged in to vote

Hello ! I got the same problem and for me it was due to the volume creation of docker you can check that with :

docker volume ls

I'm not an expert in Docker but I think if you change the password in the .env it does not create a new volume or use the old one to connect with your new password and that will obviously not work.

From this constatation you have 2 solution the first one is more or less "brutforce" and it worked for me the second one is maybe more smart but i didn't test it:

  1. Delete the old volume and build the image again with docker-compose

docker volume rm <old_db_volume_id>

or to delete every single volume

docker volume rm $(docker volume ls)

then build your project i…

Replies: 6 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by YuriiMotov
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
5 participants
Converted from issue

This discussion was converted from issue #344 on September 01, 2025 16:24.