I am using the right credentials as mentioned in deploy.dev.yml but not sure its failing to connect.

U0215B7E8T1

I am using the right credentials as mentioned in deploy.dev.yml but not sure its failing to connect.

U024CDD2S5A

Has you lloked it the db container is running in docker and the password is secret right? Has you use by the bootstrap the deploy.dev.yml when you set up the envoirment?

U0215B7E8T1

Yes it was running. Looks like I need to run below command
docker/sdk clean-data && docker/sdk up --data && docker/sdk console q:w:s -v -s

U01SE4SRCU9

I don't know about Docker but I had the same issue with Vagrant and there the problem was that due to a port collision, Vagrant forwarded 5432 to some other port. So if Docker provides any details upon launch about port forwarding, check those and see if it maybe had a similar issue and redirected 5432 to some other port. If yes, then enter that port into PHPStorm instead of 5432.

U0215B7E8T1

looks like running docker/sdk clean-data && docker/sdk up --data && docker/sdk console q:w:s -v -s didnot solve my problem. @valerii.trots @U01AHAH9478 and experts kindly help.

U0215B7E8T1

please see that it shows spryker user doesnt exist

U01SE4SRCU9

Did you check the port issue? In my case, the user not existing was exactly because it was trying to connect to the wrong place (instead of the shop's db) where such a user did not exist indeed.

U0215B7E8T1

Issue solved. thank you @U01SE4SRCU9

U01SE4SRCU9

So it was indeed the port? 🙂 You're welcome, @U0215B7E8T1

U0215B7E8T1

true it was the port already in use as I was running postgre on native machine.

U0215B7E8T1

thank you again

U01SE4SRCU9

bingo... 👍 yw 🙂