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 set up an S3 storage via docker/docker-compose. Everything works so far, data ist stored in the correct bucket/directory. Now I tried to set a policy on this storage (either a lock on the bucket or a retention policy on the files). I use the mc client binary for that, configuring and accessing the storage backend also works. But trying to set the policy ends up with errors like
mc: <ERROR> Cannot enable object lock configuration on the specified bucket. Object Lock configuration cannot be enabled on existing buckets.
I also deleted an existing bucket and tried to set the policy/lock on an empty one, but with the same result. In the case of the compliance policy on single files
Cannot set object retention on /backup/myfolder/2020-03-28T04:27:45Z_backup.zip .Bucket is missing ObjectLockConfiguration
Should the mc binary work with the docker setup? According to issue #5184, I think it should. But what I am doing wrong here?
Expected Behavior
It should be possible to use the minio client to set locks/policies on (existing?) buckets or files.
Current Behavior
Setting these policies is not possible (see error messages above)
Possible Solution
Steps to Reproduce (for bugs)
Set up minio (single server) with docker-compose
Create bucket via UI or minio client
Set retention policy/lock on bucket
Context
Using s3/minio for etcd snapshots. RKE in this case should handle the retention and delete files after a configured period. Due to a bug in RKE (rancher/rancher#24544) I tried to solve this via Minio retention in the meanwhile.
Regression
unknown
Your Environment
Version used (minio version): RELEASE.2020-03-09T18-26-53Z
Environment name and version (e.g. nginx 1.9.1):
Server type and version: Single server install
Operating System and version (uname -a): Linux ........ 3.10.0-1062.el7.x86_64 Full restructure in accordance with #1 SMP Thu Jul 18 20:25:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Link to your project:
The text was updated successfully, but these errors were encountered:
I set up an S3 storage via docker/docker-compose. Everything works so far, data ist stored in the correct bucket/directory. Now I tried to set a policy on this storage (either a lock on the bucket or a retention policy on the files). I use the mc client binary for that, configuring and accessing the storage backend also works. But trying to set the policy ends up with errors like
mc: <ERROR> Cannot enable object lock configuration on the specified bucket. Object Lock configuration cannot be enabled on existing buckets.
I also deleted an existing bucket and tried to set the policy/lock on an empty one, but with the same result. In the case of the compliance policy on single files
Cannot set object retention on /backup/myfolder/2020-03-28T04:27:45Z_backup.zip .Bucket is missing ObjectLockConfiguration
Should the mc binary work with the docker setup? According to issue #5184, I think it should. But what I am doing wrong here?
Expected Behavior
It should be possible to use the minio client to set locks/policies on (existing?) buckets or files.
Current Behavior
Setting these policies is not possible (see error messages above)
Possible Solution
Steps to Reproduce (for bugs)
Context
Using s3/minio for etcd snapshots. RKE in this case should handle the retention and delete files after a configured period. Due to a bug in RKE (rancher/rancher#24544) I tried to solve this via Minio retention in the meanwhile.
Regression
unknown
Your Environment
minio version
): RELEASE.2020-03-09T18-26-53Zuname -a
): Linux ........ 3.10.0-1062.el7.x86_64 Full restructure in accordance with #1 SMP Thu Jul 18 20:25:13 UTC 2019 x86_64 x86_64 x86_64 GNU/LinuxThe text was updated successfully, but these errors were encountered: