Charts: [stable/minio] MinIO is failing to start using default values

[xaviersierra]

Describe the bug

I'm trying to install MinIO on kubernetes, by just running the command:

helm install minio stable/minio

But, the MinIO pod is failing with the message:

 You are running an older version of MinIO released 4 weeks ago 
 Update: https://docs.min.io/docs/deploy-minio-on-kubernetes 
ERROR Unable to initialize backend: Unable to write to the backend
      > Please ensure MinIO binary has write permissions for the backend
      HINT:
        Use 'sudo chown <your-username> /export && sudo chmod u+rxw /export' to provide sufficient permissions.

This is the output of the persistent volume claims:

NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM           STORAGECLASS   REASON   AGE
pvc-7c1e22a3-1ac8-4bc9-8878-3da118e69806   10Gi       RWO            Delete           Bound    default/minio   standard                17m

And the output of the persistent volumes:

NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM           STORAGECLASS   REASON   AGE
pvc-7c1e22a3-1ac8-4bc9-8878-3da118e69806   10Gi       RWO            Delete           Bound    default/minio   standard                17m

Version of Helm and Kubernetes:
helm: 3.1.1
k8s: 1.16.3

Which chart: 5.0.23

What happened:
The helm installation reports a successful installation, nonetheless MinIO doesn't start

What you expected to happen:
After a short period of time, MinIO should start with no errors.

How to reproduce it (as minimally and precisely as possible):
Create a new k8s cluster.
run the command:

helm install minio stable/minio

[mattboardman]

Having a similar issue.

PV:

kind: PersistentVolume
apiVersion: v1
metadata:
  name: vol1
  labels:
    type: local
spec:
  storageClassName: local-storage
  capacity:
    storage: 10Gi
  accessModes:
    - ReadWriteOnce
  hostPath:
    path: "/mnt/data"
  nodeAffinity:
    required:
      nodeSelectorTerms:
      - matchExpressions:
        - key: kubernetes.io/hostname
          operator: In
          values:
          - kub-1

I was using this for testing purposes so I was able to get around for now by disabling persistence but I'm not sure if this error will occur in production on a cloud provider. Do you mind if I ask how/where you are deploying your cluster?

[alexshavelev44]

same situation with default values

helm - 3.2.0

NAME    STATUS   VOLUME       CAPACITY   ACCESS MODES   STORAGECLASS   AGE
minio   Bound    minio-test   10Gi       RWO,RWX                       93m

NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE minio-test 10Gi RWO,RWX Retain Bound minio/minio 96m

[chukynax]

same here

[kPsarakis]

same here, default values with helm install minio stable/minio

[jbarrick-mesosphere]

FWIW, I was able to workaround this by rolling back from chart version 5.0.30 to 5.0.17.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[kubbo]

I have the same problem

[harshavardhana]

Feel free to send PRs to https://github.com/minio/charts we have moved.

[Guoyoyo]

I have the same problems as you.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[stale[bot]]

This issue is being automatically closed due to inactivity.