panic: runtime error: slice bounds out of range

[devzsolt]

I have the following error on a fresh install (Ubuntu 14.04 64bit, docker 0.10.0)

panic: runtime error: slice bounds out of range

goroutine 1 [running]:
runtime.panic(0x6a9cc0, 0xa270aa)
    /usr/lib/go/src/pkg/runtime/panic.c:266 +0xb6
main.splitDockerImage(0xc21006e3c0, 0x20, 0x40, 0xc2100489a0, 0x0, ...)
    GOPATH/src/github.com/jwilder/docker-gen/docker-gen.go:80 +0x251
main.getContainers(0xc2100524a0, 0xa3512c, 0x7f358b492d20, 0x7, 0x7fff53dd87de, ...)
    GOPATH/src/github.com/jwilder/docker-gen/docker-gen.go:203 +0x3ca
main.generateFromContainers(0xc2100524a0)
    GOPATH/src/github.com/jwilder/docker-gen/docker-gen.go:233 +0x35
main.main()
    GOPATH/src/github.com/jwilder/docker-gen/docker-gen.go:357 +0x3bd

goroutine 3 [syscall]:
os/signal.loop()
    /usr/lib/go/src/pkg/os/signal/signal_unix.go:21 +0x1e
created by os/signal.init·1
    /usr/lib/go/src/pkg/os/signal/signal_unix.go:27 +0x31

I can always repoduce the error, however it seems like that the same method works on my other computer with the same fresh OS & docker install.

If you need more info, let me know.

Please help me fixing it! Thanks!

[devzsolt]

I may have an idea what caused the error and it can be a reason for the difference between my two computers. I created images on my laptop first, then uploaded to my private docker registry. On my desktop I pulled the images from my registry and ran them locally.

So on my laptop I have running containers with an image name format: user/imagename:tag
However on my PC I have running containers from the same images with a name format server:port/imagename:tag

The newly introduced colon before port could cause the problem I guess. Could you please test it?

[devzsolt]

After stopping the above mentioned containers, tagging pulled images locally and running them by the local tags, I get a correct config file, but immediately followed by these error messages:

panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x10 pc=0x40261c]

goroutine 1 [running]:
runtime.panic(0x6a9cc0, 0xa26ea8)
    /usr/lib/go/src/pkg/runtime/panic.c:266 +0xb6
main.generateFromEvents(0xc2100534a0, 0xc21001ff50, 0x1, 0x1)
    /GOPATH/src/github.com/jwilder/docker-gen/docker-gen.go:310 +0xac
main.main()
    /GOPATH/src/github.com/jwilder/docker-gen/docker-gen.go:359 +0x405

goroutine 3 [syscall]:
os/signal.loop()
    /usr/lib/go/src/pkg/os/signal/signal_unix.go:21 +0x1e
created by os/signal.init·1
    /usr/lib/go/src/pkg/os/signal/signal_unix.go:27 +0x31

goroutine 7 [chan receive]:
main.func·001()
    /GOPATH/src/github.com/jwilder/docker-gen/docker-gen.go:161 +0x56
created by main.func·002
    /GOPATH/src/github.com/jwilder/docker-gen/docker-gen.go:168 +0x50e

goroutine 11 [finalizer wait]:
runtime.park(0x40ff90, 0xa2abe0, 0xa289e8)
    /usr/lib/go/src/pkg/runtime/proc.c:1342 +0x66
runfinq()
    /usr/lib/go/src/pkg/runtime/mgc0.c:2279 +0x84
runtime.goexit()
    /usr/lib/go/src/pkg/runtime/proc.c:1394

Do you think this is related to the original issue or it is something different?

[jwilder]

I'll take a look. Thanks for reporting and looking into them further.

[jwilder]

@miu-zsolt First stacktrace should be resolved. I don't have a private local registry setup to test the second stacktrace you posted. Can you try latest and let me know if it's resolved?

[devzsolt]

@jwilder Thank you for fixing it! I can comfirm, it works now with my private registry.
You did a great job, docker-gen is very useful, thank you!