I think the error might somehow be related to minio/s3 support. I tried disabling the minio plugin, and I now got a different error on the same migration:
boto.exception.S3ResponseError: S3ResponseError: 403 Forbidden
It’s not clear from the documentation whether you can install tutor on minikube without either setting up S3 or minio, and if so, how you would do that.
The documentation mentions that you need to set up minio.LMS_HOST, but if you are running minikube on a local installation only with editing /etc/hosts, those host entries can not be resolved inside minikube.
What I made work was:
- Enable minio plugin:
tutor plugins enable minio - Enable minikube ingress controller:
minikube addons enable ingress - Expose minikube ingress controller as a service:
kubectl expose deployment nginx-ingress-controller --port=80 --target-port=80 -n kube-system - Add a CoreDNS rewrite rule:
kubectl edit configmap -n kube-system corednsaddingrewrite name minio.www.myopenedx.com nginx-ingress-controller.kube-system.svc.cluster.localas explained here: https://coredns.io/2017/05/08/custom-dns-entries-for-kubernetes/ (remember to reload CoreDNS as described, or for minikube just kill the coredns pods in the kube-system namespace to have them restarted)
With these changes in place, I was able to successfully complete the migrations and have a working tutor setup in minikube.