“Postgres数据库系统已准备好接受连接”和Docker Compose

huangapple
go评论86阅读模式
英文:

Posgres "database system is ready to accept connections" and docker compose

问题

我是新手，正在尝试创建一个简单的.NET应用程序，在Docker容器中运行一些微服务。其中一个容器包含一个Postgres数据库。

我的docker-compose.yml文件如下所示....

我的docker-compose.override.yml文件如下所示....

阅读了一些其他StackOverflow帖子，我得出的印象是discountdb部分的healthcheck将确保Postgres连接保持打开，以便我的.NET服务可以运行其"seed"？

但是当我运行docker-compose -f docker-compose.yml -f .\docker-compose.override.yml up -d时，我在portainer中查看discountdb的日志时看到以下内容....

我漏掉了什么？我查看了其他一些解决方案，需要安装或运行shell命令，但我在这方面有些新手，不太熟悉如何做。

英文:

I am new to docker and trying to create a simple .NET app that runs some microservices in docker containers. One of the containers has a postgres database.

My docker-compose.yml file looks like this....

  1. version: '3.4'
  3. services:
  4.   catalogdb:
  5.     image: mongo
  7.   basketdb: 
  8.     image: redis:alpine
  10.   discountdb: 
  11.     image: postgres
  13.   portainer:
  14.     image: portainer/portainer-ce
  16.   catalog.api:
  17.     image: ${DOCKER_REGISTRY-}catalogapi
  18.     build:
  19.       context: .
  20.       dockerfile: Services/Catalog/Catalog.API/Dockerfile
  22.   basket.api:
  23.     image: ${DOCKER_REGISTRY-}basketapi
  24.     build:
  25.       context: .
  26.       dockerfile: Services/Basket/Basket.API/Dockerfile
  28.   discount.api:
  29.     image: ${DOCKER_REGISTRY-}discountapi
  30.     build:
  31.       context: .
  32.       dockerfile: Services/Discount/Discount.API/Dockerfile
  34. volumes:
  35.   mongo_data:
  36.   portainer_data:
  37.   postgres_data:

My docker-compose.override.yml file looks like this....

  1. version: '3.4'
  3. services:
  4.   catalogdb:
  5.     container_name: catalogdb
  6.     restart: always
  7.     ports:
  8.       - "27018:27017"
  9.     volumes:
  10.       - mongo_data:/data/db
  11.  
  12.   basketdb:
  13.     container_name: basketdb
  14.     restart: always
  15.     ports:
  16.       - "6379:6379"
  18.   discountdb:
  19.       container_name: discountdb
  20.       restart: always
  21.       ports: 
  22.         - "5430:5432"
  23.       command: postgres
  24.       environment:
  25.       - POSTGRES_USER=admin
  26.       - POSTGRES_PASSWORD=admin1234
  27.       - POSTGRES_DB=DiscountDb 
  28.       healthcheck:
  29.         test: [ "CMD-SHELL", "pg_isready -d $${POSTGRES_DB} -U $${POSTGRES_USER}" ]
  30.         interval: 10s
  31.         timeout: 5s
  32.         retries: 5
  33.       volumes:
  34.         - postgres_data:/var/lib/postgesql/data/ 
  36.   portainer:
  37.     container_name: portainer
  38.     restart: always
  39.     ports:
  40.       - "8080:8000"
  41.       - "9000:9000"      
  42.     volumes:
  43.     - /var/run/docker.sock:/var/run/docker.sock
  44.     - portainer_data:/data 
  46.   catalog.api:
  47.     container_name: catalog.api
  48.     environment:
  49.       - ASPNETCORE_ENVIRONMENT=Development
  50.       - "DatabaseSettings:ConnectionString=mongodb://catalogdb:27017"
  51.     depends_on:
  52.       - catalogdb
  53.     ports:
  54.       - "8000:80"
  56.   basket.api:
  57.     container_name: basket.api
  58.     environment:
  59.       - ASPNETCORE_ENVIRONMENT=Development
  60.       - "CacheSettings:ConnectionString=basketdb:6379"
  61.     depends_on:
  62.       - basketdb
  63.     ports:
  64.       - "8001:80"
  67.   discount.api:
  68.     container_name: discount.api
  69.     environment:
  70.       - ASPNETCORE_ENVIRONMENT=Development
  71.       - "DatabaseSettings:ConnectionString=Server=discountdb;Port=5430;Database=DiscountDb;User Id=admin;Password=admin1234;"
  72.     depends_on:
  73.       - discountdb
  74.     ports:
  75.       - "8002:80"

Reading some other StackOverflow items I was under the impression that the healthcheck portion of the discountdb section would ensure the postgres connection stays open so that my .net service can run it's "seed"?

But when I run

  1. docker-compose -f docker-compose.yml -f .\docker-compose.override.yml up -d

I see the following in my logs for the discountdb when I look at the log for that in portainer....

  1. This user must also own the server process.
  2. The database cluster will be initialized with locale "en_US.utf8".
  3. The default database encoding has accordingly been set to "UTF8".
  4. The default text search configuration will be set to "english".
  5. Data page checksums are disabled.
  6. fixing permissions on existing directory /var/lib/postgresql/data ... ok
  7. creating subdirectories ... ok
  8. selecting dynamic shared memory implementation ... posix
  9. selecting default max_connections ... 100
  10. selecting default shared_buffers ... 128MB
  11. selecting default time zone ... Etc/UTC
  12. creating configuration files ... ok
  13. running bootstrap script ... ok
  14. performing post-bootstrap initialization ... ok
  15. initdb: warning: enabling "trust" authentication for local connections
  16. initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
  17. syncing data to disk ... ok
  18. Success. You can now start the database server using:
  19.     pg_ctl -D /var/lib/postgresql/data -l logfile start
  20. waiting for server to start....2023-05-18 01:47:02.074 UTC [48] LOG:  starting PostgreSQL 15.3 (Debian 15.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
  21. 2023-05-18 01:47:02.076 UTC [48] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
  22. 2023-05-18 01:47:02.083 UTC [51] LOG:  database system was shut down at 2023-05-18 01:47:01 UTC
  23. 2023-05-18 01:47:02.090 UTC [48] LOG:  database system is ready to accept connections
  24.  done
  25. server started
  26. CREATE DATABASE
  27. /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
  28. waiting for server to shut down....2023-05-18 01:47:02.289 UTC [48] LOG:  received fast shutdown request
  29. 2023-05-18 01:47:02.291 UTC [48] LOG:  aborting any active transactions
  30. 2023-05-18 01:47:02.293 UTC [48] LOG:  background worker "logical replication launcher" (PID 54) exited with exit code 1
  31. 2023-05-18 01:47:02.293 UTC [49] LOG:  shutting down
  32. 2023-05-18 01:47:02.295 UTC [49] LOG:  checkpoint starting: shutdown immediate
  33. 2023-05-18 01:47:02.370 UTC [49] LOG:  checkpoint complete: wrote 918 buffers (5.6%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.015 s, sync=0.054 s, total=0.077 s; sync files=250, longest=0.003 s, average=0.001 s; distance=4217 kB, estimate=4217 kB
  34. 2023-05-18 01:47:02.377 UTC [48] LOG:  database system is shut down
  35.  done
  36. server stopped
  37. PostgreSQL init process complete; ready for start up.
  38. 2023-05-18 01:47:02.414 UTC [1] LOG:  starting PostgreSQL 15.3 (Debian 15.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
  39. 2023-05-18 01:47:02.414 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
  40. 2023-05-18 01:47:02.414 UTC [1] LOG:  listening on IPv6 address "::", port 5432
  41. 2023-05-18 01:47:02.418 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
  42. 2023-05-18 01:47:02.424 UTC [64] LOG:  database system was shut down at 2023-05-18 01:47:02 UTC
  43. 2023-05-18 01:47:02.429 UTC [1] LOG:  database system is ready to accept connections

What am I missing here? I've looked at other solutions that require installing or running shell commands, but I am somewhat of a noob here and not really familiar with how to do that?

答案1

得分: 1

Your containers all run within a network created by Docker Compose. That's how you can use the service names as hosts.

A common misconception about port mapping is that it has an effect within the network. It does not.

A mapping like "5430:5432" maps your host port 5430 to the container port 5432. This allows you to connect host applications to localhost:5430 in order to query the Postgres DB.

But within the network, all container ports are untouched. The Postgres DB is available on discountdb:5432.

In short, your DatabaseSettings:ConnectionString should use Server=discountdb;Port=5432.

英文:

Your containers all run within a network created by Docker Compose. That's how you can use the service names as hosts.

A common misconception about port mapping is that it has an effect within the network. It does not.

A mapping like "5430:5432" maps your host port 5430 to the container port 5432. This allows you to connect host applications to localhost:5430 in order to query the Postgres DB.

But within the network, all container ports are untouched. The Postgres DB is available on discountdb:5432.

In short, your DatabaseSettings:ConnectionString should use Server=discountdb;Port=5432.

huangapple
  • 本文由 发表于 2023年5月18日 09:49:39
  • 转载请务必保留本文链接：https://go.coder-hub.com/76277228.html
  • docker
  • docker-compose
  • postgresql
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定