Docker Community Forums

Share and learn in the Docker community.

Docker inspect stopped working after upgrade


(Per Rovegård) #1

Expected behavior

It shold be possible to run:

docker inspect <imagename>

Actual behavior

Running docker inspect with an image gives:

[]
An error occurred trying to connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/hello-world/json: EOF

…with exit status 1

Information

  • the output of:
    • Moby Notification > Diagose & Feedback on Windows

Sorry, don’t know where Moby Notification is. If I open the log file from Diagnose & Feedback in the Docker tray, I get (among other things):

[13:38:07.072][ProxyProcess   ][Info   ] proxy >> GET /v1.24/containers/hello-world/json
[13:38:07.075][ProxyProcess   ][Info   ] Dial Hyper-V socket a5f8deb1-05c8-4df1-8eb0-5230b5727d4e:23a432c2-537a-4291-bcb5-d62504644739
[13:38:07.075][ProxyProcess   ][Info   ] http: panic serving //./pipe/docker_engine: runtime error: invalid memory address or nil pointer dereference
[13:38:07.081][ProxyProcess   ][Info   ] goroutine 62 [running]:
[13:38:07.084][ProxyProcess   ][Info   ] net/http.(*conn).serve.func1(0xc082143500)
[13:38:07.086][ProxyProcess   ][Info   ]    C:/go/src/net/http/server.go:1389 +0xc8
[13:38:07.089][ProxyProcess   ][Info   ] panic(0x8e40e0, 0xc082006060)
[13:38:07.092][ProxyProcess   ][Info   ]    C:/go/src/runtime/panic.go:443 +0x4f7
[13:38:07.095][ProxyProcess   ][Info   ] github.com/docker/pinata/v1/docker_proxy.(*inspectRewriter).Rewrite(0xc082104e20, 0x1aa4878, 0xc08210b640, 0x0, 0x0, 0x0)
[13:38:07.098][ProxyProcess   ][Info   ]    c:/gopath/src/github.com/docker/pinata/v1/docker_proxy/inspect.go:88 +0x5f0
[13:38:07.100][ProxyProcess   ][Info   ] github.com/docker/pinata/v1/docker_proxy.(*passthru).HandleHTTP(0xc082108a60, 0x1aa4348, 0xc0821121a0, 0xc08215c8c0, 0x0, 0x0)
[13:38:07.103][ProxyProcess   ][Info   ]    c:/gopath/src/github.com/docker/pinata/v1/docker_proxy/passthru.go:88 +0xb99
[13:38:07.105][ProxyProcess   ][Info   ] github.com/docker/pinata/v1/docker_proxy.addRoute.func1(0x1aa4348, 0xc0821121a0, 0xc08215c8c0)
[13:38:07.109][ProxyProcess   ][Info   ]    c:/gopath/src/github.com/docker/pinata/v1/docker_proxy/proxy.go:77 +0x6c
[13:38:07.112][ProxyProcess   ][Info   ] net/http.HandlerFunc.ServeHTTP(0xc082108a80, 0x1aa4348, 0xc0821121a0, 0xc08215c8c0)
[13:38:07.114][ProxyProcess   ][Info   ]    C:/go/src/net/http/server.go:1618 +0x41
[13:38:07.118][ProxyProcess   ][Info   ] github.com/docker/pinata/v1/vendor/github.com/gorilla/mux.(*Router).ServeHTTP(0xc082134000, 0x1aa4348, 0xc0821121a0, 0xc08215c8c0)
[13:38:07.120][ProxyProcess   ][Info   ]    c:/gopath/src/github.com/docker/pinata/v1/vendor/github.com/gorilla/mux/mux.go:107 +0x29e
[13:38:07.122][ProxyProcess   ][Info   ] net/http.serverHandler.ServeHTTP(0xc082142e80, 0x1aa4348, 0xc0821121a0, 0xc08215c8c0)
[13:38:07.125][ProxyProcess   ][Info   ]    C:/go/src/net/http/server.go:2081 +0x1a5
[13:38:07.128][ProxyProcess   ][Info   ] net/http.(*conn).serve(0xc082143500)
[13:38:07.130][ProxyProcess   ][Info   ]    C:/go/src/net/http/server.go:1472 +0xf35
[13:38:07.132][ProxyProcess   ][Info   ] created by net/http.(*Server).Serve
[13:38:07.135][ProxyProcess   ][Info   ]    C:/go/src/net/http/server.go:2137 +0x455

Docker version is 1.12.0-rc2-beta16 (build: 4760) 999af1e

Running Windows 10 Pro.

The problem started after today’s Docker update.

Steps to reproduce the behavior

  1. docker run hello-world
  2. docker inspect hello-world

(Per Rovegård) #2

I uploaded full diagnostics, got ID:

C2BB18E6-FE90-4D5C-8A72-D75B442DD9A8/2016-06-19_13-50-51


(Dvanderl) #3

Same issue. Running the same build. Just upgraded this morning.

Uploaded diagnostics, ID:

62807B52-682D-41AF-9FFC-0C052E687DE7/2016-06-19_16-44-19


(Per Rovegård) #4

Is there a way to downgrade? This is a showstopper for me right now.


(Rolf Neugebauer) #5

Thanks for the report and apologies for the regression. I’ve filed an internal issue (#4028) and we are looking into it
thanks’
Rolf


(Per Rovegård) #6

Thanks!

Just FYI: I opened a GitHub issue as well, because I didn’t know which was the best way to get attention on this.


(Andy Neff) #7

I have the same problem in 1.12.0-rc2 on windows

However, I found out that by specifying the --type argument, it still works (for both containers and images) Hope this helps someone.


(David Gageot) #8

Hi everyone, this should be fixed with today’s release