kubernetes/minikube

--host-only-cidr: invalid CIDR address: '192.168.99.1/24'

Open

#7,063 opened on Mar 16, 2020

View on GitHub
 (14 comments) (0 reactions) (0 assignees)Go (31,799 stars) (5,222 forks)batch import
co/virtualboxgood first issuehelp wantedkind/buglifecycle/frozenpriority/backlog

Description

With my ancient minikube version (1.4.0), I had been using the option

--host-only-cidr='192.168.99.1/24'

which now gives me

X Unable to start VM. Please investigate and run 'minikube delete' if possible: driver start: Error 
setting up host only network on machine start: invalid CIDR address: '192.168.99.1/24'

with both 1.8.1 and 1.8.2. I used the option to make sure that the minikube VM gets attached to the right host-only network. It now seemed to work fine without it, so this might be no longer needed, but still...

Regards J

Contributor guide

Tech stack
go
Domain
devops
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic minikube usageunderstanding of CIDR notation
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The issue reports that the ` host only cidr` flag with a host specific CIDR (e.g., '192.168.99.1/24') is rejected as invalid. The error originates from the VirtualBox driver setup code. Look in the minikube repository under `pkg/drivers/virtualbox` or `pkg/network` for CIDR validation logic. The fix may involve relaxing validation to allow host addresses or improving the error message to clarify that a network address is expected. Check the comments on the issue for user workarounds and maintainer hints. No linked PRs exist, so investigate the latest code on the master branch.