Closed
Description
Description
Storage in s3 buckets (using minio) no longer works when using Gitea 1.20.0 with chart v9.0.0. Changing the Gitea version to 1.19.4 with chart v9.0.0 (same configuration) makes storage in s3 buckets work again as described in the issue here:
https://gitea.com/gitea/helm-chart/issues/469
The storage configuration is:
storage:
MINIO_ACCESS_KEY_ID: ***
MINIO_BUCKET: my-existing-bucket
MINIO_ENDPOINT: storage.googleapis.com
MINIO_INSECURE_SKIP_VERIFY: false
MINIO_SECRET_ACCESS_KEY: ***
MINIO_USE_SSL: true
SERVE_DIRECT: false
STORAGE_TYPE: minio
With the above storage config, Gitea 1.20.0 says:
2023/07/18 16:33:54 ...s/setting/session.go:74:loadSessionFrom() [I] Session Service Enabled
2023/07/18 16:33:54 ...s/storage/storage.go:176:initAttachments() [I] Initialising Attachment storage with type: minio
2023/07/18 16:33:54 ...les/storage/minio.go:81:NewMinioStorage() [I] Creating Minio storage at storage.googleapis.com:my-existing-bucket with base path attachments/
2023/07/18 16:33:55 routers/init.go:60:mustInit() [F] code.gitea.io/gitea/modules/storage.Init failed: The requested bucket name is not available. The bucket namespace is shared by all users of the system. Please select a different name and try again
Is Gitea/minio trying to create the existing bucket?
Gitea Version
1.20.0
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
In Kubernetes with chart v9.0.0.
Database
PostgreSQL