Weird! I guess you have tried tearing down the whole stack and only then changing the configuration? If it uses old volumes or containers, it could mean the new database and user are never created. Maybe you could also try looking into container logs to understand the error?
I'm using docker desktop for windows to run kubernetes .. the only thing that seems to work is to use the option to completely reset all the settings to the initial defaults and start over again! And yes I've tried looking at container logs, I forget what they said but it didn't really solve it for me.
I admit I only really understand the basics of kubernetes, I can't even find where docker desktop puts the volumes (it uses WSL aka "windows subsystem for linux" and think it somehow handles them internally) but I suspect if I could find them and delete them after deleting the pod, then changing the user or pass would work.. but what do I know!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Weird! I guess you have tried tearing down the whole stack and only then changing the configuration? If it uses old volumes or containers, it could mean the new database and user are never created. Maybe you could also try looking into container logs to understand the error?
I'm using docker desktop for windows to run kubernetes .. the only thing that seems to work is to use the option to completely reset all the settings to the initial defaults and start over again! And yes I've tried looking at container logs, I forget what they said but it didn't really solve it for me.
I admit I only really understand the basics of kubernetes, I can't even find where docker desktop puts the volumes (it uses WSL aka "windows subsystem for linux" and think it somehow handles them internally) but I suspect if I could find them and delete them after deleting the pod, then changing the user or pass would work.. but what do I know!