We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
通过 minikube 启动k8s 集群命令如下: minikube start --driver=docker --cpus=2 --memory='4g' --kubernetes-version=v1.19.8 --docker-env http_proxy=http://127.0.0.1:1081 --docker-env https_proxy=http://127.0.0.1:1081 --docker-env no_proxy=localhost,127.0.0.1,::1,192.168.31.0/24,192.168.99.0/24 --alsologtostderr --registry-mirror="https://jfnjj5zp.mirror.aliyuncs.com" 重现问题所需的命令: minikube config get cpus && minikube config get memory
minikube start --driver=docker --cpus=2 --memory='4g' --kubernetes-version=v1.19.8 --docker-env http_proxy=http://127.0.0.1:1081 --docker-env https_proxy=http://127.0.0.1:1081 --docker-env no_proxy=localhost,127.0.0.1,::1,192.168.31.0/24,192.168.99.0/24 --alsologtostderr --registry-mirror="https://jfnjj5zp.mirror.aliyuncs.com"
失败的命令的完整输出:
minikube logs命令的输出:
minikube logs
使用的操作系统版本: go version go1.15.10 darwin/amd64 macOS mojave 10.14.1 minikube version: v1.17.1
The text was updated successfully, but these errors were encountered:
No branches or pull requests
通过 minikube 启动k8s 集群命令如下:
minikube start --driver=docker --cpus=2 --memory='4g' --kubernetes-version=v1.19.8 --docker-env http_proxy=http://127.0.0.1:1081 --docker-env https_proxy=http://127.0.0.1:1081 --docker-env no_proxy=localhost,127.0.0.1,::1,192.168.31.0/24,192.168.99.0/24 --alsologtostderr --registry-mirror="https://jfnjj5zp.mirror.aliyuncs.com"
重现问题所需的命令:
minikube config get cpus && minikube config get memory
失败的命令的完整输出:
Error: specified key could not be found in config
minikube logs
命令的输出:minikube-logs.txt
使用的操作系统版本:
go version go1.15.10 darwin/amd64
macOS mojave 10.14.1
minikube version: v1.17.1
The text was updated successfully, but these errors were encountered: