-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minio as s3 external storage folder (directory) creation is not working properly or at all #17987
Comments
After some more experiments found out that on fresh minio installs this only happens only one time, and after page refresh folders are creating properly, but first time of folder creation it is still same error |
#14913 (comment) |
Are you using Minio to connect to B2? If so, the problem may be that B2 fails to create files with a trailing slash (aka folders; e.g. if you try to upload "directory/" via Minio to B2). B2 doesn't have "folders", so there can't be an empty folder. Folders are just filename prefixes for B2. If you create a folder in the B2 web interface, then it will create a file named ".bzEmpty" with a size of 0 bytes with the prefix of your folder name. |
No, just standalone minio installation. |
I'm having the same issue. Using minio for storage in file storage mode. If I create a folder via Nextcloud's web UI I get a "Could not create folder" error, however an empty folder is created within minio's file storage. Nextcloud does not see the folder however. All sorts of errors if I create a folder on my computer and attempt to let the sync client handle it. Manually creating a file in the folder in minio's file storage lets Nextcloud see the folder and then sync completes normally. This is most likely related to minio's handling of empty folders, which is not quite S3 compatible. A semi-recent change in minio allows empty folders, so long as minio is using regular file storage and the folder object is created with a trailing slash in it's path and a zero size, see: minio/minio#2423 I accept that Nextcloud is likely following the normal S3 behavior and that minio is not treating empty folders the same way other S3 implementations do. But hopefully something can be done to allow Nextcloud to deal with minio's quirks. |
Is this Issue still valid? If not, please close this issue. Thanks! :) |
This appears to be working now with the NC 21 and Minio 2021-03-04 |
Steps to reproduce
docker run -p 9000:9000 --name minio1 -e "MINIO_ACCESS_KEY=AKIAIOSFODNN7EXAMPLE" -e "MINIO_SECRET_KEY=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY" minio/minio server /data
Expected behaviour
No tooltip and folder created.
Actual behaviour
Somehow when i do this on same machine where nextcloud installed tooltip pops up, but folder is actually created.
IF i spin up minio on another machine in network tooltip exists and folder is not created.
Server configuration
Operating system:
alpine inside docker on windows 10
Web server:
official docker-compose mariadb-cron-redis
Nextcloud version: (see Nextcloud admin page)
17.0.1
Updated from an older Nextcloud/ownCloud or fresh install:
fresh
Where did you install Nextcloud from:
docker hub
Signing status:
Signing status
``` No errors have been found. ```List of activated apps:
App list
Are you using external storage, if yes which one:
Minio S3
Are you using encryption:
No
Client configuration
Browser:
Chrome 78.0.3904.97
Operating system:
windows 10
Logs
Web server error log
Web server error log
Nextcloud log (data/nextcloud.log)
Nextcloud on another pc log
Minio on same pc log
Browser log
Browser log
Curl recieve 201, but in fact folder is not created
Curl log
The text was updated successfully, but these errors were encountered: