Skip to content
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

crictl images fails with panic: runtime error: slice bounds out of range #265

Closed
adelton opened this issue Mar 14, 2018 · 6 comments
Closed
Assignees

Comments

@adelton
Copy link
Contributor

adelton commented Mar 14, 2018

With CRI-O build from its master (712f3b8cf14cbbac298f3ccc020677ac2a65fa75) and cri-tools built from its master (a6dd109), running

# crictl pull registry.fedoraproject.org/fedora:27

passed but

# crictl images

fails with

panic: runtime error: slice bounds out of range

goroutine 1 [running]:
main.glob..func13(0xc4200738c0, 0x0, 0xc4200738c0)
	/root/cri-tools/_output/src/github.com/kubernetes-incubator/cri-tools/cmd/crictl/image.go:155 +0x1002
github.com/kubernetes-incubator/cri-tools/vendor/github.com/urfave/cli.HandleAction(0xca43a0, 0xe233f0, 0xc4200738c0, 0xc420055000, 0x0)
	/root/cri-tools/_output/src/github.com/kubernetes-incubator/cri-tools/vendor/github.com/urfave/cli/app.go:490 +0xd2
github.com/kubernetes-incubator/cri-tools/vendor/github.com/urfave/cli.Command.Run(0xdc4743, 0x6, 0x0, 0x0, 0x0, 0x0, 0x0, 0xdc9024, 0xb, 0x0, ...)
	/root/cri-tools/_output/src/github.com/kubernetes-incubator/cri-tools/vendor/github.com/urfave/cli/command.go:210 +0xa95
github.com/kubernetes-incubator/cri-tools/vendor/github.com/urfave/cli.(*App).Run(0xc420061a00, 0xc42000c060, 0x2, 0x2, 0x0, 0x0)
	/root/cri-tools/_output/src/github.com/kubernetes-incubator/cri-tools/vendor/github.com/urfave/cli/app.go:255 +0x6f8
main.main()
	/root/cri-tools/_output/src/github.com/kubernetes-incubator/cri-tools/cmd/crictl/main.go:218 +0xc71

Running

# crictl images --no-trunc

shows

IMAGE                               TAG                 IMAGE ID                                                           SIZE
<none>                              <none>                                                                                 0B
registry.fedoraproject.org/fedora   27                  99b71991af6eef73e85e3a657641cf2447929f37fff1f9570d525a6ef485a4a8   246MB
@adelton
Copy link
Contributor Author

adelton commented Mar 14, 2018

I forgot -- the crictl was configured with

echo 'runtime-endpoint: unix:///var/run/crio/crio.sock' > /etc/crictl.yaml

and this is on Fedora 27 host.

@mrunalp
Copy link
Member

mrunalp commented Mar 14, 2018

cc: @runcom

@runcom
Copy link
Contributor

runcom commented Mar 14, 2018

Will look, thanks for the report!

@mrunalp
Copy link
Member

mrunalp commented Mar 14, 2018

@adelton One of the PRs that went into cri-o master broke this. This isn't a cri-tools issue.

@feiskyer
Copy link
Member

Even in this case, crictl shouldn't panic itself. Let me file a PR to fix this.

/assign

@adelton
Copy link
Contributor Author

adelton commented Mar 15, 2018

Should this somehow be reported to CRI-O as well?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants