[Bug] 运行 docker compose up 报错

[Alexkerl]

📦 Environment

Docker

📌 Version

newest

💻 Operating System

Ubuntu

🌐 Browser

Chrome

🐛 Bug Description

运行 docker compose up 报错lobe-casdoor | 2024/12/27 06:09:32 Starting Radius server on 0.0.0.0:1812
lobe-casdoor | 2024/12/27 06:09:32 Listening on 0.0.0.0:389
lobe-casdoor | 2024/12/27 06:09:32.288 [I] http server Running on http://:8000
lobe-chat | [Database] Start to migration...
lobe-chat | ✅ database migration pass.
lobe-chat | -------------------------------------
lobe-chat | ▲ Next.js 15.1.2
lobe-chat | - Local: http://localhost:3210
lobe-chat | - Network: http://0.0.0.0:3210
lobe-chat |
lobe-chat | ✓ Starting...
lobe-chat | ✓ Ready in 113ms
lobe-minio |
lobe-minio | API: SYSTEM()
lobe-minio | Time: 06:09:34 UTC 12/27/2024
lobe-minio | Error: Drive /etc/minio/data, path (.minio.sys/pool.bin) returned an error (decodeXLHeaders: Unknown xl header version 2) (*fmt.wrapError)
lobe-minio | 15: internal/logger/logonce.go:118:logger.(*logOnceType).logOnceIf()
lobe-minio | 14: internal/logger/logonce.go:149:logger.LogOnceIf()
lobe-minio | 13: cmd/erasure-object.go:605:cmd.readAllXL()
lobe-minio | 12: cmd/erasure-object.go:678:cmd.erasureObjects.getObjectFileInfo()
lobe-minio | 11: cmd/erasure-object.go:225:cmd.erasureObjects.GetObjectNInfo()
lobe-minio | 10: cmd/erasure-sets.go:752:cmd.(*erasureSets).GetObjectNInfo()
lobe-minio | 9: cmd/config-common.go:33:cmd.readConfigWithMetadata()
lobe-minio | 8: cmd/config-common.go:54:cmd.readConfig()
lobe-minio | 7: cmd/erasure-server-pool-decom.go:381:cmd.(*poolMeta).load()
lobe-minio | 6: cmd/erasure-server-pool-decom.go:501:cmd.(*erasureServerPools).Init()
lobe-minio | 5: cmd/erasure-server-pool.go:157:cmd.newErasureServerPools()
lobe-minio | 4: cmd/server-main.go:976:cmd.newObjectLayer()
lobe-minio | 3: cmd/server-main.go:718:cmd.serverMain.func9()
lobe-minio | 2: cmd/server-main.go:434:cmd.bootstrapTrace()
lobe-minio | 1: cmd/server-main.go:716:cmd.serverMain()
lobe-minio | ERROR Unable to initialize backend: decodeXLHeaders: Unknown xl header version 2
lobe-minio exited with code 1
lobe-chat | (node:28) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
lobe-chat | (Use node --trace-deprecation ... to show where the warning was created)
lobe-minio |
lobe-minio | API: SYSTEM()
lobe-minio | Time: 06:09:40 UTC 12/27/2024
lobe-minio | Error: Drive /etc/minio/data, path (.minio.sys/pool.bin) returned an error (decodeXLHeaders: Unknown xl header version 2) (*fmt.wrapError)
lobe-minio | 15: internal/logger/logonce.go:118:logger.(*logOnceType).logOnceIf()
lobe-minio | 14: internal/logger/logonce.go:149:logger.LogOnceIf()
lobe-minio | 13: cmd/erasure-object.go:605:cmd.readAllXL()
lobe-minio | 12: cmd/erasure-object.go:678:cmd.erasureObjects.getObjectFileInfo()
lobe-minio | 11: cmd/erasure-object.go:225:cmd.erasureObjects.GetObjectNInfo()
lobe-minio | 10: cmd/erasure-sets.go:752:cmd.(*erasureSets).GetObjectNInfo()
lobe-minio | 9: cmd/config-common.go:33:cmd.readConfigWithMetadata()
lobe-minio | 8: cmd/config-common.go:54:cmd.readConfig()
lobe-minio | 7: cmd/erasure-server-pool-decom.go:381:cmd.(*poolMeta).load()
lobe-minio | 6: cmd/erasure-server-pool-decom.go:501:cmd.(*erasureServerPools).Init()
lobe-minio | 5: cmd/erasure-server-pool.go:157:cmd.newErasureServerPools()
lobe-minio | 4: cmd/server-main.go:976:cmd.newObjectLayer()
lobe-minio | 3: cmd/server-main.go:718:cmd.serverMain.func9()
lobe-minio | 2: cmd/server-main.go:434:cmd.bootstrapTrace()
lobe-minio | 1: cmd/server-main.go:716:cmd.serverMain()
lobe-minio | ERROR Unable to initialize backend: decodeXLHeaders: Unknown xl header version 2

📷 Recurrence Steps

No response

🚦 Expected Behavior

No response

📝 Additional Information

No response

[lobehubbot]

👀 @Alexkerl

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[dosubot]

The error you're encountering with MinIO, "decodeXLHeaders: Unknown xl header version 2," suggests that there might be an issue with the data directory or the version of MinIO being used. Here are a few steps you can take to troubleshoot and potentially resolve this issue:

1. Check MinIO Version: Ensure that you are using a compatible version of MinIO. Since the version is not specified in the docker-compose.yml, it defaults to the latest version. You might want to specify a stable version that is known to work with your setup.

2. Data Directory: The error might be related to the existing data in the MinIO data directory. You can try the following:

   • Backup the current data directory (./s3_data).
   • Clear the contents of the ./s3_data directory to reset it.
   • Restart the MinIO container to see if it initializes correctly with a fresh data directory.

3. Configuration Files: Ensure that your configuration files are not corrupted. Sometimes, configuration issues can lead to such errors.

4. Logs and Documentation: Check the MinIO logs for any additional error messages that might provide more context. Also, review the MinIO documentation for any notes on compatibility or known issues with specific versions.

5. Reinitialize MinIO: If the above steps do not resolve the issue, consider reinitializing MinIO by removing the existing data and starting fresh. This can help if the issue is due to corrupted metadata or configuration.

These steps should help you diagnose and potentially fix the issue with MinIO in your Docker setup. If the problem persists, you might need to look into more detailed logs or consider reaching out to the MinIO community for further assistance.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}