<p>I want to start minikube to learn Kubernetes but am having trouble because of error <code>RSRC_INSUFFICIENT_CORES</code>.
My mac has 2 CPU cores and minikube docs say that 2 cores are required.
Here a the machine specs from &quot;About this Mac&quot;:</p>
<ul>
<li>MacBook Pro (15-inch, Late 2008)</li>
<li>Processor 2.4 GHz Intel Core 2 Duo</li>
<li>Memory 8 GB 1067 MHz DDR3</li>
</ul>
<p>This machine has VirtualBox Version 5.2.35 r135669 but its not running, and working docker and docker-machine, as shown here:</p>
<pre><code>✗ docker-machine --version
docker-machine version 0.16.1, build 

✗ docker --version
Docker version 17.05.0-ce, build 89658be
</code></pre>
<p>I have successfully installed minikube v1.25.1 using an updated version of MacPorts, as shown here:</p>
<pre><code>✗ which minikube    
/opt/local/bin/minikube

✗ minikube version

minikube version: v1.25.1
</code></pre>
<p>I cannot start minikube and get error: <code>Exiting due to RSRC_INSUFFICIENT_CORES</code>.  Here is the output that I see from 2 different <code>minikube start</code> attempts:</p>
<pre><code>✗ minikube start --cpus=2

😄   minikube v1.25.1 on Darwin 10.11.6
✨   Automatically selected the docker driver. Other choices: virtualbox, ssh
- Ensure your docker daemon has access to enough CPU/memory resources.
- Docs https://docs.docker.com/docker-for-mac/#resources

⛔   Exiting due to RSRC_INSUFFICIENT_CORES: Requested cpu count 2 is greater than the available cpus of 1

✗ minikube start --cpus=1

😄   minikube v1.25.1 on Darwin 10.11.6
✨   Automatically selected the docker driver. Other choices: virtualbox, ssh

⛔   Exiting due to RSRC_INSUFFICIENT_CORES: Requested cpu count 1 is less than the minimum allowed of 2
</code></pre>
<p>Please excuse newbie-ness--this is my first ever SO question!</p>
<p>Is it impossible to start minikube on this Mac?</p>

<p>I ran into these errors on an M1 Mac because my podman (4.0.2) did not have the VM configured with enough capacity.  <a href="https://itnext.io/goodbye-docker-desktop-hello-minikube-3649f2a1c469" rel="noreferrer">Abhinav Sonkar</a> figured out how to fix this.  This builds on his trail blazing.</p>
<p>First you may need to get rid of your existing <a href="https://docs.podman.io/en/latest/markdown/podman-machine.1.html" rel="noreferrer">VM in podman</a>:</p>
<pre><code>podman machine stop
podman machine rm
</code></pre>
<p>Then recreate it with adequate specs and tweak the connections to <a href="https://minikube.sigs.k8s.io/docs/drivers/podman/" rel="noreferrer">work around</a> another issue:</p>
<pre><code>podman machine init --cpus 6 --memory 12288 --disk-size 50
podman machine start
podman system connection default podman-machine-default-root
</code></pre>
<p>After that I was able to install minikube from <code>brew</code> and start it with:</p>
<pre><code>minikube start --driver=podman --container-runtime=cri-o
</code></pre>
<p>With that the <code>minikube</code> subcommands work and <code>kubectl</code> seems fine talking to it.  I've also gotten <code>minikube start</code> to work with <code>--kubernetes-version=v1.23.5</code>, <code>v1.22.5</code>, <code>v1.22.8</code> and <code>v1.23.2</code>.</p>
