jamescarlos

I like how my Unraid server is an all in one machine handling multiple tasks using containers. I would like to see an integration using docker-compose so that I can reliably back up my docker compose files and configuration using version control (git).

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.

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

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

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.

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.

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 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.

Thanks! Upgraded from 6.5.0 without issue. The Docker page loaded initially and I was able to update all my outdated docker containers. I just came back to the Docker page and now am experiencing the loading indicator again which just keeps spinning. Any clue?

For completeness, here's what I did: - Stopped the array - Reassigned the failed disk to "No Device" - Started the array with "Maintenance Mode" checked - Stopped the array again - Removed failed drive and hot-swapped it into a different empty drive bay - Reassigned the disk to the failed drive and started the array to rebuild After 14 hours, the rebuild completed with 0 errors. We'll see if this continues without error.

Awesome, thanks johnnie.black. I'll give that a try.

Hi Guys, I received a dreaded drive failure notification this morning on my unRAID server. The drive that failed is a Western Digital Red 5TB. I'm hoping some folks here can help me determine the reason for the failure and some next steps. The problem drive used to be my parity disk for a couple of years without issue, so I'm assuming it's just the backplane slot that is the culprit. Attached is the diagnostics .zip. The server hasn't been rebooted or stopped until I figure out the best way to go forward. Thanks in advance! tower-diagnostics-20170224-0907.zip

This is great information Viaduct. I'm going to look it over soon and see how I can contribute.

Thanks jamescarlos ! As for the icon size, I thought I had _specifically_ solved that issue Is it possible that your browser is reading the old copy of the image (it was that big before). Can you try a hard refresh (Cmd + R on a Mac, I think it's Ctrl + R on Windows), and let me know if that solves it ? Indeed, it was Chrome that was caching the previous icon. Looks splendid now!