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

Help, what are the steps for the correct version upgrade instructions? #1057

New Issue
Closed
opened 2026-02-21 17:29:45 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 17:29:45 -05:00
Owner
Copy Link
Copy Source

Originally created by @nickboyabc on GitHub (Feb 17, 2024).

Self Checks

Dify version

0.5.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I have followed the official instructions to execute the following command:
git checkout main
git pull origin main
cd docker
docker-compose up -d

But the version upgrade (0.5.0 to 0.5.5) is still not realized

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @nickboyabc on GitHub (Feb 17, 2024). ### Self Checks - [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 file this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). ### Dify version 0.5.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I have followed the official instructions to execute the following command: git checkout main git pull origin main cd docker docker-compose up -d But the version upgrade (0.5.0 to 0.5.5) is still not realized ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug📚 documentation labels 2026-02-21 17:29:45 -05:00
yindo closed this issue 2026-02-21 17:29:45 -05:00
yindo commented 2026-02-21 17:29:45 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 17, 2024):

🤖

Hey there, @nickboyabc! Great to see you back. Hope you're doing awesome! 😊

Based on the information you've provided and similar issues I found in the repository, it seems like you might be missing a step in the upgrade process. Specifically, you need to update the image version in your docker-compose.yaml file before running the docker-compose up -d command.

Here are the steps you should follow:

  1. Open your docker-compose.yaml file.

  2. Find the services that use the dify image. In your case, these are the api, worker, and web services.

  3. Update the image version for each of these services. You should change langgenius/dify-api:0.5.0 and langgenius/dify-web:0.5.0 to langgenius/dify-api:0.5.5 and langgenius/dify-web:0.5.5 respectively.

Here's how the updated sections should look:

# API service
api:
  image: langgenius/dify-api:0.5.5
  ...

# worker service
worker:
  image: langgenius/dify-api:0.5.5
  ...

# Frontend web application.
web:
  image: langgenius/dify-web:0.5.5
  ...

  1. Save the docker-compose.yaml file.

  2. Run docker-compose down to stop and remove the current containers.

  3. Run docker-compose pull to pull the new images from the Docker registry.

  4. Run docker-compose up -d to start the new containers.

Please note that you should backup your data before performing these steps, as they may cause data loss if not done correctly. Also, these steps assume that the new version is backward compatible with the old one. If it's not, you may need to perform additional steps such as database migrations.

As for the specific changes between version 0.5.0 and 0.5.5 of dify, I wasn't able to find that information in the repository. You might want to check the release notes or changelog for that information.

I hope this helps! If you have any other questions, feel free to ask.

Sources:

Sources

About Dosu

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

@dosubot[bot] commented on GitHub (Feb 17, 2024): _🤖_ <!-- Greeting --> Hey there, @nickboyabc! Great to see you back. Hope you're doing awesome! 😊 <!-- Answer --> Based on the information you've provided and similar issues I found in the repository, it seems like you might be missing a step in the upgrade process. Specifically, you need to update the image version in your docker-compose.yaml file before running the `docker-compose up -d` command. Here are the steps you should follow: 1. Open your docker-compose.yaml file. 2. Find the services that use the dify image. In your case, these are the `api`, `worker`, and `web` services. 3. Update the image version for each of these services. You should change `langgenius/dify-api:0.5.0` and `langgenius/dify-web:0.5.0` to `langgenius/dify-api:0.5.5` and `langgenius/dify-web:0.5.5` respectively. Here's how the updated sections should look: ```yaml # API service api: image: langgenius/dify-api:0.5.5 ... # worker service worker: image: langgenius/dify-api:0.5.5 ... # Frontend web application. web: image: langgenius/dify-web:0.5.5 ... ``` 4. Save the docker-compose.yaml file. 5. Run `docker-compose down` to stop and remove the current containers. 6. Run `docker-compose pull` to pull the new images from the Docker registry. 7. Run `docker-compose up -d` to start the new containers. Please note that you should backup your data before performing these steps, as they may cause data loss if not done correctly. Also, these steps assume that the new version is backward compatible with the old one. If it's not, you may need to perform additional steps such as database migrations. As for the specific changes between version 0.5.0 and 0.5.5 of dify, I wasn't able to find that information in the repository. You might want to check the release notes or changelog for that information. I hope this helps! If you have any other questions, feel free to ask. Sources: - [docker/docker-compose.yaml](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml) - [Version Upgrade Command Help](https://github.com/langgenius/dify/issues/1939) - [bug](https://github.com/langgenius/dify/issues/803) - [已经 docker 部署了，请问如何升级？](https://github.com/langgenius/dify/issues/377) ## Sources - [Version Upgrade Command Help](https://github.com/langgenius/dify/issues/1939) - [bug](https://github.com/langgenius/dify/issues/803) - [已经 docker 部署了，请问如何升级？](https://github.com/langgenius/dify/issues/377) - [docker/docker-compose.yaml](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml) <!-- Dosu Comment Footer --> <details open> <summary> #### About Dosu </summary> This response is meant to be useful and save you time. It is **not meant to be a precise solution**, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot. </details>
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 📚 documentation
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#1057
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?