Skip to content
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

aws vm: Error : there are only 1 CPUs available. #7907

Closed
r-suresh-kumar opened this issue Apr 25, 2020 · 3 comments
Closed

aws vm: Error : there are only 1 CPUs available. #7907

r-suresh-kumar opened this issue Apr 25, 2020 · 3 comments
Labels
kind/support Categorizes issue or PR as a support question. needs-faq-entry Things that could use documentation in a FAQ needs-solution-message Issues where where offering a solution for an error would be helpful priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@r-suresh-kumar
Copy link

Steps to reproduce the issue:

Pre-condition:
I am using Amazon EC2 linux instance with virtualization set to hvm.
But when I use command "grep -E --color 'vmx|svm' /proc/cpuinfo" to check if virtualization is enabled or disabled, it does not give any response.......I guess, virtualization is disabled. Please correct me if i am wrong

  1. $ minikube start --vm-driver=none

OR

  1. $ minikube start --driver=docker

OR

  1. $ minikube start --no-vtx-check=false

minikube v1.9.2 on Amazon 2018.03 (xen/amd64)
Using the docker driver based on existing profile
Starting control plane node m01 in cluster minikube
Pulling base image ...
docker "minikube" container is missing, will recreate.
Creating Kubernetes in docker container with (CPUs=2) (1 available), Memory=985MB (985MB available) ...
StartHost failed, but will try again: recreate: creating host: create: creating: create kic node: create container: failed args: [run -d -t --privileged --security-opt seccomp=unconfined --tmpfs /tmp --tmpfs /run -v /lib/modules:/lib/modules:ro --hostname minikube --name minikube --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --label role.minikube.sigs.k8s.io= --label mode.minikube.sigs.k8s.io=minikube --volume minikube:/var --cpus=2 --memory=985mb --expose 8443 --publish=127.0.0.1::8443 --publish=127.0.0.1::22 --publish=127.0.0.1::2376 gcr.io/k8s-minikube/kicbase:v0.0.8@sha256:2f3380ebf1bb0c75b0b47160fd4e61b7b8fef0f1f32f9def108d3eada50a7a81] output: docker: Error response from daemon: Range of CPUs is from 0.01 to 1.00, as there are only 1 CPUs available.
See 'docker run --help'.
: exit status 125
docker "minikube" container is missing, will recreate.
Creating Kubernetes in docker container with (CPUs=2) (1 available), Memory=985MB (985MB available) ...

Failed to start docker container. "minikube start" may fix it.: recreate: creating host: create: creating: create kic node: create container: failed args: [run -d -t --privileged --security-opt seccomp=unconfined --tmpfs /tmp --tmpfs /run -v /lib/modules:/lib/modules:ro --hostname minikube --name minikube --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --label role.minikube.sigs.k8s.io= --label mode.minikube.sigs.k8s.io=minikube --volume minikube:/var --cpus=2 --memory=985mb --expose 8443 --publish=127.0.0.1::8443 --publish=127.0.0.1::22 --publish=127.0.0.1::2376 gcr.io/k8s-minikube/kicbase:v0.0.8@sha256:2f3380ebf1bb0c75b0b47160fd4e61b7b8fef0f1f32f9def108d3eada50a7a81] output: docker: Error response from daemon: Range of CPUs is from 0.01 to 1.00, as there are only 1 CPUs available.
See 'docker run --help'.
: exit status 125

minikube is exiting due to an error. If the above message is not useful, open an issue:
https://github.com/kubernetes/minikube/issues/new/choose

@medyagh
Copy link
Member

medyagh commented Apr 25, 2020

@r-suresh-kumar while the error looks scray and I appologize we need to make the error look better, and provide better action,

it seems that you are running minikube on VM with only 1 CPU ? the minimum required number of CPU cores are 2. could you please verify and try with a VM with higher CPU ccounts?

@medyagh medyagh added needs-solution-message Issues where where offering a solution for an error would be helpful priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/needs-information Indicates an issue needs more information in order to work on it. labels Apr 25, 2020
@medyagh medyagh changed the title minikube does not get started in Linux (AWS Instance) minikube on AWS Instance: Error response from daemon: there are only 1 CPUs available. Apr 25, 2020
@medyagh medyagh changed the title minikube on AWS Instance: Error response from daemon: there are only 1 CPUs available. on AWS Instance: Error response from daemon: there are only 1 CPUs available. Apr 25, 2020
@medyagh medyagh changed the title on AWS Instance: Error response from daemon: there are only 1 CPUs available. aws vm: Error response from daemon: there are only 1 CPUs available. Apr 25, 2020
@medyagh medyagh changed the title aws vm: Error response from daemon: there are only 1 CPUs available. aws vm: Error : there are only 1 CPUs available. Apr 25, 2020
@tstromberg tstromberg added the kind/support Categorizes issue or PR as a support question. label Apr 26, 2020
@r-suresh-kumar
Copy link
Author

Thank you for the response. Let me check and fix your recommendations.

@tstromberg
Copy link
Contributor

minikube needs 2 CPU's. We'll need to clean up the error message to be more actionable, as well as add a FAQ item.

@tstromberg tstromberg added the needs-faq-entry Things that could use documentation in a FAQ label Apr 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. needs-faq-entry Things that could use documentation in a FAQ needs-solution-message Issues where where offering a solution for an error would be helpful priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

3 participants