Suggestion: Add Remove unused Docker images and volumes (optional) to the upgrade guide.

[hiro-gj]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

I had been upgrading my server from 1.0.0a, and when I upgraded it from 1.6.0 to 1.7.1 following the 1.7.1 Upgrade Guide (the usual procedure), it failed to start.

✘ Container docker-db-1 Error
dependency failed to start: container docker-db-1 is unhealthy

Checking the log with docker logs docker-db-1, I found that it said No space left on device.

PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-08-11 03:21:06.102 UTC [1] FATAL: could not write lock file "postmaster.pid": No space left on device

I asked the generation AI how to resolve the issue, and by deleting unused Docker images and volumes, I was able to successfully start the server.

docker image prune -a
docker volume prune

2. Additional context or comments

Would you like to make the following changes to the upgrade guide steps in the release notes?

• (1) Add Remove unused Docker images and volumes (optional).
• (2) Change the command git checkout main to git switch main.

(example)

---

Upgrade Guide

Docker Compose Deployments

1. Back up your customized docker-compose YAML file (optional)

   cd docker
   cp docker-compose.yaml docker-compose.yaml.$(date +%s).bak
   

2. Get the latest code from the main branch

   git switch main
   git pull origin main
   

3. Stop the service. Please execute in the docker directory

   docker compose down
   

4. Back up data

   tar -cvf volumes-$(date +%s).tgz volumes
   

5. Remove unused Docker images and volumes (optional)

   docker image prune -a
   docker volume prune
   

6. Upgrade services

   docker compose up -d
   

---

3. Can you help us with this feature?

• I am interested in contributing to this feature.

[kurokobo]

If we are also using Docker for purposes other than Dify, those commands could cause serious data loss in environments unrelated to Dify.

I don't think we should easily include commands that could affect non-Dify environments in our instructions and let people run them without caution. What do you think?

Since this is general Docker knowledge, not something specific to Dify, maybe we shouldn't include it in the main steps at all—or, if we mention it, perhaps it would be better to add it as a note or troubleshooting topic outside the step-by-step guide.

[hiro-gj]

or, if we mention it, perhaps it would be better to add it as a note or troubleshooting topic outside the step-by-step guide.

Thank you, @kurokobo
I see. That's a great idea!
Indeed, past data was still stored even when Back up data was executed,
so adding docker ~ prune did not fundamentally solve the problem.