-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
Closed
Description
Description
I am testing the process of moving from local storage to AWS S3. I did this on a test machine:
for DATATYPE in attachments lfs avatars repo-avatars repo-archive packages actions_log actions_artifacts; do
echo DATATYPE=$DATATYPE;
gitea migrate-storage \
--type=$DATATYPE \
--minio-base-path=$DATATYPE \
--storage=minio \
--minio-endpoint=s3.us-east-1.amazonaws.com \
--minio-access-key-id=xxxx \
--minio-secret-access-key=yyyy \
--minio-bucket=my-gitea \
--minio-location=us-east-1 \
--minio-use-ssl=true
doneThis mostly worked. I am ignoring the "unsupported storage" errors for things that do not support minio... that's fair.
The problem is repo-avatars. Normal avatars migrated fine (and so did attachments and lfs), but repo-avatars gave me this error:
2024/01/08 09:03:35 ...les/storage/minio.go:86:NewMinioStorage() [I] Creating Minio storage at s3.us-east-1.amazonaws.com:my-gitea with base path repo-avatars
Command error: Put "https://my-gitea.s3.dualstack.us-east-1.amazonaws.com/repo-avatars": read /data/gitea/repo-avatars: is a directory
Yes, it's a directory, but that shouldn't be a problem. Right?
Config:
[picture]
ENABLE_FEDERATED_AVATAR = false
AVATAR_UPLOAD_PATH = /data/gitea/avatars
REPOSITORY_AVATAR_UPLOAD_PATH = /data/gitea/repo-avatarsThe error message refers to the current storage path on the local disk, so here's what those folders look like:
gitea:/$ ls -ld /data/gitea/avatars /data/gitea/repo-avatars
drwxr-xr-x 3 git git 4096 Nov 28 22:49 /data/gitea/avatars
drwxr-xr-x 3 git git 4096 Apr 28 2023 /data/gitea/repo-avatars
Gitea Version
1.21.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
using official docker image with tag 1.21
Database
SQLite