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

Docker Compose deployment failed. #4346

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

Originally created by @henrion-y on GitHub (Jun 30, 2024).

Originally assigned to: @guchenhe on GitHub.

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).
  • 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.6.12

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

b01d3ed1dbe0335e7740665e81b07d9

After executing the following commands:

cd docker
cp .env.example .env
docker compose up -d

an error is reported: "ERROR: Invalid interpolation format for 'opensearch' option in service 'services': 'discovery.type=${OPENSEARCH_DISCOVERY_TYPE:-single-node}'"

✔️ Expected Behavior

Normal updates to the operational Docker project.

❌ Actual Behavior

an error is reported: "ERROR: Invalid interpolation format for 'opensearch' option in service 'services': 'discovery.type=${OPENSEARCH_DISCOVERY_TYPE:-single-node}'"

Originally created by @henrion-y on GitHub (Jun 30, 2024). Originally assigned to: @guchenhe on GitHub. ### 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] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.6.12 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="528" alt="b01d3ed1dbe0335e7740665e81b07d9" src="https://github.com/langgenius/dify/assets/30074062/be15155d-a05c-4233-8ceb-7666381755a9"> After executing the following commands: ``` cd docker cp .env.example .env docker compose up -d ``` an error is reported: "ERROR: Invalid interpolation format for 'opensearch' option in service 'services': 'discovery.type=${OPENSEARCH_DISCOVERY_TYPE:-single-node}'" ### ✔️ Expected Behavior Normal updates to the operational Docker project. ### ❌ Actual Behavior an error is reported: "ERROR: Invalid interpolation format for 'opensearch' option in service 'services': 'discovery.type=${OPENSEARCH_DISCOVERY_TYPE:-single-node}'"
yindo added the 🐞 bugstale labels 2026-02-21 18:05:57 -05:00
yindo closed this issue 2026-02-21 18:05:57 -05:00
yindo commented 2026-02-21 18:05:57 -05:00
Author
Owner
Copy Link
Copy Source

@guchenhe commented on GitHub (Jun 30, 2024):

hi - thanks so much for the feedback. To make sure that custom configurations can be separated from docker-compose.yaml moving forward, the new docker file makes use of environment interpolation feature of docker compose. I suspect this may be due to how compose wrongly interprets the dash in the value single-node.

A lot of environment interpolation related issues were ironed out in compose v2.11.2 (see: https://github.com/docker/compose/issues/9879). Could you try upgrading your compose to v2.11.2+ to see if this could be fixed?

@guchenhe commented on GitHub (Jun 30, 2024): hi - thanks so much for the feedback. To make sure that custom configurations can be separated from `docker-compose.yaml` moving forward, the new docker file makes use of environment interpolation feature of docker compose. I suspect this may be due to how compose wrongly interprets the dash in the value `single-node`. A lot of environment interpolation related issues were ironed out in compose v2.11.2 (see: https://github.com/docker/compose/issues/9879). Could you try upgrading your compose to v2.11.2+ to see if this could be fixed?
yindo commented 2026-02-21 18:05:57 -05:00
Author
Owner
Copy Link
Copy Source

@thenetguy commented on GitHub (Jun 30, 2024):

just tried to deploy via docker-compose up -d and got this error


$//' /docker-entrypoint.sh && chmod +x /docker-entrypoint.sh && /docker-entrypoint.sh"cp /docker-entrypoint-mount.sh /docker-entrypoint.sh && sed -i 's/`

and no i dont want to try docker compose v2 .

@thenetguy commented on GitHub (Jun 30, 2024): just tried to deploy via docker-compose up -d and got this error ``` $//' /docker-entrypoint.sh && chmod +x /docker-entrypoint.sh && /docker-entrypoint.sh"cp /docker-entrypoint-mount.sh /docker-entrypoint.sh && sed -i 's/` ``` and no i dont want to try docker compose v2 .
yindo commented 2026-02-21 18:05:57 -05:00
Author
Owner
Copy Link
Copy Source

@guchenhe commented on GitHub (Jun 30, 2024):

just tried to deploy via docker-compose up -d and got this error


$//' /docker-entrypoint.sh && chmod +x /docker-entrypoint.sh && /docker-entrypoint.sh"cp /docker-entrypoint-mount.sh /docker-entrypoint.sh && sed -i 's/`

and no i dont want to try docker compose v2 .

this seems like a different error - please open another issue with the full log of the error message

@guchenhe commented on GitHub (Jun 30, 2024): > just tried to deploy via docker-compose up -d and got this error > > ``` > > $//' /docker-entrypoint.sh && chmod +x /docker-entrypoint.sh && /docker-entrypoint.sh"cp /docker-entrypoint-mount.sh /docker-entrypoint.sh && sed -i 's/` > ``` > > and no i dont want to try docker compose v2 . this seems like a different error - please open another issue with the full log of the error message
yindo commented 2026-02-21 18:05:57 -05:00
Author
Owner
Copy Link
Copy Source

@thenetguy commented on GitHub (Jun 30, 2024):

that is all the output i get from docker-compose up -d there arent any other logs. steps to reproduce,

  1. clone the repo
  2. cd into the repo
  3. cd docker
  4. cp .env.example .env
  5. docker-compose up -d
@thenetguy commented on GitHub (Jun 30, 2024): that is all the output i get from docker-compose up -d there arent any other logs. steps to reproduce, 1. clone the repo 2. cd into the repo 3. cd docker 4. cp .env.example .env 5. docker-compose up -d
yindo commented 2026-02-21 18:05:57 -05:00
Author
Owner
Copy Link
Copy Source

@simplast commented on GitHub (Jun 30, 2024):

sudo docker compose pull

invalid interpolation format for services.ssrf_proxy.entrypoint.[]: "cp /docker-entrypoint-mount.sh /docker-entrypoint.sh && sed -i 's/\r$//' /docker-entrypoint.sh && chmod +x /docker-entrypoint.sh && /docker-entrypoint.sh". You may need to escape any with another

@simplast commented on GitHub (Jun 30, 2024): sudo docker compose pull --- invalid interpolation format for services.ssrf_proxy.entrypoint.[]: "cp /docker-entrypoint-mount.sh /docker-entrypoint.sh && sed -i 's/\r$//' /docker-entrypoint.sh && chmod +x /docker-entrypoint.sh && /docker-entrypoint.sh". You may need to escape any $ with another $
yindo commented 2026-02-21 18:05:57 -05:00
Author
Owner
Copy Link
Copy Source

@takatost commented on GitHub (Jul 1, 2024):

Hey @henrion-y @thenetguy @simplast, the issue's fixed now. You can pull the latest code from the main branch and try redeploying.

@takatost commented on GitHub (Jul 1, 2024): Hey @henrion-y @thenetguy @simplast, the issue's fixed now. You can pull the latest code from the main branch and try redeploying.
yindo commented 2026-02-21 18:05:57 -05:00
Author
Owner
Copy Link
Copy Source

@big-pan-whu commented on GitHub (Jul 4, 2024):

Hey @henrion-y @thenetguy @simplast, the issue's fixed now. You can pull the latest code from the main branch and try redeploying.

I pull the latest code and try redeploying, It takes timeout error:error pulling image configuration: download failed after attempts=6: dial tcp 173.252.105.21:443: i/o timeout

@big-pan-whu commented on GitHub (Jul 4, 2024): > Hey @henrion-y @thenetguy @simplast, the issue's fixed now. You can pull the latest code from the main branch and try redeploying. I pull the latest code and try redeploying, It takes timeout error:error pulling image configuration: download failed after attempts=6: dial tcp 173.252.105.21:443: i/o timeout
yindo commented 2026-02-21 18:05:58 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 10, 2024):

Hey @henrion-y @thenetguy @simplast, the issue's fixed now. You can pull the latest code from the main branch and try redeploying.

I pull the latest code and try redeploying, It takes timeout error:error pulling image configuration: download failed after attempts=6: dial tcp 173.252.105.21:443: i/o timeout

This is a general network issue.

@crazywoola commented on GitHub (Jul 10, 2024): > > Hey @henrion-y @thenetguy @simplast, the issue's fixed now. You can pull the latest code from the main branch and try redeploying. > > I pull the latest code and try redeploying, It takes timeout error:error pulling image configuration: download failed after attempts=6: dial tcp 173.252.105.21:443: i/o timeout This is a general network issue.
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 stale 🐞 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#4346
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?