https://www.spryker.com logo
Join Slack
Powered by
Hi guys when I try to run propel install in the C...
# docker
a
Hi guys when I try to run propel install in the CLI container I get this error Any clues?
Untitled
it seems like this container does not have
Copy code
SPRYKER_DB_*
env vars declared
I could work it around by just running the command propel:install in zed instead of the CLI container
now I have another question … why can’t I login to the DB from PHPStorm? The connection seems successful but it does not accept the password I tried both spryker/secret and root/secret … both did not work!
q
can you try 
localhost
instead of 
127.0.0.1
? (wild guess)
password is 
secret
?
a
I tried also 😄
the password is secret by default isnt it?
q
yes
a
I am using secret as password
a
on my system the database is called "postgres" and "eu-docker" is a schema.
a
I tried postgres also but did not work
thats why I changed it to eu-docker
what are other params that you are using?
a
No, no other parameters. Do you have another Postgress instance running on your machine, which would not know anything about the spryker user?!
q
what does your 
deploy.dev.yml
say?
any customization?
h
docker/sdk ps
Please, check that database is running @acoustic-businessperson-27970
May be you have MySQL/Maria instead of PGSQL running. Check it too
a
🙂
of course it is running, on port 5432
@quick-account-45953 no customization
h
Do you have 5432 port forwarded to the host? (it should be declared in deploy.yml file as separate tcp endpoint) Also please check that credentials in deploy.yml file for database.
a
yes
➜ nc -vz 0.0.0.0 5432 Connection to 0.0.0.0 port 5432 [tcp/postgresql] succeeded!
running this command
is success
the port is open on the host because it is forwarded from the Gateway container
Copy code
spryker_b2b_dev_gateway_1           /docker-entrypoint.sh ngin ...   Up             0.0.0.0:16379->16379/tcp,:::16379->16379/tcp, 0.0.0.0:443->443/tcp,:::443->443/tcp, 0.0.0.0:5432->5432/tcp,:::5432->5432/tcp, 0.0.0.0:5672->5672/tcp,:::5672->5672/tcp, 0.0.0.0:80->80/tcp,:::80->80/tcp, 0.0.0.0:9200->9200/tcp,:::9200->9200/tcp
h
Copy code
sudo lsof -nP -i4TCP:5432 | grep LISTEN
a
thank you
this last command listed 2 processes
😓
one of them is the vagrant box
that I forgot running
I shut it down and now it works
😄 1
h
😬
🙂
a
it is weird how did it start actually?
h
It seems they are listening on different adapters: 0.0.0.0 127.0.0.1
a
yeah maybe
ok thanks mate
Open in Slack
PreviousNext
Powered by