You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I try to create a bucket using mc with object lock enabled but it fails.
Expected Behavior
Executing
mc mb --with-lock dev/bucket-with-lock
should create the bucket bucket-with-lock.
Current Behavior
Creation of the bucket fails:
mc mb --with-lock dev/bucket-with-lock
mc: <ERROR> Unable to make bucket `dev/bucket-with-lock`. A header you provided implies functionality that is not implemented
MinIO running as Docker container on Ubuntu 20.04 LTS
uname -a
Linux ubuntu-dev 5.4.0-39-generic #43-Ubuntu SMP Fri Jun 19 10:28:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
docker --version
Docker version 19.03.8, build afacb8b7f0
mc --version
mc version RELEASE.2020-06-26T19-56-55Z
mc admin info dev
● localhost:9000
Uptime: 2 hours
Version: 2020-07-02T00:15:09Z
Network: 1/1 OK
The text was updated successfully, but these errors were encountered:
@kannappanr I'm new to MinIO, is there a documentation which lists limitations depending on modes, etc?
At first sight it's not clear to me why locks depend on erasure-coded mode.
@kannappanr I'm new to MinIO, is there a documentation which lists limitations depending on modes, etc?
At first sight it's not clear to me why locks depend on erasure-coded mode.
FS mode think of it as minimal implementation, erasure coded is full fledged
I try to create a bucket using mc with object lock enabled but it fails.
Expected Behavior
Executing
should create the bucket
bucket-with-lock
.Current Behavior
Creation of the bucket fails:
Context
Creating a bucket with object lock enabled is a prerquisite for locking objects as described here: https://github.com/minio/minio/tree/master/docs/retention
Your Environment
MinIO running as Docker container on Ubuntu 20.04 LTS
The text was updated successfully, but these errors were encountered: