Error when running propel install in the CLI container

UM9F81RCP
UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet
edited June 2023 in Propel ORM

Hi guys

when I try to run propel install in the CLI container I get this error

Any clues?

Tagged:
Β«1

Comments

  • UM9F81RCP
    UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet

    it seems like this container does not have

    SPRYKER_DB_*
    

    env vars declared

  • UM9F81RCP
    UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet

    I could work it around by just running the command propel:install in zed instead of the CLI container

  • can you try localhost instead of 127.0.0.1? (wild guess)

  • password is secret ?

  • UM9F81RCP
    UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet

    I tried also πŸ˜„

  • UM9F81RCP
    UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet

    the password is secret by default isnt it?

  • UM9F81RCP
    UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet

    I am using secret as password

  • U01BV4LNUKZ
    U01BV4LNUKZ Posts: 9 πŸ§‘πŸ»β€πŸš€ - Cadet

    on my system the database is called "postgres" and "eu-docker" is a schema.

  • UM9F81RCP
    UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet

    I tried postgres also but did not work

  • UM9F81RCP
    UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet

    thats why I changed it to eu-docker

  • UM9F81RCP
    UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet

    what are other params that you are using?

  • U01BV4LNUKZ
    U01BV4LNUKZ Posts: 9 πŸ§‘πŸ»β€πŸš€ - Cadet

    No, no other parameters.
    Do you have another Postgress instance running on your machine, which would not know anything about the spryker user?!

  • what does your deploy.dev.yml say?

  • Unknown
    edited May 2021

    any customization?

  • sprymiker
    sprymiker Sprykee Posts: 781 πŸ§‘πŸ»β€πŸš€ - Cadet
    edited May 2021

    docker/sdk ps

    Please, check that database is running

    @UM9F81RCP

  • sprymiker
    sprymiker Sprykee Posts: 781 πŸ§‘πŸ»β€πŸš€ - Cadet

    May be you have MySQL/Maria instead of PGSQL running. Check it too

  • UM9F81RCP
    UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet

    πŸ™‚

  • UM9F81RCP
    UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet

    of course it is running, on port 5432

  • UM9F81RCP
    UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet

    @UJN2JRU4F no customization

  • sprymiker
    sprymiker Sprykee Posts: 781 πŸ§‘πŸ»β€πŸš€ - Cadet

    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.

  • UM9F81RCP
    UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet

    yes

  • UM9F81RCP
    UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet

    running this command

  • UM9F81RCP
    UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet

    ➜ nc -vz 0.0.0.0 5432

    Connection to 0.0.0.0 port 5432 [tcp/postgresql] succeeded!

  • UM9F81RCP
    UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet

    is success

  • UM9F81RCP
    UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet

    the port is open on the host because it is forwarded from the Gateway container

  • UM9F81RCP
    UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet
    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
    
  • sprymiker
    sprymiker Sprykee Posts: 781 πŸ§‘πŸ»β€πŸš€ - Cadet
    sudo lsof -nP -i4TCP:5432 | grep LISTEN
    
  • UM9F81RCP
    UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet

    thank you

  • UM9F81RCP
    UM9F81RCP Posts: 516 πŸ§‘πŸ»β€πŸš€ - Cadet

    this last command listed 2 processes