portainer: ERROR: Unable to retrieve Images

BUG REPORT INFORMATION

Description

Clicking on Images, and receive error message: Unable to retrieve images.

Technical details:

Portainer version: 1.13.5 (also happened on develop branch)
Target Docker version (the host/cluster you manage): 1.11.2
Platform (windows/linux): QNAP QTS 4.3.3 Build 0238 (Kernel 4.2.8)
Command used to start Portainer (docker run -p 9000:9000 portainer/portainer):
docker run -d -p 9000:9000 --name=portainer
–net=host --restart=on-failure
-v /share/Docker_configs/portainer:/data
-v /var/run/docker.sock:/var/run/docker.sock portainer/portainer
Target Swarm version (if applicable):
Browser: Safari 10.1.1

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 7
Comments: 38 (17 by maintainers)

Commits related to this issue

feat(app): add tooltip component [EE-2047] (#1033) — committed to portainer/portainer by chiptus 3 years ago

Most upvoted comments

This has been fixed you can try it in portainer/portainer:develop

Le mar. 25 juil. 2017 à 20:41, divisuals notifications@github.com a écrit :

I encountered the same error with my local Docker environment (VirtualBox on Mac OSX 10.12.6 using docker v1.11.2/ API version 1.23).

df does give a 404 - see attached.

[image: portainer_error] https://user-images.githubusercontent.com/3194722/28588041-f81309d6-712d-11e7-9a78-bd8ccf07b930.png

The total image count is accurate and other resources are also pulling-up. Is this expected?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/portainer/portainer/issues/1033#issuecomment-317830982, or mute the thread https://github.com/notifications/unsubscribe-auth/AFOyBZjaCPRPtjLJS_hIrsDVUo8D4nJwks5sRjbNgaJpZM4OXuO5 .

– Anthony Lapenna https://deviantony.github.io

deviantony on Jul 25, 2017

Never mind… I had my browser pointing at my TEST NAS instance (was connecting by ip), but my SSH was pointing at my prod nas. Rechecked with browser pointing to RIGHT NAS and now all appears to be working properly. <sigh>

MwC-Trexx on Jul 24, 2017

MwC-Trexx on Jul 22, 2017

There is a 404 for GET system/df which is actually a system%2Fdf that is called while the images page is loaded. It seems that a direct call to portainer:9000 node is forgiving this encoded url, whereas Apache’s ProxyPass directive gives 404. I can fix the GET call with my “browser’s developer add-on” and resend it, which results in a OK 200.

The dataUsage call has been added to app/rest/docker/system.js in 1.13.5 by #1009 thus downgrading to 1.13.4 circumvents the issue for now. Some url rewrite magic with the proxying Apache might be a workaround as well.

h0l0gram on Jul 15, 2017