langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

When I upgraded version 0.6.16 to version 0.7.2, I found that the upgrade was invalid. What should I do? Do I need to modify the env file #5307

New Issue
Closed
opened 2026-02-21 18:10:20 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:10:20 -05:00
Owner
Copy Link
Copy Source

Originally created by @tingaicompass on GitHub (Aug 29, 2024).

Self Checks

  • 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 (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.6.16

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When I upgraded version 0.6.16 to version 0.7.2, I found that the upgrade was invalid. What should I do? Do I need to modify the env file

cd dify/docker
docker compose down
git pull origin main
docker compose pull
docker compose up -d

✔️ Expected Behavior

Upgrade to version 0.7.2, and save the previous version information. Such as: data, account information, etc

❌ Actual Behavior

cd dify/docker
docker compose down
git pull origin main
docker compose pull
docker compose up -d

After following the above information, the docker-compose.yaml file does not get the latest version

  • branch main -> FETCH_HEAD
    Already up to date.

Hope to give a detailed update dify tutorial, rich in details

Originally created by @tingaicompass on GitHub (Aug 29, 2024). ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.6.16 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When I upgraded version 0.6.16 to version 0.7.2, I found that the upgrade was invalid. What should I do? Do I need to modify the env file ``` cd dify/docker docker compose down git pull origin main docker compose pull docker compose up -d ``` ### ✔️ Expected Behavior Upgrade to version 0.7.2, and save the previous version information. Such as: data, account information, etc ### ❌ Actual Behavior ``` cd dify/docker docker compose down git pull origin main docker compose pull docker compose up -d ``` After following the above information, the docker-compose.yaml file does not get the latest version * branch main -> FETCH_HEAD Already up to date. Hope to give a detailed update dify tutorial, rich in details
yindo added the 🐞 bug label 2026-02-21 18:10:20 -05:00
yindo closed this issue 2026-02-21 18:10:20 -05:00
yindo commented 2026-02-21 18:10:20 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 29, 2024):

@dingidng Hello there! I'm here to help you with any issues you may have. I can assist with bug solving, answer questions, and even guide you on becoming a contributor. Let's see if I can assist you with the issue you've encountered.

To resolve the issue with the upgrade from version 0.6.16 to version 0.7.2, you need to ensure that your docker-compose.yaml file is correctly configured for the new version. Here are the steps you should follow:

  1. Clone the Dify Source Code:

    git clone https://github.com/langgenius/dify.git

  2. Navigate to the Docker Directory:

    cd dify/docker

  3. Copy the Example Environment File:

    cp .env.example .env

  4. Update the Environment Variables:
    Ensure that the environment variables in your .env file are correctly set to match the new version's requirements. You can refer to the .env.example file for the full set of annotated environment variables. If .env.example has been updated, make sure to sync these changes to your local .env file. The .env file is now mandatory for running docker compose up and is crucial for configuring your deployment and ensuring custom settings persist through upgrades.

  5. Upgrade Dify:

    cd dify/docker
git pull origin main
docker compose down
docker compose pull
docker compose up -d

  6. Check if All Containers are Running Successfully:

    docker compose ps

  7. Access Dify:
    Finally, access http://localhost to use the deployed Dify.

If your system has Docker Compose V2 installed instead of V1, use docker compose instead of docker-compose. Check if this is the case by running $ docker compose version.

By following these steps, you should be able to resolve the upgrade issue and ensure that your environment variables are correctly configured. Additionally, note that the new docker-compose.yaml includes a certbot container for managing SSL certificates, and all vector database services are now managed from a single Docker Compose file. Make sure to review and update your .env file accordingly [1][2][3][4][5].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Aug 29, 2024): <!-- Greeting --> @dingidng Hello there! I'm here to help you with any issues you may have. I can assist with bug solving, answer questions, and even guide you on becoming a contributor. Let's see if I can assist you with the issue you've encountered. <!-- Answer --> To resolve the issue with the upgrade from version 0.6.16 to version 0.7.2, you need to ensure that your `docker-compose.yaml` file is correctly configured for the new version. Here are the steps you should follow: 1. **Clone the Dify Source Code**: ```bash git clone https://github.com/langgenius/dify.git ``` 2. **Navigate to the Docker Directory**: ```bash cd dify/docker ``` 3. **Copy the Example Environment File**: ```bash cp .env.example .env ``` 4. **Update the Environment Variables**: Ensure that the environment variables in your `.env` file are correctly set to match the new version's requirements. You can refer to the `.env.example` file for the full set of annotated environment variables. If `.env.example` has been updated, make sure to sync these changes to your local `.env` file. The `.env` file is now mandatory for running `docker compose up` and is crucial for configuring your deployment and ensuring custom settings persist through upgrades. 5. **Upgrade Dify**: ```bash cd dify/docker git pull origin main docker compose down docker compose pull docker compose up -d ``` 6. **Check if All Containers are Running Successfully**: ```bash docker compose ps ``` 7. **Access Dify**: Finally, access [http://localhost](http://localhost) to use the deployed Dify. If your system has Docker Compose V2 installed instead of V1, use `docker compose` instead of `docker-compose`. Check if this is the case by running `$ docker compose version`. By following these steps, you should be able to resolve the upgrade issue and ensure that your environment variables are correctly configured. Additionally, note that the new `docker-compose.yaml` includes a `certbot` container for managing SSL certificates, and all vector database services are now managed from a single Docker Compose file. Make sure to review and update your `.env` file accordingly <sup>[[1]](https://github.com/langgenius/dify/blob/main/docker-legacy/docker-compose.yaml)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/docker-compose.md)</sup><sup>[[3]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/getting-started/install-self-hosted/docker-compose.md)</sup><sup>[[4]](https://github.com/langgenius/dify-docs/blob/main/jp/getting-started/install-self-hosted/docker-compose.md)</sup><sup>[[5]](https://github.com/langgenius/dify/blob/main/docker/README.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:10:21 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 30, 2024):

You should read the release logs. Try to upgrade versions one by one instead of upgrading to the latest https://github.com/langgenius/dify/releases

Hence there is no useful information indicates what kind of errors you are encountering.

@crazywoola commented on GitHub (Aug 30, 2024): You should read the release logs. Try to upgrade versions one by one instead of upgrading to the latest https://github.com/langgenius/dify/releases Hence there is no useful information indicates what kind of errors you are encountering.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#5307
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?