Skip to content

VM driver wont work if user path is too long #21087

Description

@medyagh

when tryin to run qemu in github action it is not happy that
'/Users/runner/work/minikube/minikube/minikube_binaries/testhome/.minikube/machines/functional-405000/monitor' is too long

we should Detect this and if this happening the LEAST we could do is warn ppl so it doesnt blow up in an ugly way
and most we could do is actually find a way to fix that

=== RUN   TestFunctional/serial/StartWithProxy
    functional_test.go:2251: (dbg) Run:  ./minikube-darwin-amd64 start -p functional-405000 --memory=4096 --apiserver-port=8441 --wait=all --vm-driver=qemu --wait-timeout=15m --network socket_vmnet
    functional_test.go:2251: (dbg) Non-zero exit: ./minikube-darwin-amd64 start -p functional-405000 --memory=4096 --apiserver-port=8441 --wait=all --vm-driver=qemu --wait-timeout=15m --network socket_vmnet: exit status 80 (23.564294248s)
        
        -- stdout --
        	* [functional-405000] minikube v1.36.0 on Darwin 13.7.6
        	  - MINIKUBE_HOME=/Users/runner/work/minikube/minikube/minikube_binaries/testhome
        	  - KUBECONFIG=/Users/runner/work/minikube/minikube/minikube_binaries/testhome/kubeconfig
        	* Using the qemu2 driver based on user configuration
        	* Downloading VM boot image ...
        	* Starting "functional-405000" primary control-plane node in "functional-405000" cluster
        	* Downloading Kubernetes v1.33.2 preload ...
        	* Creating qemu2 VM (CPUs=2, Memory=4096MB, Disk=20000MB) ...
        	OUTPUT: 
        	ERROR: qemu-system-x86_64: -qmp unix:/Users/runner/work/minikube/minikube/minikube_binaries/testhome/.minikube/machines/functional-405000/monitor,server,nowait: UNIX socket path '/Users/runner/work/minikube/minikube/minikube_binaries/testhome/.minikube/machines/functional-405000/monitor' is too long
        	Path must be less than 104 bytes
        	
        	* Deleting "functional-405000" in qemu2 ...
        	* Creating qemu2 VM (CPUs=2, Memory=4096MB, Disk=20000MB) ...
        	OUTPUT: 
        	ERROR: qemu-system-x86_64: -qmp unix:/Users/runner/work/minikube/minikube/minikube_binaries/testhome/.minikube/machines/functional-405000/monitor,server,nowait: UNIX socket path '/Users/runner/work/minikube/minikube/minikube_binaries/testhome/.minikube/machines/functional-405000/monitor' is too long
        	Path must be less than 104 bytes

Metadata

Metadata

Assignees

Labels

co/krunkitKrunkit related issuesco/qemu-driverQEMU related issuesco/vfkitVFkit related issueslifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.

Type

Fields

No fields configured for Bug.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions