logo标签列表

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

postgresqldockerdocker-composepostgresql-9.5
59

使用docker-compose启动Postgres时立即关闭。使用的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 run命令以相同的镜像启动容器时，Postgres似乎可以正常工作。

docker run --name local-postgres9.5 -p 5432:5432 postgres:9.5
8
如果你的问题已经得到解决，请与我们分享！ - shuboy2014
就我个人而言，看起来这是故意的行为：https://github.com/docker-library/postgres/blob/36906949307e9b00e0f8f6f05b342c0db2dc816f/docker-entrypoint.sh#L284 - hagemt
你发布的日志中提到了解决方案。-----------------本地Postgres9.5 | 使用“-e POSTGRES_PASSWORD=password”来设置 - Anshumaan Bakshi
我也遇到了同样的问题，这让我很烦恼，因为我正在尝试对数据库运行liquibase。对我来说，情况是这样的：我的liquibase等待脚本看到数据库已经启动并运行，所以它尝试开始运行，然后像你提到的那样停止和启动服务器，在停止时，liquibase出现错误，因为它无法连接到数据库。如有建议，将不胜感激。 - Ray
@Ray 请查看这个解决方案：https://dev59.com/WVoU5IYBdhLWcg3wnoAP#71315084，它与你的情况相同... - s_bighead
4个回答
42

如果您查看日志输出，以下行将出现在末尾：

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.
2
问题在于它在启动、停止、重新启动时会两次显示“数据库系统已准备好接受连接”。 - Ray
第一次运行时我无法使其运行...它只是变得无响应，只有在我停止容器并再次运行时才能工作。 在启动容器之前，我使用docker rm container_name删除了先前创建的容器，然后再次使用docker-compose up --build --force-recreate运行。我的docker-compose.yml与上面的基本相同。即使这是我第一次创建容器，我也希望容器能够正常运行。我还尝试使用其他任何客户端（DBeaver、psql）连接，但它们都无法成功连接... - s_bighead
6

我正在使用与你相同的Postgres Docker镜像版本（9.5），并遇到了同样的问题。

在创建容器的第一次运行中，Postgres运行一系列命令，最后发送一个关闭信号，服务器变得无响应（但第二次及以后就正常工作）。

经过多次尝试，我发现一旦我尝试连接到服务器未准备好接受连接时，PostgresDB会意外关闭，并且任何试图远程连接（容器外部）的客户端都会出现同样的情况。

我在以下场景中遇到了这个错误 - 我有两个容器：一个是PostgresDB本身，另一个包含一个Postgres客户端（psql），试图连接到第一个容器来创建一些用户、数据库，并运行一个Liquibase脚本来创建所有的方案。

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

我可以通过在我的docker-compose.yml文件中添加一个healthcheck来解决此错误：

请查看下面的CHANGE 1和CHANGE 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。

希望能对你有所帮助！

3

我尝试了你的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。这个镜像正常工作。

2
谢谢。你是对的，Postgres实际上正在运行。我以为由于docker-compose没有超越启动postgres容器，所以这是个问题。当我使用-d选项时，一切似乎都正常工作了。 - arjunurs
如果数据目录不存在，容器运行并重新启动是正确的。这是因为官方镜像引导程序的脚本编写方式。更多细节请参见：https://stackoverflow.com/questions/65417340/docker-compose-postgres-restart-after-running-scripts-in-docker-entrypoint-initd/65417566#65417566 - hagemt
-6
请按照截图中的方式在docker-compose.yml文件下的postgres服务下添加密码。谢谢。 点击查看截图 
version: '3'
services:
     postgres:
          image: postgres
          environment:
              - POSTGRES_PASSWORD=postgres_password
1
请在您的答案中包含任何代码作为文本，这样人们可以轻松地复制并尝试它。此外，这使其对搜索引擎可见，因此可以在第一时间找到它。 - sainaen
网页内容由stack overflow 提供, 点击上面的
可以查看英文原文，
原文链接