bitcoin-dev-project / warnet

Monitor and analyze the emergent behaviors of Bitcoin networks
https://warnet.dev
MIT License
93 stars 35 forks source link

setup: check that docker desktop users have enabled kubernetes #650

Closed pinheadmz closed 1 month ago

pinheadmz commented 1 month ago

:-(

(.venv) --> warnet setup

                    ╭───────────────────────────╮
                    │  Welcome to Warnet Setup  │
                    ╰───────────────────────────╯

    Let's find out if your system has what it takes to run Warnet...

[?] Which platform would you like to use?:
   Minikube
 > Docker Desktop
   No Backend (Interacting with remote cluster, see `warnet auth --help`)

 ⭐️ Kubectl is satisfied: /Users/matthewzipkin/Desktop/work/warnet/.venv/bin/kubectl
 ⭐️ Helm is satisfied: /Users/matthewzipkin/Desktop/work/warnet/.venv/bin/helm
 ⭐️ Docker is satisfied: /usr/local/bin/docker
 ⭐️ Docker Desktop is satisfied: /usr/local/bin/docker
 ⭐️ Running Docker is satisfied: docker is running
 💥 Kubernetes Running in Docker Desktop is not satisfied.
    Instruction: Please enable the local kubernetes cluster in Docker Desktop
    URL: https://docs.docker.com/desktop/kubernetes/
Please fix the installation issues above and try setup again.

:-)


(.venv) --> warnet setup

                    ╭───────────────────────────╮
                    │  Welcome to Warnet Setup  │
                    ╰───────────────────────────╯

    Let's find out if your system has what it takes to run Warnet...

[?] Which platform would you like to use?:
   Minikube
 > Docker Desktop
   No Backend (Interacting with remote cluster, see `warnet auth --help`)

 ⭐️ Kubectl is satisfied: /Users/matthewzipkin/Desktop/work/warnet/.venv/bin/kubectl
 ⭐️ Helm is satisfied: /Users/matthewzipkin/Desktop/work/warnet/.venv/bin/helm
 ⭐️ Docker is satisfied: /usr/local/bin/docker
 ⭐️ Docker Desktop is satisfied: /usr/local/bin/docker
 ⭐️ Running Docker is satisfied: docker is running
 ⭐️ Kubernetes Running in Docker Desktop is satisfied:
        Kubernetes control plane is running at https://kubernetes.docker.internal:6443
        CoreDNS is running at https://kubernetes.docker.internal:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

        To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
 ⭐️ Warnet prerequisites look good.