January 27, 201511 yr Effects 6b12 and possibly earlier beta's. I dabbled in docker a few weeks back and decided I could live with my current set-up since I run so few plugins. APCUPSD, and Plex and I know APCUPSD is going to native to unRAID in future releases so even fewer plugins soon. Anyway... When messing with docker I created a 5gb image on my cache drive. After messing with docker I deleted all my containers and removed the docker image via telnet. The docker tab showed no container and the process stopped. I assumed this meant I was done with docker and had freed up 5gb of free space on my cache for use again. Issue: Three days ago I rebooted after making some changes to the unRAID. Today I randomly clicked on the docker tab (why would I look at it when I don't believe I have any dockers running and no docker image installed) and much to my surprise unRAID had decided to remake the docker image (5gb in the location I last specified) and start docker, when it booted (looked in logs and found that info) using the last known information (same settings from when I dabbled in docker) Did I miss a way to turn this off? Should this be the default behavior? If an image exists I think you should load it and start docker, but if it doesn't exist I don't think unRAID should create one and start docker using the last known settings. Also I think docker clean up should be a bit better, when you decide you don't want to use docker anymore it should give you the option to remove the image in the webgui (maybe it does and I missed it), having to go into telnet / ssh seems bad.
January 27, 201511 yr Effects 6b12 and possibly earlier beta's. I dabbled in docker a few weeks back and decided I could live with my current set-up since I run so few plugins. APCUPSD, and Plex and I know APCUPSD is going to native to unRAID in future releases so even fewer plugins soon. Anyway... When messing with docker I created a 5gb image on my cache drive. After messing with docker I deleted all my containers and removed the docker image via telnet. The docker tab showed no container and the process stopped. I assumed this meant I was done with docker and had freed up 5gb of free space on my cache for use again. Issue: Three days ago I rebooted after making some changes to the unRAID. Today I randomly clicked on the docker tab (why would I look at it when I don't believe I have any dockers running and no docker image installed) and much to my surprise unRAID had decided to remake the docker image (5gb in the location I last specified) and start docker, when it booted (looked in logs and found that info) using the last known information (same settings from when I dabbled in docker) Did I miss a way to turn this off? Should this be the default behavior? If an image exists I think you should load it and start docker, but if it doesn't exist I don't think unRAID should create one and start docker using the last known settings. Also I think docker clean up should be a bit better, when you decide you don't want to use docker anymore it should give you the option to remove the image in the webgui (maybe it does and I missed it), having to go into telnet / ssh seems bad. Definite changes that we are looking to make in a future release of Docker Man. I know exactly what you're talking about and agree that the tools in the webGui need a bit more refinement. Stay tuned.
February 19, 201511 yr Author Effects 6b12 and possibly earlier beta's. I dabbled in docker a few weeks back and decided I could live with my current set-up since I run so few plugins. APCUPSD, and Plex and I know APCUPSD is going to native to unRAID in future releases so even fewer plugins soon. Anyway... When messing with docker I created a 5gb image on my cache drive. After messing with docker I deleted all my containers and removed the docker image via telnet. The docker tab showed no container and the process stopped. I assumed this meant I was done with docker and had freed up 5gb of free space on my cache for use again. Issue: Three days ago I rebooted after making some changes to the unRAID. Today I randomly clicked on the docker tab (why would I look at it when I don't believe I have any dockers running and no docker image installed) and much to my surprise unRAID had decided to remake the docker image (5gb in the location I last specified) and start docker, when it booted (looked in logs and found that info) using the last known information (same settings from when I dabbled in docker) Did I miss a way to turn this off? Should this be the default behavior? If an image exists I think you should load it and start docker, but if it doesn't exist I don't think unRAID should create one and start docker using the last known settings. Also I think docker clean up should be a bit better, when you decide you don't want to use docker anymore it should give you the option to remove the image in the webgui (maybe it does and I missed it), having to go into telnet / ssh seems bad. Definite changes that we are looking to make in a future release of Docker Man. I know exactly what you're talking about and agree that the tools in the webGui need a bit more refinement. Stay tuned. Update: This issue still exists in 6b13; I have to manually delete my docker image after every reboot. This isn't terrible as one shouldn't be rebooting often, but it's also not ideal.
April 4, 201511 yr Hi all, I just updated to unraid 6 beta 13. But now i have a problem with SNAP I dont get any view under the SNAP plugin under settings. The whole plugin page is white and i dont see an error.
April 4, 201511 yr Hi all, I just updated to unraid 6 beta 13. But now i have a problem with SNAP I dont get any view under the SNAP plugin under settings. The whole plugin page is white and i dont see an error. If you are going to upgrade why not go to beta 14b (the current version with the next one will imminent). I would suggest removing the SNAP plugin, upgrading to 14b, and then reinstalling the SNAP plugin.
Archived
This topic is now archived and is closed to further replies.