Docker - How can run the psql command in the postgres container?

docker exec -it yiialkalmi_postgres_1 psql -U project -W project

Some explanation

docker exec -it The command to run a command to a running container. The it flags open an interactive tty. Basically it will cause to attach to the terminal. If you wanted to open the bash terminal you can do this

docker exec -it yiialkalmi_postgres_1 bash

yiialkalmi_postgres_1 The container name (you could use the container id instead, which in your case would be 40e39bd0329a )

psql -U project -W project The command to execute to the running container

U user

W Tell psql that the user needs to be prompted for the password at connection time. This parameter is optional. Without this parameter, there is an extra connection attempt which will usually find out that a password is needed, see the PostgreSQL docs.

project the database you want to connect to. There is no need for the -d parameter to mark it as the dbname when it is the first non-option argument, see the docs: -d "is equivalent to specifying dbname as the first non-option argument on the command line."

These are specified by you here

environment:
    POSTGRES_DB: project
    POSTGRES_USER: project
    POSTGRES_PASSWORD: project

---

If you need to restore the database in a container you can do this:

docker exec -i app_db_1 psql -U postgres < app_development.back

Don't forget to add -i.

:)

---

This worked for me:

goto bash :

docker exec -it <container-name> bash

from bash :

psql -U <dataBaseUserName> <dataBaseName>

or just this one-liner :

docker exec -it  <container-name> psql -U <dataBaseUserName> <dataBaseName>

helps ?

---

You can enter inside the postgres container using docker-compose by typing the following

docker-compose exec postgres bash

knowing that postgres is the name of the service. Replace it with the name of the Postgresql service in you docker-compose file.

if you have many docker-compose files, you have to add the specific docker-compose.yml file you want to execute the command with. Use the following commnand instead.

docker-compose -f < specific docker-compose.yml> exec postgres bash

For example if you want to run the command with a docker-compose file called local.yml, here the command will be

docker-compose -f local.yml exec postgres bash

Then, use psql command and specify the database name with the -d flag and the username with the -U flag

psql -U <database username you want to connect with> -d <database name>

Baammm!!!!! you are in.

---

After the Postgres container is configured using docker, open the bash terminal using:

docker exec -it <containerID>(postgres container name / ID) bash

Switch to the Postgres user:

su - postgres

Then run:

psql

It will open the terminal access for the Postgres.

---

If you have running "postgres" container:

docker run -it --rm --link postgres:postgres postgres:9.6 sh -c "exec psql -h \$POSTGRES_PORT_5432_TCP_ADDR -p \$POSTGRES_PORT_5432_TCP_PORT -U postgres"

---

We can enter the container with a terminal sh or bash by using,

docker run -it

if assume it is sh,

psql -U postgres

will work

---

Just fired up a local test, not sure if -c is what you were after from the cli.

docker run -it --rm --name psql-test-connection -e PGPASSWORD=1234 postgres psql -h kubernetes.docker.internal -U awx -c "\conninfo"

You are connected to database "awx" as user "awx" on host "kubernetes.docker.internal" (address "192.168.65.4") at port "5432".

---

RUN /etc/init.d/postgresql start &&\
    psql --command "CREATE USER docker WITH SUPERUSER PASSWORD 'docker';" &&\
    createdb -O docker docker &&\

---

In many common setups, the PostgreSQL port is published out to the host.

postgres:
  ports:
    - '12345:5432'

If this is the case, you don't need to do anything Docker-specific to connect to the database. You can use the psql client directly on your host system pointing to the first ports: number.

psql -h localhost -p 12345 -U project

This approach only requires psql or another ordinary PostgreSQL client be installed on the host and that the database container be configured with ports: making it accessible from outside Docker. (The ports: are not necessary for inter-container communication and a production-oriented setup could reasonably not have them.) This does not require the ability to run docker commands and the attendant security concerns, and it can avoid multiple layers of additional command quoting from a docker exec sh -c '...' sequence.

---