Postgres 在使用 docker-compose 启动时立即关闭

Postgres shuts down immediately when started with docker-compose

Postgres 在使用 docker-compose 启动时立即关闭。使用的yaml文件如下

version: '2'

services:   
    postgres:
        image: postgres:9.5
        container_name: local-postgres9.5
        ports:
          - "5432:5432"

执行docker-compose up命令时的日志

Creating local-postgres9.5
Attaching to local-postgres9.5
local-postgres9.5 | The files belonging to this database system will be owned by user "postgres".
local-postgres9.5 | This user must also own the server process.
local-postgres9.5 |
local-postgres9.5 | The database cluster will be initialized with locale "en_US.utf8".
local-postgres9.5 | The default database encoding has accordingly been set to "UTF8".
local-postgres9.5 | The default text search configuration will be set to "english".
local-postgres9.5 |
local-postgres9.5 | Data page checksums are disabled.
local-postgres9.5 |
local-postgres9.5 | fixing permissions on existing directory /var/lib/postgresql/data ... ok
local-postgres9.5 | creating subdirectories ... ok
local-postgres9.5 | selecting default max_connections ... 100
local-postgres9.5 | selecting default shared_buffers ... 128MB
local-postgres9.5 | selecting dynamic shared memory implementation ... posix
local-postgres9.5 | creating configuration files ... ok
local-postgres9.5 | creating template1 database in /var/lib/postgresql/data/base/1 ... ok
local-postgres9.5 | initializing pg_authid ... ok
local-postgres9.5 | initializing dependencies ... ok
local-postgres9.5 | creating system views ... ok
local-postgres9.5 | loading system objects' descriptions ... ok
local-postgres9.5 | creating collations ... ok
local-postgres9.5 | creating conversions ... ok
local-postgres9.5 | creating dictionaries ... ok
local-postgres9.5 | setting privileges on built-in objects ... ok
local-postgres9.5 | creating information schema ... ok
local-postgres9.5 | loading PL/pgSQL server-side language ... ok
local-postgres9.5 | vacuuming database template1 ... ok
local-postgres9.5 | copying template1 to template0 ... ok
local-postgres9.5 | copying template1 to postgres ... ok
local-postgres9.5 | syncing data to disk ... ok
local-postgres9.5 |
local-postgres9.5 | WARNING: enabling "trust" authentication for local connections
local-postgres9.5 | You can change this by editing pg_hba.conf or using the option -A, or
local-postgres9.5 | --auth-local and --auth-host, the next time you run initdb.
local-postgres9.5 |
local-postgres9.5 | Success. You can now start the database server using:
local-postgres9.5 |
local-postgres9.5 |     pg_ctl -D /var/lib/postgresql/data -l logfile start
local-postgres9.5 |
local-postgres9.5 | ****************************************************
local-postgres9.5 | WARNING: No password has been set for the database.
local-postgres9.5 |          This will allow anyone with access to the
local-postgres9.5 |          Postgres port to access your database. In
local-postgres9.5 |          Docker's default configuration, this is
local-postgres9.5 |          effectively any other container on the same
local-postgres9.5 |          system.
local-postgres9.5 |
local-postgres9.5 |          Use "-e POSTGRES_PASSWORD=password" to set
local-postgres9.5 |          it in "docker run".
local-postgres9.5 | ****************************************************
local-postgres9.5 | waiting for server to start....LOG:  database system was shut down at 2016-05-16 16:51:54 UTC
local-postgres9.5 | LOG:  MultiXact member wraparound protections are now enabled
local-postgres9.5 | LOG:  database system is ready to accept connections
local-postgres9.5 | LOG:  autovacuum launcher started
local-postgres9.5 |  done
local-postgres9.5 | server started
local-postgres9.5 | ALTER ROLE
local-postgres9.5 |
local-postgres9.5 |
local-postgres9.5 | /docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
local-postgres9.5 |
local-postgres9.5 | LOG:  received fast shutdown request
local-postgres9.5 | LOG:  aborting any active transactions
local-postgres9.5 | LOG:  autovacuum launcher shutting down
local-postgres9.5 | LOG:  shutting down
local-postgres9.5 | waiting for server to shut down....LOG:  database system is shut down
local-postgres9.5 |  done
local-postgres9.5 | server stopped
local-postgres9.5 |
local-postgres9.5 | PostgreSQL init process complete; ready for start up.
local-postgres9.5 |
local-postgres9.5 | LOG:  database system was shut down at 2016-05-16 16:51:55 UTC
local-postgres9.5 | LOG:  MultiXact member wraparound protections are now enabled
local-postgres9.5 | LOG:  database system is ready to accept connections
local-postgres9.5 | LOG:  autovacuum launcher started

当容器启动时使用与 docker 运行

相同的图像,Postgres 似乎工作正常
docker run --name local-postgres9.5 -p 5432:5432 postgres:9.5

我尝试了您的 docker-compose,服务似乎 运行 在容器中:

root@0afe99de0f0b:/# ps aux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
postgres     1  0.5  0.8 227148 16128 ?        Ss   14:42   0:00 postgres
postgres    74  0.0  0.0 227148  1768 ?        Ss   14:42   0:00 postgres: checkpointer process  
postgres    75  0.0  0.0 227148  1772 ?        Ss   14:42   0:00 postgres: writer process  
postgres    76  0.0  0.0 227148  1768 ?        Ss   14:42   0:00 postgres: wal writer process  
postgres    77  0.0  0.1 227576  2720 ?        Ss   14:42   0:00 postgres: autovacuum launcher process  
postgres    78  0.0  0.0  82132  1888 ?        Ss   14:42   0:00 postgres: stats collector process  
root        79  2.0  0.0  21820  1984 ?        Ss   14:42   0:00 /bin/bash
root        84  0.0  0.0  19092  1296 ?        R+   14:42   0:00 ps aux

无论如何,对于我的项目,我使用另一个 postgresql 图像:https://github.com/sameersbn/docker-postgresql。这个很好用。

如果您查看日志输出,将在末尾显示以下行:

local-postgres9.5 | server stopped
local-postgres9.5 |
local-postgres9.5 | PostgreSQL init process complete; ready for start up.

显然,停止并重新启动 Postgres 服务器是初始化过程的一部分。事实上,倒数第二行说

local-postgres9.5 | LOG:  database system is ready to accept connections.

在 docker-compose.yml 中的 postgres 服务下添加密码,如屏幕截图所示。谢谢你。 click to see the screenshot

version: '3'
services:
     postgres:
          image: postgres
          environment:
              - POSTGRES_PASSWORD=postgres_password

我使用的是与您 (9.5) 相同的 Postgres docker 图像版本,我 运行 遇到了同样的问题。

第一次创建容器时,Postgres 运行 一系列命令,最后,它只是发送一个关闭信号,服务器变得无响应(但第二次开始工作)。

经过几次尝试,我发现一旦我尝试连接到服务器,在它准备好接受连接之前PostgresDB 会意外关闭,对于任何尝试远程连接(在容器外)的客户端,都会发生同样的情况。

我在以下情况下遇到此错误 - 我有两个容器:一个用于 PostgresDB 本身,另一个包含尝试连接到第一个容器以创建一些用户的 Postgres 客户端 (psql) 、数据库和 运行 创建所有模式的 liquibase 脚本。

起初,我在 bash 脚本中使用了一个循环,每 5 秒检查一次服务器是否可用,然后在第一次尝试后,Postgres 发出关闭信号并变得无响应。

我可以通过在 docker-compose.yml:

中添加 healthcheck 来消除这个错误

查看下面的 CHANGE 1CHANGE 2 评论

version: '3.9'
services:
  postgres-db:
    container_name: ${POSTGRES_HOST}
    image: postgres:9.5
    restart: always
    ports:
      - "5432:5432"
    command: postgres
    expose:
      - 5432
    environment:
      POSTGRES_USER: "${POSTGRES_USER}"
      POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}"
      POSTGRES_DB: "${POSTGRES_DB}"

      #this ENV variable is only required for the healthcheck section - if you don't specify it, the check command will fail stating the root user doesn't exist in posgres
      PGUSER: "postgres"
    healthcheck:
      #CHANGE 1: this command checks if the database is ready, right on the source db server
      test: [ "CMD-SHELL", "pg_isready" ]
      interval: 5s
      timeout: 5s
      retries: 5

  liquibase:
    container_name: liquibase-schema-config
    image: company/liquibase
    build:
      context: ./liquibase
    environment:
      - PGPASSWORD=${POSTGRES_PASSWORD}
      - PGPORT=${POSTGRES_PORT}
      - PGHOST=${POSTGRES_HOST}
      - PGUSER=${POSTGRES_USER}
      - PGDATABASE=${POSTGRES_DB}

      - JDBC_URL=jdbc:postgresql://${POSTGRES_HOST}:${POSTGRES_PORT}/
      - LIQUIBASE_HOME=${LIQUIBASE_HOME}
    depends_on:
      #CHANGE 2: it prevents issuing a request while the server is starting to depend on the healthy status of postgres-db 
      postgres-db:
        condition: service_healthy

编辑:在 Linux 上使用 Cisco AnyConnect 时,还有另一个问题阻止 Docker 访问受 VPN 保护的站点(甚至互联网站点)(在 MacOS 上不会发生)。为了避免这种不需​​要的行为,我在 Ubuntu 上安装了 openconnect sudo apt install openconnect 并停止使用 AnyConnect。

希望对您有所帮助!