-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tarball.Write panic: runtime error: invalid memory address or nil pointer dereference #6147
Comments
I can confirm this issue on my test box with minikube 1.6.2, Windows 10 1903 and VirtualBox 6.0.14 installed.
|
I got the same issue, detailed info as below: The exact command to reproduce the issue:
The full output of the command that failed:
The output of the
The operating system version:
|
the same problem |
Same problem on my mac |
The line in our code is:
The line in tarball.Write is:
This says to me that
The additional logging would help you figure out which image is failing to be looked up. |
If anyone runs into this, could you confirm if this binary fixes it: https://storage.googleapis.com/minikube-builds//6236/minikube-darwin-amd64 It would be nice to see the output of |
@tstromberg The binary should be https://storage.googleapis.com/minikube-builds/6236/minikube-darwin-amd64. Pls update it :) |
@tstromberg I made a test on your binary but has no luck to fix the problem. The current binaryMinikube version:
The full output of the command that failed:
The output of the minikube logs command:
6236 build binaryMinikube version:
The full output of the command that failed:
The output of the minikube logs command:
|
@ericsyh env HTTP_PROXY HTTPS_PROXY |
➜ ~ minikube start -v=1 --alsologtostderr goroutine 97 [running]: |
also tried this https://storage.googleapis.com/minikube-builds/6236/minikube-darwin-amd64 you provided ,but it doesn't work either |
OMG..Are all Chinese users above? However, (This comment is for Chinese users only) |
did anyone solved with this issue? |
thx,this works for my ubuntu 18.04. :) |
works for my OSX 10.15.2, if you are running into this error, do the following: minikube delete you can replace vmwarefusion for your own vm-driver |
Can anyone confirm whether minikube v1.7.0-beta.0 fixes the issue for them? I believe it should. Thank you. |
Works like a charm. |
Thank you @Veitor , this works for me as well on macOS 10.15.1 with minikube 1.6.2
|
Note: this is fixed in minikube 1.7.0! |
this works to me |
I use shell command to install kubectl and minikube, it works |
The exact command to reproduce the issue:
minikube start --vm-driver=virtualbox (Administrator)
The full output of the command that failed:
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x28 pc=0x12ee976]
goroutine 103 [running]:
github.com/google/go-containerregistry/pkg/v1/tarball.Write(0x0, 0xc0003b4030, 0xa, 0xc0003b403b, 0xe, 0xc0003b404a, 0x7, 0x0, 0x0, 0xc00062bc58, ...)
/go/pkg/mod/github.com/google/[email protected]/pkg/v1/tarball/write.go:57 +0x136
k8s.io/minikube/pkg/minikube/machine.CacheImage(0xc0003b4030, 0x21, 0xc0004b41e0, 0x46, 0x0, 0x0)
/app/pkg/minikube/machine/cache_images.go:395 +0x615
k8s.io/minikube/pkg/minikube/machine.CacheImages.func1(0xc0004aff68, 0x0)
/app/pkg/minikube/machine/cache_images.go:85 +0xed
golang.org/x/sync/errgroup.(*Group).Go.func1(0xc00033db90, 0xc00033dbf0)
/go/pkg/mod/golang.org/x/[email protected]/errgroup/errgroup.go:57 +0x6b
created by golang.org/x/sync/errgroup.(*Group).Go
/go/pkg/mod/golang.org/x/[email protected]/errgroup/errgroup.go:54 +0x6d
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x28 pc=0x12ee976]
goroutine 106 [running]:
github.com/google/go-containerregistry/pkg/v1/tarball.Write(0x0, 0xc00055e300, 0xa, 0xc00055e30b, 0x7, 0xc00055e313, 0x5, 0x0, 0x0, 0xc000699c58, ...)
/go/pkg/mod/github.com/google/[email protected]/pkg/v1/tarball/write.go:57 +0x136
k8s.io/minikube/pkg/minikube/machine.CacheImage(0xc00055e300, 0x18, 0xc000598180, 0x3d, 0x0, 0x0)
/app/pkg/minikube/machine/cache_images.go:395 +0x615
k8s.io/minikube/pkg/minikube/machine.CacheImages.func1(0xc0004adf68, 0x0)
/app/pkg/minikube/machine/cache_images.go:85 +0xed
golang.org/x/sync/errgroup.(*Group).Go.func1(0xc00033db90, 0xc00033dc80)
/go/pkg/mod/golang.org/x/[email protected]/errgroup/errgroup.go:57 +0x6b
created by golang.org/x/sync/errgroup.(*Group).Go
/go/pkg/mod/golang.org/x/[email protected]/errgroup/errgroup.go:54 +0x6d
The output of the
minikube logs
command:X command runner: getting ssh client for bootstrapper: Error dialing tcp via ssh client: dial tcp 127.0.0.1:22: connectex: No connection could be made because the target machine actively refused it.
The operating system version:
Windows 10 Pro 1903
VirtualBox 6.1.0 platform packages with VirtualBox 6.1.0 Oracle VM VirtualBox Extension Pack
Hyper-V Requirements: 虚拟机监视器模式扩展: 是
固件中已启用虚拟化: 是
二级地址转换: 是
数据执行保护可用: 是
The text was updated successfully, but these errors were encountered: