Postgresql Docker compose read connection reset by peer error on pipeline

当在管道中运行docker compose时，当管道上的测试使用mytainer的API时，我收到了这个错误.

panic: Get "http://localhost:8080/api/admin/folder": read tcp 127.0.0.1:60066->127.0.0.1:8080: read: connection reset by peer [recovered]

panic: Get "http://localhost:8080/api/admin/folder": read tcp 127.0.0.1:60066->127.0.0.1:8080: read: connection reset by peer

这是我的Ducker Copose文件:

version: "3"

volumes:
  postgres_vol:
    driver: local
    driver_opts:
      o: size=1000m
      device: tmpfs
      type: tmpfs

networks:
  mynetwork:
    driver: bridge

services:
  postgres:
    image: postgres:14
    container_name: postgres
    restart: always
    environment:
      - POSTGRES_USER=xxx
      - POSTGRES_PASSWORD=xxx
      - POSTGRES_DB=newdatabase
    volumes:
      #- ./postgres-init-db.sql:/docker-entrypoint-initdb.d/postgres-init-db.sql
      - "postgres_vol:/var/lib/postgresql/data"
    ports:
      - 5432:5432
    networks:
      - mynetwork

  mycontainer:
    image: myprivaterepo/mycontainer-image:1.0.0
    container_name: mycontainer
    restart: always
    environment:
      - DATABASE_HOST=postgres
      - DATABASE_PORT=5432
      - DATABASE_NAME=newdatabase
      - DATABASE_USERNAME=xxx
      - DATABASE_PASSWORD=xxx
      - DATABASE_SSL=false
    depends_on:
      - postgres
    ports:
      - 8080:8080
    networks:
      - mynetwork

mycontainer正在监听端口8080，本地一切正常.

然而，当我运行启动这个停靠器的管道时，Compose就是我得到错误的地方.

基本上，我正在运行一些使用mycontainerAPI(http://localhost:8080/api/admin/folder)的测试.

如果我在本地运行docker compose，并重新执行管道中遵循的步骤，以利用API，则一切正常.我可以通过本地主机与两个容器进行本地通信.

此外，我try 在容器上使用Health Checks，并在postgres中对mytainer&amp；127.0.0.1:5432:5432使用127.0.0.1:8080:8080(包括0.0.0.0:8080:8080&amp；0.0.0.0:5342:5432以防万一).

对此有什么 idea 吗？