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

After upgrading to 1.1.3, docker compose fails to start. How can I downgrade to 1.1.2? #12051

New Issue
Closed
opened 2026-02-21 19:05:30 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 19:05:30 -05:00
Owner
Copy Link
Copy Source

Originally created by @Pahkho on GitHub (Mar 24, 2025).

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

1.1.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

Image

Image

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @Pahkho on GitHub (Mar 24, 2025). ### 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 1.1.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/bf53c12d-1c29-4441-8948-1b1e4298f0ca) ![Image](https://github.com/user-attachments/assets/882345e8-7247-4548-a038-c90e470205a2) ![Image](https://github.com/user-attachments/assets/c2958b2f-2893-4027-8478-895494937b0c) ![Image](https://github.com/user-attachments/assets/61282914-5bd7-4a00-b252-b0d6dc1b76e4) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:05:30 -05:00
yindo closed this issue 2026-02-21 19:05:30 -05:00
yindo commented 2026-02-21 19:05:31 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 24, 2025):

To downgrade Dify from version 1.1.3 to 1.1.2 using Docker Compose, follow these steps:

  1. Stop the current Dify Docker instance:

    docker compose down

  2. Clone the specific version:
    Create a new directory separate from your current Dify installation and clone the repository for version 1.1.2:

    git clone https://github.com/langgenius/dify.git --branch 1.1.2

  3. Navigate to the Docker directory:

    cd dify/docker

  4. Start the downgraded version:

    docker compose up -d

This process will set up Dify at version 1.1.2. Make sure to back up any important data before performing the downgrade to avoid data loss. If you encounter any database migration issues, you may need to address them separately, as downgrading can sometimes lead to such conflicts [1].

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

@dosubot[bot] commented on GitHub (Mar 24, 2025): <!-- Answer --> To downgrade Dify from version 1.1.3 to 1.1.2 using Docker Compose, follow these steps: 1. **Stop the current Dify Docker instance:** ```bash docker compose down ``` 2. **Clone the specific version:** Create a new directory separate from your current Dify installation and clone the repository for version 1.1.2: ```bash git clone https://github.com/langgenius/dify.git --branch 1.1.2 ``` 3. **Navigate to the Docker directory:** ```bash cd dify/docker ``` 4. **Start the downgraded version:** ```bash docker compose up -d ``` This process will set up Dify at version 1.1.2. Make sure to back up any important data before performing the downgrade to avoid data loss. If you encounter any database migration issues, you may need to address them separately, as downgrading can sometimes lead to such conflicts <sup>[[1]](https://github.com/langgenius/dify/discussions/14671)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/ec458a1e-8eff-4a61-8c90-7fd1fd050231?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/ec458a1e-8eff-4a61-8c90-7fd1fd050231?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/ec458a1e-8eff-4a61-8c90-7fd1fd050231?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/ec458a1e-8eff-4a61-8c90-7fd1fd050231?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ec458a1e-8eff-4a61-8c90-7fd1fd050231?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/ec458a1e-8eff-4a61-8c90-7fd1fd050231?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ec458a1e-8eff-4a61-8c90-7fd1fd050231?feedback_type=other)</sup>
yindo commented 2026-02-21 19:05:31 -05:00
Author
Owner
Copy Link
Copy Source

@Pahkho commented on GitHub (Mar 24, 2025):

Self Checks

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

Dify version

1.1.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

Image

Image

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

What is this error?

@Pahkho commented on GitHub (Mar 24, 2025): > ### 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 > 1.1.3 > > ### Cloud or Self Hosted > Self Hosted (Docker) > > ### Steps to reproduce > ![Image](https://github.com/user-attachments/assets/bf53c12d-1c29-4441-8948-1b1e4298f0ca) > > ![Image](https://github.com/user-attachments/assets/882345e8-7247-4548-a038-c90e470205a2) > > ![Image](https://github.com/user-attachments/assets/c2958b2f-2893-4027-8478-895494937b0c) > > ![Image](https://github.com/user-attachments/assets/61282914-5bd7-4a00-b252-b0d6dc1b76e4) > > ### ✔️ Expected Behavior > _No response_ > > ### ❌ Actual Behavior > _No response_ What is this error?
yindo commented 2026-02-21 19:05:31 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 24, 2025):

The error you're encountering is related to DNS resolution issues when trying to connect to the PostgreSQL database. The message "could not translate host name 'db' to address: Name or service not known" indicates that the hostname 'db' cannot be resolved to an IP address. This is often due to misconfigurations in the Docker Compose setup, where the service name 'db' is not correctly linked or recognized.

To resolve this, ensure that your Docker Compose file correctly defines the database service with the appropriate service name and network settings. Additionally, verify that the environment variables for the database connection (such as DB_HOST) are correctly set to match the service name used in your Docker Compose configuration. If the issue persists, you might want to check the Docker network settings to ensure that the containers can communicate with each other properly.

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

@dosubot[bot] commented on GitHub (Mar 24, 2025): <!-- Answer --> The error you're encountering is related to DNS resolution issues when trying to connect to the PostgreSQL database. The message "could not translate host name 'db' to address: Name or service not known" indicates that the hostname 'db' cannot be resolved to an IP address. This is often due to misconfigurations in the Docker Compose setup, where the service name 'db' is not correctly linked or recognized. To resolve this, ensure that your Docker Compose file correctly defines the database service with the appropriate service name and network settings. Additionally, verify that the environment variables for the database connection (such as `DB_HOST`) are correctly set to match the service name used in your Docker Compose configuration. If the issue persists, you might want to check the Docker network settings to ensure that the containers can communicate with each other properly. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/b76b3e5a-9dbd-43f4-852a-acffbbbd0320?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/b76b3e5a-9dbd-43f4-852a-acffbbbd0320?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/b76b3e5a-9dbd-43f4-852a-acffbbbd0320?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/b76b3e5a-9dbd-43f4-852a-acffbbbd0320?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b76b3e5a-9dbd-43f4-852a-acffbbbd0320?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/b76b3e5a-9dbd-43f4-852a-acffbbbd0320?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b76b3e5a-9dbd-43f4-852a-acffbbbd0320?feedback_type=other)</sup>
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#12051
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?