Issue Station
Sign In
Tools hereToolbox

dify - 💡(How to fix) Fix Container docker-db_postgres-1 Skipped: optional dependency "db_postgres" failed to start [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
langgenius/dify#35252•Fetched 2026-04-16 07:06:53
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
1
Author
WanderfoWanderfo
Participants
WanderfoWanderfo
Timeline (top)
closed ×1labeled ×1

Error Message

I mistakenly moved the dify directory and received an error when moving it back

RAW_BUFFERClick to expand / collapse

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.13.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

docker-compose up -d
[+] up 9/11
[+] up 11/12 docker-ssrf_proxy-1 Running 0.0s ✔ Container docker-ssrf_proxy-1 Running 0.0s ✔ Container docker-redis-1 Running 0.0s [+] up 12/12 docker-weaviate-1 Running 0.0s ✔ Container docker-ssrf_proxy-1 Running 0.0s ✔ Container docker-redis-1 Running 0.0s ✔ Container docker-weaviate-1 Running 0.0s ✔ Container docker-web-1 Running 0.0s ✔ Container docker-sandbox-1 Running 0.0s ✔ Container docker-worker_beat-1 Running 0.0s ✔ Container docker-worker-1 Running 0.0s ✔ Container docker-api-1 Running 0.0s ✔ Container docker-nginx-1 Running 0.0s ! Container docker-db_postgres-1 Skipped: optional dependency "db_postgres" failed to start 0.5s ✔ Container docker-init_permissions-1 Exited 0.7s ✔ Container docker-plugin_daemon-1 Started

docker logs -f docker-db_postgres-1

PostgreSQL Database directory appears to contain a database; Skipping initialization

2026-04-15 08:07:52.210 UTC [1] FATAL: could not write lock file "postmaster.pid": No space left on device

PostgreSQL Database directory appears to contain a database; Skipping initialization

2026-04-15 08:07:52.713 UTC [1] FATAL: could not write lock file "postmaster.pid": No space left on device

PostgreSQL Database directory appears to contain a database; Skipping initialization

✔️ Expected Behavior

I mistakenly moved the dify directory and received an error when moving it back

❌ Actual Behavior

! Container docker-db_postgres-1 Skipped: optional dependency "db_postgres" failed to start

extent analysis

TL;DR

The PostgreSQL container fails to start due to a "No space left on device" error, indicating a storage issue.

Guidance

  • Check the available disk space on the device where the PostgreSQL data directory is located to confirm the storage issue.
  • Verify that the docker-db_postgres-1 container has sufficient resources allocated, particularly storage, to run without issues.
  • Consider cleaning up unnecessary data or increasing the storage capacity to resolve the "No space left on device" error.
  • Review the PostgreSQL configuration to ensure it is set up to handle storage limitations appropriately.

Notes

The issue seems to be related to storage capacity rather than the Dify application itself. Resolving the storage issue should allow the PostgreSQL container to start correctly.

Recommendation

Apply workaround: Increase the storage capacity or clean up unnecessary data to resolve the "No space left on device" error, as this is a storage-related issue rather than a version-specific problem.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#docker error#permission error#memory optimization

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING