[Bug] [Help] 过一段时间之后容器会停止运行，求助如何打印详细日志

[ChangeHow]

📦 部署环境

Docker

📦 部署模式

服务端模式(lobe-chat-database 镜像)

📌 软件版本

latest

💻 系统环境

Other Linux, Ubuntu

🌐 浏览器

Chrome

🐛 问题描述

我在服务器上部署了 database 版本，最近频繁出现容器自动停止的情况；但是日志输出只有 info 级别的输出，不知道具体是什么问题导致的：

这个是我的 docker composer 配置：

lobe:
    image: lobehub/lobe-chat-database:latest
    container_name: lobe-chat
    network_mode: 'service:network-service'
    depends_on:
      postgresql:
        condition: service_healthy
      network-service:
        condition: service_started
      minio:
        condition: service_started

    environment:
      - 'APP_URL=https://****'
      # https://lobehub.com/zh/docs/self-hosting/environment-variables/auth
      - 'AUTH_URL=https://****/api/auth'
      - 'NEXTAUTH_URL=https://****'
      - 'NEXT_AUTH_SECRET=NX2ka********re5RfoT7hg'
      - 'NEXT_AUTH_SSO_PROVIDERS=generic-oidc' 
      - 'AUTH_GENERIC_OIDC_ID=67a********99231ea3a28'
      - 'AUTH_GENERIC_OIDC_SECRET=1a21bf********eaa712ee9ffa2e'
      - 'AUTH_GENERIC_OIDC_ISSUER=https://****authing.cn/oidc'
      - 'KEY_VAULTS_SECRET=Kix2wcUONd4CX51E********4wzJgKjPtz2sGztqQ='
      - 'DATABASE_URL=postgresql://postgres:${POSTGRES_PASSWORD}@postgresql:5432/${LOBE_DB_NAME}'
      - 'S3_ENDPOINT=http://127.0.0.1:${MINIO_PORT}'
      - 'S3_BUCKET=${MINIO_LOBE_BUCKET}'
      - 'S3_PUBLIC_DOMAIN=http://127.0.0.1:${MINIO_PORT}'
      - 'S3_ENABLE_PATH_STYLE=1'
      - 'LLM_VISION_IMAGE_USE_BASE64=1'
    env_file:
      - .env
    restart: on-failure:3

  watchtower:
    image: containrrr/watchtower
    container_name: watchtower
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - WATCHTOWER_CLEANUP=true
      - WATCHTOWER_POLL_INTERVAL=300
    command: --interval 300 lobe-chat
    restart: always
    networks:
      - lobe-networ

可能是 watchover 重新拉取镜像导致自动重启失败的原因吗？

📷 复现步骤

暂无稳定复现步骤

🚦 期望结果

No response

📝 补充信息

No response

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

📦 Deployment environment

Docker

📦 Deployment mode

Server-side mode (lobe-chat-database mirror)

📌 Software version

Latest

💻 System environment

Other Linux, Ubuntu

🌐 Browser

Chrome

🐛 Question description

I have deployed the database version on the server, and the container has been stopped automatically recently frequently; but the log output only has info-level output, so I don’t know what the specific problem is causing:

This is my docker composer configuration:

lobe:
    image: lobehub/lobe-chat-database:latest
    container_name: lobe-chat
    network_mode: 'service:network-service'
    depends_on:
      postgresql:
        condition: service_healthy
      network-service:
        condition: service_started
      minio:
        condition: service_started

    environment:
      - 'APP_URL=https://****'
      # https://lobehub.com/zh/docs/self-hosting/environment-variables/auth
      - 'AUTH_URL=https://****/api/auth'
      - 'NEXTAUTH_URL=https://****'
      - 'NEXT_AUTH_SECRET=NX2ka******re5RfoT7hg'
      - 'NEXT_AUTH_SSO_PROVIDERS=generic-oidc'
      - 'AUTH_GENERIC_OIDC_ID=67a*********99231ea3a28'
      - 'AUTH_GENERIC_OIDC_SECRET=1a21bf*********eaa712ee9ffa2e'
      - 'AUTH_GENERIC_OIDC_ISSUER=https://****authing.cn/oidc'
      - 'KEY_VAULTS_SECRET=Kix2wcUONd4CX51E******4wzJgKjPtz2sGztqQ='
      - 'DATABASE_URL=postgresql://postgres:${POSTGRES_PASSWORD}@postgresql:5432/${LOBE_DB_NAME}'
      - 'S3_ENDPOINT=http://127.0.0.1:${MINIO_PORT}'
      - 'S3_BUCKET=${MINIO_LOBE_BUCKET}'
      - 'S3_PUBLIC_DOMAIN=http://127.0.0.1:${MINIO_PORT}'
      - 'S3_ENABLE_PATH_STYLE=1'
      - 'LLM_VISION_IMAGE_USE_BASE64=1'
    env_file:
      - .env
    restart: on-failure:3

  watchtower:
    image: containsrrr/watchtower
    container_name: watchtower
    Volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - WATCHTOWER_CLEANUP=true
      - WATCHTOWER_POLL_INTERVAL=300
    command: --interval 300 lobe-chat
    restart: always
    networks:
      - lobe-networ

Could it be the reason why watchover re-pulls the image and causes the automatic restart to fail?

📷 Reproduction steps

No stable reproduction steps yet

🚦 Expected results

No response

📝 Supplementary information

No response

[lobehubbot]

👀 @ChangeHow

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[dosubot[bot]]

@ChangeHow 你好！我是Dosu，我是一个可以帮助你解决 bug、回答问题并成为贡献者的机器人。我会在等待人类维护者的时候帮助你。祝你有愉快的一天！🤖

To address the issue of your Docker container stopping unexpectedly and to enable more detailed logging, you can take the following steps:

1. Increase Logging Verbosity:

   • If the current logging level is set to info, you might want to increase it to debug to capture more detailed logs. Check if the application or Docker setup allows configuring the log level through environment variables or configuration files.

2. Check Watchtower Configuration:

   • The watchtower service is configured to automatically update the lobe-chat container every 300 seconds. This could potentially cause the container to restart if a new image is pulled. You can try disabling the automatic updates temporarily to see if it resolves the issue by removing or commenting out the watchtower service in your docker-compose.yml.

3. Review Restart Policy:

   • The restart: on-failure:3 policy will attempt to restart the container up to 3 times if it exits with a non-zero status. If the container stops after these attempts, it might indicate a persistent issue. Consider checking the logs for any error messages that occur just before the container stops.

4. Inspect Logs for Errors:

   • Use docker logs lobe-chat to inspect the logs of the lobe-chat container for any error messages or warnings that might indicate why the container is stopping.

5. Health Checks:

   • Ensure that the health checks for dependent services like postgresql and minio are correctly configured and passing. If these services are not healthy, it could cause the lobe-chat container to stop.

By following these steps, you should be able to gather more information about why the container is stopping and potentially resolve the issue.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}