Docker page loading indicator spinning

I too have noticed slow loading on the the docker page.

Hmm, docker container list is working fine for me on rc1.  

 

@smdion can you define slow loading with a time/duration?

Clear your browser cache, see if that makes a difference.

 

20 minutes ago, bonienl said:

Clear your browser cache, see if that makes a difference.

 

I tried both private browsing and clearing browser cache, but the Docker page still shows a the spinning loading icon and doesn't load my container list. I'll try a reboot to see what happens.

Looks like you tried it Mar 21 @ 4:24 (then dashboard @ 4:45, update @ 4:51)  Did you try reloading the page (after waiting a couple of minutes)

 

Was anything really going insane on the server at the time (eg: Plex going full tilt transcoding a stream and using all available resources?)

I see the same problem as well.

Using Firefox  59.0.1, worked fine after first page view, but now it just shows the loading indicator.. tried clearing session cookies with no luck. Cleared all site cookies.. no luck.

Tried another browser, Chrome 64.0.3282.186, same issue.

 

Looking at chrome devtools, "DockerUpdate.php" has the warning:

Failed to load resource: the server responded with a status of 504 (Gateway Time-out)

 

:/var/log/nginx# cat error.log 
2018/03/22 20:49:33 [error] 6918#6918: *101348 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.2, server: , request: "POST /plugins/dynamix.docker.manager/include/DockerUpdate.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.0.11", referrer: "http://192.168.0.11/Docker"
2018/03/22 20:52:48 [error] 6918#6918: *101348 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.2, server: , request: "GET /plugins/dynamix.docker.manager/include/DockerUpdate.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.0.11"
2018/03/22 20:53:43 [error] 6918#6918: *101789 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.2, server: , request: "POST /plugins/community.applications/include/exec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.0.11", referrer: "http://192.168.0.11/Apps"

 

I have 3 dockers.. kodi-headless, netdata, and gitlab-ce. GitLab-CE looks to be a memory hog and caused the box to run out of ram and that is what I saw yesterday. I've now removed gitlab-ce and will monitor to see if the issue returns.

Edited March 23, 2018 by zoggy

15 hours ago, Squid said:

Looks like you tried it Mar 21 @ 4:24 (then dashboard @ 4:45, update @ 4:51)  Did you try reloading the page (after waiting a couple of minutes)

 

Was anything really going insane on the server at the time (eg: Plex going full tilt transcoding a stream and using all available resources?)

I did try to reload the page multiple times even after leaving it for more than an hour. Nothing out of the ordinary was using a large amount of resources.

 

I did reboot the server and was able to access the Docker page and see my containers listed one time. After that though I was again unable to access the container listing and only saw the spinning icon. I'm going to try to remove some docker containers to see if that helps.

I think @bonienl has been making some strides in determining what the underlying issue is.  Docker subsystem seems to be the common denominator on these issues.

Please re-test with -rc2.

May I ask everybody who had the Docker tab hanging to execute the below command (just copy + paste) and see if this succeeds.

docker inspect --format='{{.State.Running}}#{{range $p,$c := .HostConfig.PortBindings}}{{$p}}:{{(index $c 0).HostPort}}|{{end}}#{{range $p,$c := .Config.ExposedPorts}}{{$p}}|{{end}}#{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}#{{range $c := .HostConfig.Binds}}{{$c}}|{{end}}' $(docker ps -a --format='{{.Names}}')

Thanks

18 hours ago, bonienl said:

May I ask everybody who had the Docker tab hanging to execute the below command (just copy + paste) and see if this succeeds.

docker inspect --format='{{.State.Running}}#{{range $p,$c := .HostConfig.PortBindings}}{{$p}}:{{(index $c 0).HostPort}}|{{end}}#{{range $p,$c := .Config.ExposedPorts}}{{$p}}|{{end}}#{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}#{{range $c := .HostConfig.Binds}}{{$c}}|{{end}}' $(docker ps -a --format='{{.Names}}')

Thanks

Hi All, the issue is still occurring for me with -rc2. After the upgrade and reboot, I was able to access the Docker page and update a few containers. Then I would come back later to the Docker page and only see the spinning icon.

 

@bonienl - I ran the above command, but it looks like it just hangs or is waiting for the command to complete.

 

Let me know if there's anything further I can help to test.

Also just to point out, I do have 1 container that I can't seem to stop using the command line:

CONTAINER ID        IMAGE                                COMMAND                  CREATED             STATUS                  PORTS                                                                                                                NAMES
a9da4ab188c2        appcelerator/telegraf:telegraf-1.0   "/bin/sh -c /run.sh"     8 months ago        Up 14 hours (healthy)                                                                                                                        untelegraf

I've tried docker rm -f, docker stop, docker kill but they all seem to hang when trying to stop/remove the container.

Try to stop the containers, the command below attempts to stop all running containers.

docker stop $(docker ps --format='{{.Names}}')

Let me know if some containers can't be stopped and which one(s).

 

Our posts crossed

Edited March 25, 2018 by bonienl

2 minutes ago, bonienl said:

Try to stop the containers, the command below attempts to stop all running containers.

docker stop $(docker ps --format='{{.Names}}')

Let me know if some containers can't be stopped and which one(s).

Yup, the only one that doesn't stop successfully is:

CONTAINER ID        IMAGE                                COMMAND                CREATED             STATUS                  PORTS               NAMES
a9da4ab188c2        appcelerator/telegraf:telegraf-1.0   "/bin/sh -c /run.sh"   8 months ago        Up 14 hours (healthy)                       untelegraf

 

Is there anything interesting in /var/log/docker.log (might be a big file)?

 

You can also get the logs of a container

docker logs untelegraf

 

Edited March 25, 2018 by bonienl

There are some reports of people with similar issue and not being able to stop a container. Apparently a recurring issue since the introduction of 'containerd' and still present in version 17.12.1-ce. Some people downgraded to version 12.09 as a workaround.

 

Here is a link

Edited March 25, 2018 by bonienl

Sorry @bonienl, I ended up rebooting the server, accessing the docker page immediately after reboot and removed the untelegraf container. Ever since then the Docker page seems to work properly. I'll let you know if I notice anything further.

 

FYI, in order to reboot previously I had to kill the following processes in order for the array to stop completely:

/usr/bin/dockerd -p /var/run/dockerd.pid --storage-driver=btrfs --storage-driver=btrfs
docker-containerd --config /var/run/docker/containerd/containerd.toml

 

Just providing an update here.

 

Removal of my problematic container, untelegraf, solved this issue for me. I'm still not sure why this particular container caused the issue of listing the docker containers on the Docker page and also prevented stopping the docker service upon reboot/shutdown of the Array.

 

Hope this helps provide some insight.

Thanks for the update.

 

I have installed "untelegraf" as well, but it is running fine no hang ups since installing yesterday.

 

There are reports on the Docker forum about more people not able to stop containers. It could well be a bug in docker. To be continued.

 

Marking this one closed for now.

Changed Status to Closed