coze-dev / coze-dev/coze-studio

各位大佬,请教coze-server启动失败应该如何处理,谢谢!

Open
#2,522 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
21.6k
Forks
3.1k
PR merge metrics
No merged PRs in 30d

Description

docker目录下docker-compose --profile "*" up -d启动coze-studio
发现coze-server启动失败,日志如下:
coze-server | 2025/12/04 08:22:19.755080 main.go:111: [Info] load env file: .env
coze-server | 2025/12/04 08:22:19.756281 main.go:132: [Info] log level: debug
coze-server | panic: InitializeInfra failed, err=init tos client failed, err=init minio client failed check bucket opencoze exist failed The Access Key Id you provided does not exist in our records.
coze-server |
coze-server | goroutine 1 [running]:
coze-server | main.main()
coze-server | /app/main.go:55 +0x86

Contributor guide

Open the contributing guide

Research direction

Start in the docker directory with the docker-compose profile configuration and the .env values loaded by coze-server. Trace the initialization reported at main.go:111 and main.go:132, with the panic reaching /app/main.go:55. Done means the compose startup completes without the coze-server panic.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker-compose, go
Domain
backend, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.