sharifelgamal
commented
3 years ago This strikes me as a legitimate bug in our mounting code.
Closed iamnoah closed 1 year ago
sharifelgamal
commented
3 years ago This strikes me as a legitimate bug in our mounting code.
iamnoah
commented
3 years ago @sharifelgamal thanks for taking a look. Note that whatever is populating /etc/hosts also gets the IP wrong.
mcg1969
commented
3 years ago I'm now seeing this as well. My bridge100 address is 192.168.60.1. So far I have tried modifying the Minikube /etc/hosts manually and passing --ip 192.168.60.1 to the mount command; neither have resolved the issue. Here's the resulting log. I am guessing the timeout is a red herring, and the bind: can't assign requested address issue earlier is a more direct symptom.
Log file created at: 2021/08/03 09:13:35
Running on machine: michaels
Binary: Built with gc go1.16.1 for darwin/amd64
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
I0803 09:13:35.437102 1384 out.go:291] Setting OutFile to fd 1 ...
I0803 09:13:35.437372 1384 out.go:343] isatty.IsTerminal(1) = true
I0803 09:13:35.437380 1384 out.go:304] Setting ErrFile to fd 2...
I0803 09:13:35.437385 1384 out.go:343] isatty.IsTerminal(2) = true
I0803 09:13:35.437465 1384 root.go:316] Updating PATH: /Users/mgrant/.minikube/bin
I0803 09:13:35.437721 1384 mustload.go:65] Loading cluster: minikube
I0803 09:13:35.438346 1384 main.go:128] libmachine: Found binary path at /Users/mgrant/.minikube/bin/docker-machine-driver-hyperkit
I0803 09:13:35.438393 1384 main.go:128] libmachine: Launching plugin server for driver hyperkit
I0803 09:13:35.449024 1384 main.go:128] libmachine: Plugin server listening at address 127.0.0.1:50058
I0803 09:13:35.449541 1384 main.go:128] libmachine: () Calling .GetVersion
I0803 09:13:35.450017 1384 main.go:128] libmachine: Using API Version 1
I0803 09:13:35.450032 1384 main.go:128] libmachine: () Calling .SetConfigRaw
I0803 09:13:35.450351 1384 main.go:128] libmachine: () Calling .GetMachineName
I0803 09:13:35.450473 1384 main.go:128] libmachine: (minikube) Calling .GetState
I0803 09:13:35.450600 1384 main.go:128] libmachine: (minikube) DBG | exe=/Users/mgrant/.minikube/bin/docker-machine-driver-hyperkit uid=0
I0803 09:13:35.450723 1384 main.go:128] libmachine: (minikube) DBG | hyperkit pid from json: 1004
I0803 09:13:35.451800 1384 host.go:66] Checking if "minikube" exists ...
I0803 09:13:35.452164 1384 main.go:128] libmachine: Found binary path at /Users/mgrant/.minikube/bin/docker-machine-driver-hyperkit
I0803 09:13:35.452192 1384 main.go:128] libmachine: Launching plugin server for driver hyperkit
I0803 09:13:35.462532 1384 main.go:128] libmachine: Plugin server listening at address 127.0.0.1:50064
I0803 09:13:35.462964 1384 main.go:128] libmachine: () Calling .GetVersion
I0803 09:13:35.463369 1384 main.go:128] libmachine: Using API Version 1
I0803 09:13:35.463385 1384 main.go:128] libmachine: () Calling .SetConfigRaw
I0803 09:13:35.463656 1384 main.go:128] libmachine: () Calling .GetMachineName
I0803 09:13:35.463795 1384 main.go:128] libmachine: (minikube) Calling .DriverName
I0803 09:13:35.463912 1384 main.go:128] libmachine: (minikube) Calling .DriverName
I0803 09:13:35.464371 1384 main.go:128] libmachine: (minikube) Calling .DriverName
I0803 09:13:35.485707 1384 out.go:170] 📁 Mounting host path /Users/mgrant/Repos/anaconda-platform into VM as /Users/mgrant/Repos/anaconda-platform ...
I0803 09:13:35.506391 1384 out.go:170] ▪ Mount type:
I0803 09:13:35.527420 1384 out.go:170] ▪ User ID: docker
I0803 09:13:35.548325 1384 out.go:170] ▪ Group ID: docker
I0803 09:13:35.569339 1384 out.go:170] ▪ Version: 9p2000.L
I0803 09:13:35.590349 1384 out.go:170] ▪ Message Size: 262144
I0803 09:13:35.612431 1384 out.go:170] ▪ Permissions: 755 (-rwxr-xr-x)
I0803 09:13:35.633340 1384 out.go:170] ▪ Options: map[]
I0803 09:13:35.654317 1384 out.go:170] ▪ Bind Address: 192.160.60.1:50066
W0803 09:13:35.654482 1384 out.go:424] no arguments passed for "🚀 Userspace file server: " - returning raw string
I0803 09:13:35.654747 1384 ssh_runner.go:149] Run: /bin/bash -c "[ "x$(findmnt -T /Users/mgrant/Repos/anaconda-platform | grep /Users/mgrant/Repos/anaconda-platform)" != "x" ] && sudo umount -f /Users/mgrant/Repos/anaconda-platform || echo "
I0803 09:13:35.675306 1384 out.go:170] 🚀 Userspace file server:
I0803 09:13:35.675430 1384 main.go:128] libmachine: (minikube) Calling .GetSSHHostname
I0803 09:13:35.675622 1384 main.go:114] stdlog: ufs.go:27 listen tcp 192.160.60.1:50066: bind: can't assign requested address
W0803 09:13:35.675646 1384 out.go:424] no arguments passed for "🛑 Userspace file server is shutdown\n" - returning raw string
W0803 09:13:35.675666 1384 out.go:424] no arguments passed for "🛑 Userspace file server is shutdown\n" - returning raw string
I0803 09:13:35.675765 1384 main.go:128] libmachine: (minikube) Calling .GetSSHPort
I0803 09:13:35.701386 1384 out.go:170] 🛑 Userspace file server is shutdown
I0803 09:13:35.701678 1384 main.go:128] libmachine: (minikube) Calling .GetSSHKeyPath
I0803 09:13:35.701857 1384 main.go:128] libmachine: (minikube) Calling .GetSSHUsername
I0803 09:13:35.702040 1384 sshutil.go:53] new ssh client: &{IP:192.168.60.13 Port:22 SSHKeyPath:/Users/mgrant/.minikube/machines/minikube/id_rsa Username:docker}
I0803 09:13:35.760554 1384 mount.go:147] unmount for /Users/mgrant/Repos/anaconda-platform ran successfully
I0803 09:13:35.760581 1384 ssh_runner.go:149] Run: /bin/bash -c "sudo mkdir -m 755 -p /Users/mgrant/Repos/anaconda-platform"
I0803 09:13:35.766858 1384 ssh_runner.go:149] Run: /bin/bash -c "sudo mount -t 9p -o dfltgid=$(grep ^docker: /etc/group | cut -d: -f3),dfltuid=$(id -u docker),msize=262144,port=50066,trans=tcp,version=9p2000.L 192.160.60.1 /Users/mgrant/Repos/anaconda-platform"
I0803 09:14:07.690018 1384 ssh_runner.go:189] Completed: /bin/bash -c "sudo mount -t 9p -o dfltgid=$(grep ^docker: /etc/group | cut -d: -f3),dfltuid=$(id -u docker),msize=262144,port=50066,trans=tcp,version=9p2000.L 192.160.60.1 /Users/mgrant/Repos/anaconda-platform": (31.922163087s)
I0803 09:14:07.711683 1384 out.go:170]
W0803 09:14:07.711990 1384 out.go:235] ❌ Exiting due to GUEST_MOUNT: mount with cmd /bin/bash -c "sudo mount -t 9p -o dfltgid=$(grep ^docker: /etc/group | cut -d: -f3),dfltuid=$(id -u docker),msize=262144,port=50066,trans=tcp,version=9p2000.L 192.160.60.1 /Users/mgrant/Repos/anaconda-platform" : /bin/bash -c "sudo mount -t 9p -o dfltgid=$(grep ^docker: /etc/group | cut -d: -f3),dfltuid=$(id -u docker),msize=262144,port=50066,trans=tcp,version=9p2000.L 192.160.60.1 /Users/mgrant/Repos/anaconda-platform": Process exited with status 32
stdout:
stderr:
mount: /Users/mgrant/Repos/anaconda-platform: mount(2) system call failed: Connection timed out.
W0803 09:14:07.712103 1384 out.go:424] no arguments passed for "\n" - returning raw string
W0803 09:14:07.712149 1384 out.go:235]
W0803 09:14:07.714775 1384 out.go:424] no arguments passed for "😿 If the above advice does not help, please let us know:\n" - returning raw string
W0803 09:14:07.714800 1384 out.go:424] no arguments passed for "👉 https://github.com/kubernetes/minikube/issues/new/choose\n\n" - returning raw string
W0803 09:14:07.714806 1384 out.go:424] no arguments passed for "Please attach the following file to the GitHub issue:\n" - returning raw string
W0803 09:14:07.714929 1384 out.go:424] no arguments passed for "😿 If the above advice does not help, please let us know:\n👉 https://github.com/kubernetes/minikube/issues/new/choose\n\nPlease attach the following file to the GitHub issue:\n- /var/folders/zr/v087ks_x1dz1vr46g7jqb1880000gp/T/minikube_mount_ae8b53f7a951cd07b355402e8ec52c8ff7125fc3_0.log\n\n" - returning raw string
W0803 09:14:07.716276 1384 out.go:235] [31m╭────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮[0m
W0803 09:14:07.716293 1384 out.go:235] [31m│[0m [31m│[0m
W0803 09:14:07.716332 1384 out.go:235] [31m│[0m 😿 If the above advice does not help, please let us know: [31m│[0m
W0803 09:14:07.716345 1384 out.go:235] [31m│[0m 👉 https://github.com/kubernetes/minikube/issues/new/choose [31m│[0m
W0803 09:14:07.716351 1384 out.go:235] [31m│[0m [31m│[0m
W0803 09:14:07.716356 1384 out.go:235] [31m│[0m Please attach the following file to the GitHub issue: [31m│[0m
W0803 09:14:07.716444 1384 out.go:235] [31m│[0m - /var/folders/zr/v087ks_x1dz1vr46g7jqb1880000gp/T/minikube_mount_ae8b53f7a951cd07b355402e8ec52c8ff7125fc3_0.log [31m│[0m
W0803 09:14:07.716451 1384 out.go:235] [31m│[0m [31m│[0m
W0803 09:14:07.716457 1384 out.go:235] [31m╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯[0m
W0803 09:14:07.716649 1384 out.go:235] 
k8s-triage-robot
commented
2 years ago The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale is appliedlifecycle/stale was applied, lifecycle/rotten is appliedlifecycle/rotten was applied, the issue is closedYou can:
/remove-lifecycle stale/lifecycle rotten/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
k8s-triage-robot
commented
2 years ago The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale is appliedlifecycle/stale was applied, lifecycle/rotten is appliedlifecycle/rotten was applied, the issue is closedYou can:
/remove-lifecycle rotten/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
blacksd
commented
2 years ago This bug is still present; whenever hyperkit is not selecting the default network of 192.168.64.0/24 the start and mount command behave incorrectly.
❯ ifconfig bridge100
bridge100: flags=8a63<UP,BROADCAST,SMART,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> mtu 1500
options=3<RXCSUM,TXCSUM>
ether 16:7d:da:3c:ad:51
inet 192.168.205.1 netmask 0xffffff00 broadcast 192.168.205.255
inet6 fe80::18d6:2ca3:ade3:7b8f%bridge100 prefixlen 64 secured scopeid 0x11
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x0
member: en9 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 16 priority 0 path cost 0
Address cache:
91:b:a7:0:13:16 Vlan1 en9 1052 flags=0<>
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: activeMount fails with
Please note how it's referencing the 192.168.84.1 here too, but that CIDR it's not configured anywhere - and I'd really like to avoid passing the IP as mentioned in the probably related #12729
spowelljr
commented
2 years ago Hi @blacksd, I'm curious what version of minikube you're using. I fixed up a lot of the mounting code in December, so if you're on an older version this could possibly have been fixed.
blacksd
commented
2 years ago @spowelljr I checked just now, it's v1.25.2.
❯ minikube version
minikube version: v1.25.2
commit: 362d5fdc0a3dbee389b3d3f1034e8023e72bd3a7This is my startup routine:
❯ declare -f minikube_docker_start
minikube_docker_start () {
export KUBECONFIG="/Users/marco/.kube/config_minikube"
local -r _minikube_docker_profile="docker-only"
if [ ! -s "~/.minikube/profiles/${_minikube_docker_profile}/config.json" ]
then
rm -f ~/.minikube/config/config.json 2> /dev/null
minikube config set profile docker-only
minikube config set driver hyperkit
minikube config set cpus 2
minikube config set memory 2G
minikube config set disk-size 10G
minikube config set container-runtime docker
minikube config set kubernetes-version 0.0.0
fi
minikube start --mount --mount-string /Users:/Users
}
❯ minikube_docker_start
❗ These changes will take effect upon a minikube delete and then a minikube start
❗ These changes will take effect upon a minikube delete and then a minikube start
❗ These changes will take effect upon a minikube delete and then a minikube start
❗ These changes will take effect upon a minikube delete and then a minikube start
❗ These changes will take effect upon a minikube delete and then a minikube start
😄 [docker-only] minikube v1.25.2 on Darwin 11.6.4
▪ KUBECONFIG=/Users/marco/.kube/config_minikube
✨ Using the hyperkit driver based on user configuration
👍 Starting minikube without Kubernetes docker-only in cluster docker-only
🔥 Creating hyperkit VM (CPUs=2, Memory=2048MB, Disk=10240MB) ...
📁 Creating mount /Users:/Users ...
🏄 Done! minikube is ready without Kubernetes!
╭───────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ 💡 Things to try without Kubernetes ... │
│ │
│ - "minikube ssh" to SSH into minikube's node. │
│ - "minikube docker-env" to point your docker-cli to the docker inside minikube. │
│ - "minikube image" to build images without docker. │
│ │
╰───────────────────────────────────────────────────────────────────────────────────────╯
❯ minikube ip
192.168.205.12
❯ minikube ssh
_ _
_ _ ( ) ( )
___ ___ (_) ___ (_)| |/') _ _ | |_ __
/' _ ` _ `\| |/' _ `\| || , < ( ) ( )| '_`\ /'__`\
| ( ) ( ) || || ( ) || || |\`\ | (_) || |_) )( ___/
(_) (_) (_)(_)(_) (_)(_)(_) (_)`\___/'(_,__/'`\____)
$ mount
tmpfs on / type tmpfs (rw,relatime,size=1830292k)
devtmpfs on /dev type devtmpfs (rw,relatime,size=900288k,nr_inodes=225072,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,size=406732k,nr_inodes=819200,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,size=4096k,nr_inodes=1024,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,nr_inodes=409600)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
/dev/vda1 on /mnt/vda1 type ext4 (rw,relatime)
/dev/vda1 on /var/lib/boot2docker type ext4 (rw,relatime)
/dev/vda1 on /var/lib/docker type ext4 (rw,relatime)
/dev/vda1 on /var/lib/containerd type ext4 (rw,relatime)
/dev/vda1 on /var/lib/buildkit type ext4 (rw,relatime)
/dev/vda1 on /var/lib/containers type ext4 (rw,relatime)
/dev/vda1 on /var/log type ext4 (rw,relatime)
/dev/vda1 on /var/tmp type ext4 (rw,relatime)
/dev/vda1 on /var/lib/kubelet type ext4 (rw,relatime)
/dev/vda1 on /var/lib/cni type ext4 (rw,relatime)
/dev/vda1 on /data type ext4 (rw,relatime)
/dev/vda1 on /tmp/hostpath_pv type ext4 (rw,relatime)
/dev/vda1 on /tmp/hostpath-provisioner type ext4 (rw,relatime)
/dev/vda1 on /var/lib/minikube type ext4 (rw,relatime)
/dev/vda1 on /var/lib/toolbox type ext4 (rw,relatime)
/dev/vda1 on /var/lib/minishift type ext4 (rw,relatime)
$ ls /Users/
$This works just fine if the minikube ip is in the 192.168.84.x CIDR.
spowelljr
commented
2 years ago Do you have Internet Sharing enabled? System Preferences -> Sharing
I'm wondering if this is what's causing a different inet
blacksd
commented
2 years ago Do you have
Internet Sharingenabled?System Preferences->SharingI'm wondering if this is what's causing a different
inet
@spowelljr no, I don't have it running.
Also, this persists after the upgrade from Big Sur to Monterey. Like I mentioned in the other comment, I think the different inet started appearing after testing out other hyperkit-based implementations like colima.
tsjk
commented
2 years ago minikube mount has the --ip parameter for this, no?
So, you could do (assuming bash)
minikube mount --ip $(ggrep -oP '(?<=\sinet\s)[0-9\.]+(?=\/)' < <(ip address show bridge100 2> /dev/null)) ...
where ip is from iproute2 and ggrep is GNU grep.
blacksd
commented
2 years ago @tsjk that would probably do it, but I don't think it's something we can require from a user (installing GNU grep, detecting the actual bridge device...)
tsjk
commented
2 years ago @blacksd Ok. I do exactly this, however. I agree that it's not something I'd expect from the average user, but then again - would the average user have an altered dhcpd scope? Sometimes it's easier to educate the user than giving confusing advice. E.g. "Disable your VPN", which the more knowledgeable user needs spend time on decoding to "If you have something routable on the same network address as is chosen by the vm dhcpd you have to do something extra."
Best of all, however, may be for minikube mount to detect the bridge device. Given the machine instance it'd have all the information to set parameters right.
blacksd
commented
2 years ago @tsjk totally agree on the advanced detection performed by minikube mount - that would make the "issue" effectively transparent. I'd be happy to contribute to this.
Also, as I pointed out a few times in the previous comments, I see this case getting more and more recurring as developers are shifting from Docker Desktop to different Hyperkit-based solutions (evaluating different solutions will get you into this).
nrb
commented
2 years ago I agree that minikube should detect this, but a work around I've found for discovering the host IP without messing with the Hyperkit bridges is:
ip=$(minikube ssh -- cat /etc/resolv.conf | awk -F' ' '/^nameserver/ { print $2}' | tr -d '\r')
minikube mount --ip ${ip} <your options>Using nslookup to get the IP within the minikube VM fails because there's not a valid search server. It'll get you the IP, but also return an error code of 1. Reading resolv.conf within the minikube VM seems to be the most consistent method I've found, as /etc/hosts still lists 192.168.64.1 host.minikube.internal for me, despite my subnet being 192.168.205.
tsjk
commented
2 years ago That's nice. But you might as well ask systemd for the gateway if you want to do it from within the VM. Like
ip="`minikube ssh -- '/usr/bin/networkctl --no-pager status | awk -F '\'' '\'' '\''/^\s*Gateway:\s/ { print $2 }'\'''`"That has the upside of assuming nothing about the host environment except being able to run an sh statement.
sharifelgamal
commented
2 years ago We'd be happy to review a PR that detects this proactively.
k8s-triage-robot
commented
2 years ago The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale is appliedlifecycle/stale was applied, lifecycle/rotten is appliedlifecycle/rotten was applied, the issue is closedYou can:
/remove-lifecycle stale/lifecycle rotten/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
k8s-triage-robot
commented
1 year ago The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale is appliedlifecycle/stale was applied, lifecycle/rotten is appliedlifecycle/rotten was applied, the issue is closedYou can:
/remove-lifecycle rotten/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
CtrlZvi
commented
1 year ago This is more far reaching than just mounts. It also ruins DNS resolution of host.minikube.internal. /remove-lifecycle rotten
CtrlZvi
commented
1 year ago Adding information in case someone has more time than me to work on a PR:
bridge100 interfacebridge100tsjk
commented
1 year ago I think the interface is created by com.apple.vmnet, and IP addressing can be configured, in /Library/Preferences/SystemConfiguration/com.apple.vmnet.plist. The IP address of interface can also change if the previous address is indicated as occupied in /var/db/dhcpd_leases (I for one always clear that file before starting minikube).
k8s-triage-robot
commented
1 year ago The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale is appliedlifecycle/stale was applied, lifecycle/rotten is appliedlifecycle/rotten was applied, the issue is closedYou can:
/remove-lifecycle stale/lifecycle rotten/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
k8s-triage-robot
commented
1 year ago The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale is appliedlifecycle/stale was applied, lifecycle/rotten is appliedlifecycle/rotten was applied, the issue is closedYou can:
/remove-lifecycle rotten/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
medyagh
commented
1 year ago this issue must be fixed by this PR https://github.com/kubernetes/minikube/pull/15720 could anyone who has this problem try this binary and confirm it is fixed ? https://storage.googleapis.com/minikube-builds/15720/minikube-darwin-amd64
This PR will be included in minikube 1.29.1
tsjk
commented
1 year ago I'm not using minikube at the moment. The mac mini I used it on is rather old now. I got tired of the extra work needed for keeping it on a supported macOS version, and switched to Debian on it.
blacksd
commented
1 year ago @medyagh unfortunately the issue persist with the linked build:
❯ ./minikube-darwin-amd64 version
minikube version: v1.29.0
commit: 54702ac2ae098681775f2fb951d03d55676a1ca1
❯ rm -f ~/.minikube/config/config.json 2> /dev/null
minikube config set profile docker-only
minikube config set driver hyperkit
minikube config set cpus 2
minikube config set memory 2G
minikube config set disk-size 10G
minikube config set container-runtime docker
minikube config set kubernetes-version 0.0.0
❗ These changes will take effect upon a minikube delete and then a minikube start
❗ These changes will take effect upon a minikube delete and then a minikube start
❗ These changes will take effect upon a minikube delete and then a minikube start
❗ These changes will take effect upon a minikube delete and then a minikube start
❗ These changes will take effect upon a minikube delete and then a minikube start
❯ ./minikube-darwin-amd64 delete
🔥 Deleting "docker-only" in hyperkit ...
💀 Removed all traces of the "docker-only" cluster.
❯ ./minikube-darwin-amd64 start --mount --mount-string /Users:/Users
😄 minikube v1.29.0 on Darwin 13.2
▪ KUBECONFIG=/Users/marco/.kube/config_minikube
✨ Using the hyperkit driver based on user configuration
👍 Starting minikube without Kubernetes in cluster minikube
🔥 Creating hyperkit VM (CPUs=2, Memory=2048MB, Disk=10240MB) ...
🐳 Preparing Docker 20.10.23 ...
📁 Creating mount /Users:/Users ...
🏄 Done! minikube is ready without Kubernetes!
╭───────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ 💡 Things to try without Kubernetes ... │
│ │
│ - "minikube ssh" to SSH into minikube's node. │
│ - "minikube docker-env" to point your docker-cli to the docker inside minikube. │
│ - "minikube image" to build images without docker. │
│ │
╰───────────────────────────────────────────────────────────────────────────────────────╯
❯ ./minikube-darwin-amd64 ip
192.168.105.5
❯ ./minikube-darwin-amd64 ssh
_ _
_ _ ( ) ( )
___ ___ (_) ___ (_)| |/') _ _ | |_ __
/' _ ` _ `\| |/' _ `\| || , < ( ) ( )| '_`\ /'__`\
| ( ) ( ) || || ( ) || || |\`\ | (_) || |_) )( ___/
(_) (_) (_)(_)(_) (_)(_)(_) (_)`\___/'(_,__/'`\____)
$ mount | grep Users
$ ls /Users/
$ logout
p2c2e
commented
1 year ago @blacksd - I was the one who provided the fix. Want to validate a few things.
./minikube-darwin-amd64 mount /Users:/Users -v7
and see if this shows the 192.168.105.1:
mount: /Users: mount(2) system call failed: Connection timed out.💡 Suggestion:
If the host has a firewall:
1. Allow a port through the firewall
2. Specify "--port=<port_number>" for "minikube mount"
2. Unrelated to the issue: I see that you tried to delete the config.json and set some defaults. But, I hope you were not trying to launch the 'docker-only' profile. The started profile was default 'minikube'. I hope this was intentional.The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale is appliedlifecycle/stale was applied, lifecycle/rotten is appliedlifecycle/rotten was applied, the issue is closedYou can:
/reopen/remove-lifecycle rottenPlease send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
k8s-ci-robot
commented
1 year ago @k8s-triage-robot: Closing this issue, marking it as "Not Planned".
Steps to reproduce the issue:
minikube start --vm=true192.168.168.1in this case.minikube mount --alsologtostderr /tmp:/tmp(mount times out, logs below)Full output of failed command:
Full output of
minikube logscommand:ifconfig (note bridge100):
minikube ssh 'cat /etc/hosts'
It seems like the root cause is that minikube simply has its own IP wrong.
All software is latest version: