minikube quick start xhyve deprecated/removed

[jobergum]

https://docs.vespa.ai/documentation/vespa-quick-start-kubernetes.html

minikube start --vm-driver xhyve --memory 4096
😄  minikube v1.23.2 on Darwin 11.6

❌  Exiting due to DRV_UNSUPPORTED_OS: The driver 'xhyve' is not supported on darwin/amd64

Seems like the current is using hyperkit instead, ref https://github.com/kubernetes/minikube/issues/5481

minikube start --vm-driver hyperkit --memory 4096

[kkraune]

Looping in expert @griseau

[griseau]

Hey @kkraune don't know much about minikube.. I can try to give it a go with hyperkit if needed and see if it works

[kkraune]

that would be great - thanks!

[griseau]

Hey guys, sorry I've been pretty busy in the past days. I checked minikube and the driver you want to use depends on the machine you're using and the hypervisor you can install. I've seen we can use docker so I guess it's the easiest solution. I tried with minikube start --vm-driver docker --memory 4096 but the container fails with the following error :

Running /opt/vespa/libexec/vespa/start-configserver
Creating data directory /opt/vespa/var/zookeeper/version-2
Failed extending datasegment: : Cannot allocate memory
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
/opt/vespa/libexec/vespa/start-configserver: line 160:   681 Segmentation fault      printenv > $cfpfile
Failed extending datasegment: : Cannot allocate memory
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
/opt/vespa/libexec/vespa/start-configserver: line 88:   684 Segmentation fault      chown ${VESPA_USER} $1
Failed extending datasegment: : Cannot allocate memory
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
/opt/vespa/libexec/vespa/start-configserver: line 88:   687 Segmentation fault      chmod 755 $1
Failed extending datasegment: : Cannot allocate memory
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
/opt/vespa/libexec/vespa/start-configserver: line 198:   690 Segmentation fault      vespa-run-as-vespa-user vespa-runserver -s configserver -r 30 -p $pidfile -- java -Xms128m -Xmx2048m -XX:+PreserveFramePointer -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath="${VESPA_HOME}/var/crash" -XX:ErrorFile="${VESPA_HOME}/var/crash/hs_err_pid%p.log" -XX:+ExitOnOutOfMemoryError -XX:-OmitStackTraceInFastThrow -XX:MaxJavaStackTraceDepth=1000000 $jvmargs --illegal-access=warn --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens=java.base/jdk.internal.loader=ALL-UNNAMED --add-opens=java.base/sun.security.ssl=ALL-UNNAMED -Djava.io.tmpdir=${VESPA_HOME}/tmp -Djava.library.path=${VESPA_HOME}/lib64 -Djava.awt.headless=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.net.client.defaultConnectTimeout=5000 -Dsun.net.client.defaultReadTimeout=60000 -Djavax.net.ssl.keyStoreType=JKS -Djdk.tls.rejectClientInitiatedRenegotiation=true -Djdisc.config.file=$cfpfile -Djdisc.export.packages= -Djdisc.cache.path=$bundlecachedir -Djdisc.bundle.path=${VESPA_HOME}/lib/jars -Djdisc.logger.enabled=true -Djdisc.logger.level=ALL -Djdisc.logger.tag=jdisc/configserver -Dfile.encoding=UTF-8 -Dzookeeper_log_file_prefix=${ZOOKEEPER_LOG_FILE_PREFIX} -cp "$CP" com.yahoo.jdisc.core.StandaloneMain standalone-container-jar-with-dependencies.jar

Also the statefulset used apps/v1beta1 is not supported anymore since Kubernetes 1.16, I'm creating another issue for that

[jobergum]

The above happens due to insufficient memory for the container. The configuration server fails to start. I Will check. Thanks a lot @griseau!

[kkraune]

Fixed in https://github.com/vespa-engine/documentation/pull/1782