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
start cluster on Mac hangs with minikube. docker container started, but the correct ip is vm ip, not the host ip. minikube ip is 192.168.64.28 on my laptop. 192.168.2.2 is the host ip.
$ ./cn cluster start mycluster -f huge
Using /Users/<name>/workspace/go/src/github.com/ceph/cn/cn.toml as configuration file
2019/12/09 21:21:00 Cluster mycluster is already running!
2019/12/09 21:21:20 Timeout while trying to reach: http://192.168.2.2:8000
2019/12/09 21:21:20 S3 gateway for cluster mycluster is not responding. Showing S3 logs (if any):
^cat: /var/log/ceph/client.rgw.ceph-nano-mycluster-faa32aebf00b.log: No such file or directory
2019/12/09 21:21:20 Please open an issue at: https://github.com/ceph/cn.
The text was updated successfully, but these errors were encountered:
start cluster on Mac hangs with minikube. docker container started, but the correct ip is vm ip, not the host ip. minikube ip is 192.168.64.28 on my laptop. 192.168.2.2 is the host ip.
The text was updated successfully, but these errors were encountered: