mayurans commented on issue #736: camel-k-cache crashes on minikube URL: https://github.com/apache/camel-k/issues/736#issuecomment-501018153 I've re-deployed minikube and tried latest kamel binary (0.3.4). But, I'm still getting the same runtime error in `camel-k-cache`. minikube config: ``` $ minikube version minikube version: v1.1.1 $ cat ~/.minikube/config/config.json { "cpus": 4, "disk-size": "50g", "kubernetes-version": "v1.12.0", "memory": 8192, "profile": "camelk", "registry": true, "vm-driver": "kvm2" } $minikube start -p camelk --extra-config=apiserver.enable-admission-plugins="LimitRanger,NamespaceExists,NamespaceLifecycle,ResourceQuota,ServiceAccount,DefaultStorageClass,MutatingAdmissionWebhook" ``` Kamel config: ``` $ kamel version Camel K Client 0.3.4 $kamel install $ kubectl get pods -w NAME READY STATUS RESTARTS AGE camel-k-operator-66b855c5f-g4h6j 0/1 Pending 0 1s camel-k-operator-66b855c5f-g4h6j 0/1 Pending 0 1s camel-k-operator-66b855c5f-g4h6j 0/1 ContainerCreating 0 1s camel-k-cache 0/1 Pending 0 0s camel-k-cache 0/1 Pending 0 0s camel-k-cache 0/1 Pending 0 0s camel-k-cache 0/1 Init:0/1 0 0s camel-k-operator-66b855c5f-g4h6j 1/1 Running 0 45s camel-k-cache 0/1 PodInitializing 0 3s camel-k-cache 1/1 Running 0 13s camel-k-cache 0/1 Error 0 44s ``` camel-k-cache log: ``` $ kubectl logs camel-k-cache panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0xf13712] goroutine 1 [running]: github.com/GoogleContainerTools/kaniko/pkg/cache.WarmCache(0x1977fe0, 0xf25480, 0xc42036dcd8) /go/src/github.com/GoogleContainerTools/kaniko/pkg/cache/warm.go:47 +0x372 github.com/GoogleContainerTools/kaniko/cmd/warmer/cmd.glob..func2(0x196f140, 0xc4202e7380, 0x0, 0x2) /go/src/github.com/GoogleContainerTools/kaniko/cmd/warmer/cmd/root.go:54 +0x2d github.com/GoogleContainerTools/kaniko/vendor/github.com/spf13/cobra.(*Command).execute(0x196f140, 0xc4200a4070, 0x2, 0x2, 0x196f140, 0xc4200a4070) /go/src/github.com/GoogleContainerTools/kaniko/vendor/github.com/spf13/cobra/command.go:766 +0x2c1 github.com/GoogleContainerTools/kaniko/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0x196f140, 0x0, 0x4, 0x116cca9) /go/src/github.com/GoogleContainerTools/kaniko/vendor/github.com/spf13/cobra/command.go:852 +0x30a github.com/GoogleContainerTools/kaniko/vendor/github.com/spf13/cobra.(*Command).Execute(0x196f140, 0xc42036df78, 0xc42009e058) /go/src/github.com/GoogleContainerTools/kaniko/vendor/github.com/spf13/cobra/command.go:800 +0x2b main.main() /go/src/github.com/GoogleContainerTools/kaniko/cmd/warmer/main.go:26 +0x2d ``` docker images in minikube: ``` $ minikube ssh _ _ _ _ ( ) ( ) ___ ___ (_) ___ (_)| |/') _ _ | |_ __ /' _ ` _ `\| |/' _ `\| || , < ( ) ( )| '_`\ /'__`\ | ( ) ( ) || || ( ) || || |\`\ | (_) || |_) )( ___/ (_) (_) (_)(_)(_) (_)(_)(_) (_)`\___/'(_,__/'`\____) $ docker images REPOSITORY TAG IMAGE ID CREATED SIZE busybox latest ef46e0caa533 22 hours ago 1.21MB apache/camel-k 0.3.4 4e98c80fd813 4 days ago 524MB gcr.io/kaniko-project/warmer v0.9.0 b454d1cbac22 4 months ago 22.8MB k8s.gcr.io/kube-addon-manager v9.0 119701e77cbc 4 months ago 83.1MB k8s.gcr.io/kubernetes-dashboard-amd64 v1.10.1 f9aed6605b81 5 months ago 122MB k8s.gcr.io/kube-apiserver v1.12.0 ab60b017e34f 8 months ago 194MB k8s.gcr.io/kube-controller-manager v1.12.0 07e068033cf2 8 months ago 164MB k8s.gcr.io/kube-proxy v1.12.0 9c3a9d3f09a0 8 months ago 96.6MB k8s.gcr.io/kube-scheduler v1.12.0 5a1527e735da 8 months ago 58.3MB k8s.gcr.io/etcd 3.2.24 3cab8e1b9802 8 months ago 220MB k8s.gcr.io/coredns 1.2.2 367cdc8433a4 9 months ago 39.2MB k8s.gcr.io/k8s-dns-dnsmasq-nanny-amd64 1.14.8 c2ce1ffb51ed 17 months ago 41MB k8s.gcr.io/k8s-dns-sidecar-amd64 1.14.8 6f7f2dc7fab5 17 months ago 42.2MB k8s.gcr.io/k8s-dns-kube-dns-amd64 1.14.8 80cc5ea4b547 17 months ago 50.5MB k8s.gcr.io/pause 3.1 da86e6ba6ca1 17 months ago 742kB gcr.io/k8s-minikube/storage-provisioner v1.8.1 4689081edb10 19 months ago 80.8MB ```
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
