coze-server不断重启，日志报错minio问题

`coze-server` 容器一直重启，无法正常进入。
日志显示报错信息如下：
2025/12/03 07:29:59.432523 main.go:132: [Info] log level: debug
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.

以下是相关配置和进行过的尝试，
1. .env文件配置：
MINIO_ROOT_USER=minioadmin
MINIO_ROOT_PASSWORD=minioadmin123
MINIO_AK=$MINIO_ROOT_USER
MINIO_SK=$MINIO_ROOT_PASSWORD

2. 进入MinIO 容器env查看：
MINIO_AK=$MINIO_ROOT_USER
MINIO_SK=$MINIO_ROOT_PASSWORD
MINIO_ROOT_USER=minioadmin
MINIO_ROOT_PASSWORD=minioadmin123
MINIO_DEFAULT_BUCKETS=opencoze,milvus

Minio容器网络：
curl -I http://coze-minio:9000/minio/health/live
HTTP/1.1 200 OK
curl -I http://coze-minio:9000/minio/health/ready
HTTP/1.1 200 OK

MinIO 初始化日志：
已成功初始化各个默认文件和插件
输出：`MinIO initialization complete.`

3. 强制进入Server容器查看：
以 debug 模式启动：/app/opencoze
报错panic: InitializeInfra failed, err=init tos client failed, err=init minio client failed Endpoint url cannot have fully qualified paths.
环境变量：MINIO_ROOT_USER=minioadmin
MINIO_ROOT_PASSWORD=minioadmin123
MINIO_ENDPOINT=http://coze-minio:9000
MINIO_AK=minioadmin
MINIO_SK=minioadmin123
MINIO_DEFAULT_BUCKETS=opencoze
STORAGE_TYPE=minio
LOG_LEVEL=debug

4. 在Server 内对 MinIO 测试：

curl -I http://coze-minio:9000/minio/health/live
curl -I http://coze-minio:9000/minio/health/ready
都返回200ok
Server 容器可以 ping 通 MinIO

尝试获取 bucket 列表：
curl -X GET -u minioadmin:minioadmin123 http://coze-minio:9000/opencoze
InvalidRequest: The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256

Start at main.go:132 and the /app/opencoze entry point, then trace the infrastructure initialization that checks the opencoze bucket. Compare the reported .env and container environment values, and rerun the health checks and debug startup. Done means coze-server stays running and the bucket check completes without either reported error.

Written by the indexing model from the issue text.