Skip to content

Conversation

shx815
Copy link

@shx815 shx815 commented Sep 10, 2025

What type of PR is this?

fix

Check the PR title.

  • This PR title match the format:[fix][coze-loop]: resolve port conflict with coze-studio
  • The description of this PR title is user-oriented and clear enough for others to understand.
  • Add documentation if the current PR requires user awareness at the usage level.
  • This PR is written in English. PRs not in English will not be reviewed.

(Optional) Translate the PR title into Chinese.

[修复][coze-loop] 将端口8888改为8880以解决冲突

(Optional) More detailed description for this PR(en: English/zh: Chinese).

en:

  • Changed files:
    release/deployment/docker-compose/.env: Modified COZE_LOOP_APP_OPENAPI_PORT from 8888 to 8880

  • Reason for change:
    Resolves port conflict between Coze Loop and Coze Studio, which both default to 8888.

  • Testing performed:

    • Verified local deployment with docker compose up -d
    • Confirmed no port binding errors in container logs
    • Validated Coze Loop access via http://localhost:8880

zh(optional):

  • 修改文件:
    .env 文件:将 COZE_LOOP_APP_OPENAPI_PORT8888 修改为 8880

  • 变更原因:
    解决 Coze Loop 与 Coze Studio 默认端口 8888 的冲突问题

  • 测试情况:

    • 本地部署 docker compose up -d 无端口绑定错误
    • 容器日志无异常输出
    • 通过 http://localhost:8880 可正常访问 Coze Loop

(Optional) Which issue(s) this PR fixes:

@CLAassistant
Copy link

CLAassistant commented Sep 10, 2025

CLA assistant check
All committers have signed the CLA.

@shx815 shx815 requested a review from lsy357 September 18, 2025 09:29
COZE_LOOP_APP_IMAGE_NAME=coze-loop
COZE_LOOP_APP_IMAGE_TAG=1.1.0
COZE_LOOP_APP_OPENAPI_PORT=8888
COZE_LOOP_APP_OPENAPI_PORT=8880
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, I think the PORT here can't be changed. Because after modifying it and redeploying, the SDK client code also needs to be updated to listen on the new port. This incompatible change requires careful handling.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In your case, changing the port may need to be addressed by automatically mounting customized configurations.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry I took it to easy.
But i think it will make sense if we resolve port conflict with coze-studio, since there is need to use both of them.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We will carefully consider and resolve the issue you encountered during using. We will continue to communicate with you once we have a solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants