-
Notifications
You must be signed in to change notification settings - Fork 68
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
Dataset operator CrashLoopBackOff #362
Comments
@vmtuan12 you have spotted a bug but it was triggered by a mistake in the dataset specification you provided. The spec did not contain
|
Can you tell me where is the |
@vmtuan12 An example for specifying S3 credential as a K8s secret is provided here . We recommend using this over the default example. Having said that, your configuration should work so check if there are any missing parameters or paste a santised version here so that we can take a look at it Thanks for raising the issue. I have issued a patch for the original bug which could close this issue. Please reopen with new comments |
Thanks! I have fixed that, now the pod
|
I installed Datashim in my K8s cluster for Minio, using the command
kubectl apply -f https://raw.githubusercontent.com/datashim-io/datashim/master/release-tools/manifests/dlf.yaml
But the pod
dataset-operator
keeps having status CrashLoopBackOff, and here is the log of this podI still do not know why, and how to fix it.
The text was updated successfully, but these errors were encountered: