kamhighway

@theone Thanks for this info. I thought this setting might have been the reason that my virtualbox vms do not survive a reboot. Guess it is something else. Update: I'm not sure what fixed my problem, but virtualbox vms are now saving their state and surviving a reboot just fine.

@dmacias, Nice tool. Working fine on a supermicro X9SCM motherboard. I sometimes use supermicro's IPMI tool to restart the computer and watch the bootup process through their iKVM tools. It's nice to be able to read the sensors right from Unraid. Thanks again.

In the "Mount and Startup" options, what is the field labeled "VirtualBox symbolic link (part of install package) - Change from default /boot/custom/vbox:" supposed to point to? I have my virtualbox vms at /mnt/cache/appdata/virtualbox. Is this where I should be pointing the Virtualbox symbolic link?

Thank you Squid

Here's a screenshot of the network settings page.

/config/plugins/community.applications does not exist on the flash drive. Diagnostics: https://www.dropbox.com/s/w71i4izqzh7vjic/tower-diagnostics-20150221-0741.zip?dl=0

DNS settings are identical to my primary unraid server. I reentered the info anyway and rebooted. Still getting same error messages.

Can't install community applications plugin on fresh Unraid 6.1.6 install. Here is the log: plugin: installing: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg plugin: downloading https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg plugin: downloading: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg ... done Warning: simplexml_load_file(): /tmp/plugins/community.applications.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): /tmp/plugins/community.applications.plg:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 plugin: xml parse error Seems like something is missing?

@CHBMB TRURL and BRiT have said that we should be posting about this topic in the support forums for the containers causing the problem. I think we would all be happy to do that if we could figure out which containers are causing the problem. BRiT's suggestion that we start with a clean slate and enable one container at a time until we find the problem will not identify the problem containers unless the trigger for the problem occurs during the 12 hour period you are testing the container. Just because a container runs fine for 12 hours does not mean there is no problem. I think the approach you are taking is a better one. If we could isolate which container has ballooned in size we can then take the discussion to the right support thread and focus on figuring out how to properly configure the containers to avoid the problem.

Yes I have read the replies. You made this recommendation in the past and several of us have tried it and reported that it did not help. Since you repeated your recommendation again, I thought maybe there's a way to use cadvisor that I have not figured out so I thought I'd ask you.

@gfjardim First, I would like to thank you for the work you've put into making and supporting this docker. Following the advice contained in this 30 page thread, I was able to get owncloud up and running with needo/mariadb. However, in order to make owncloud accessible from the internet, I had to edit config.php inside the running container at /var/www/owncloud/config. I was wondering whether my edits to config.php will survive the next time you update the container? Seems to me that they will be overwritten. If so, do you recommend mapping /var/www/owncloud/config to somewhere on the cache drive? Update: I see that config.php was copied to the directory that I mapped for owncloud's data. I guess I should have edited that copy instead of editing the version in the container.

@CHBMB, I tried using cadvisor to figure out which container was growing. cadvisor always reported all of my containers remaining the same size even as the utilization of docker.img grew by GBs/day. If there is a way to use cadvisor to figure out which container is the problem, please tell us how to use it.

@brit Do you have a list of dockers that have passed your tests?

@brit Did you come across any dockers that you stopped using after this process?

@ikosa, How about a way for users to give a thumbs up to a docker so we can all see which dockers are working well for the biggest number of users?

@Brit, You may be correct that the problem is container specific and not a problem with Unraid. However, telling us to post in the support forum for each container is not helpful if we cannot tell which container is causing the problem. @Rara1234, I would start by disabling the last docker you added and seeing if that solves the problem. However, I should tell you that I went down this road and it just so happened that while I had the last-in docker disabled, my daughter went to a girl scouts camping trip so she wasn't doing any transcoding. Consequently, my docker utilization did not grow and the problem appeared to be caused by the docker I disabled. Send me on wild goose chase for a couple of days.

@rara1234, There is more than one reason that can cause the docker utilization rate to skyrocket. In my case, it was needo's Plex docker that by default performs transcoding inside the docker container. I had been using this docker for months without issue. However, after i bought my daughter an ipad, I found that I had to increase my docker image size every few days. At the time, I did not make the connection between the two events and like you I posted in this forum. The people on this forum helped me narrow down the list of suspect dockers. The big breakthrough for me was when I noticed my daughter was spending a lot of time watching her shows on her ipad via plex. Her ipad is the only device that required plex to transcode. This made sense to me because I had been running fine for months before seeing the utilization of docker.img jump by gigabytes some days and then flatline for days. For me, this pattern ruled out an out of control log file as the problem. I found a post JonP wrote a post explaining how to make plex transcode in either ram or on the cache drive. This is what solved my problem. Others have said their problem was due dockers which auto update themselves sometimes leaving dangling containers. And, in at least one case, it seemed that it was an out of control log file. Of the dockers you listed, I would check out emby to see where it performs transcoding. You may have to figure out how to map emby's transcode directory to either ram or your cache drive. As for the other dockers you've installed, we don't overlap on any. However, I am using Binhex's Couchpotato and Sonarr with great success. I've been through several version updates with Binhex's dockers without seeing my docker.img utilization balloon. Binhex posted in this thread some of the things he builds into his dockers to avoid this problem. I wish all docker authors would take as much care as he does.

I am in the same boat as death.hilarious, thaddeussmith, and wizard84. I can install it, get it running, and start a bash session. However, if I enter a beet command that requires a response, beet ignores keyboard presses so I can't respond.

@sparklyballs Thank you for the lesson in how to update the docker. It did indeed download a new version, even though the UR docker page said I was on the most recent version. Also, it looks like the change you made fixed the problem that prevented me from using this docker. I'm going to play with this over the next few days to see how the app works. This could be a great solution for my family. Thank you for your work.

@sparklyballs, I went to the dockers tab and pressed the button to check for updates. No update was found for photoshow. How do I get the version with the update you made today?

@sparklyballs: Thanks sparklyballs. Did you update the one in your repository, or the one in linuxserver.io, or both?

Thanks for reporting your findings. I'm still looking for an app that will let my relatives place comments on pictures. PhotoShow would have fit the bill, except for that bug.

@Squid There are two that we overlap on: Needo-MariaDB, and Needo-Plex. In diagnosing my issues, I've had Needo-MariaDB turned off for days when the utilization of docker.img increased by gigabytes a day, so I'm pretty sure Needo-MariaDB was not causing my problem. Needo-Plex however was the docker that seems to account for most of my problem. The issue is that in order to make Plex transcode outside of docker.img, you have to change setting that is not on the docker setup screen. See my previous post for details. There may be other dockers that have similar application settings that cannot be configured in the docker setup screen. And, there may be some apps that generate huge log files. Maybe we should always map the log files for any docker app to the cache drive?

The ones where we overlap are binhex-sonarr, and binhex-couchpotato. I too have not had any problems with these two. The one docker that I found an issue with was needo-plex, but I think the same issue would arise with any plex docker. The issue with Plex is that in order to transcode outside of the docker.img, you have to change a setting in Plex that is NOT visible in the docker setup screen. Mapping /tmp in the plex docker to /tmp does not solve the problem. LMJ42 mentions this in his post above: 1) Add a volume mapping for /transcode to /tmp (or a location on your cache drive) 2) In Plex, go to Settings -> Server -> Transcoder. Hit Show Advanced. In the "Transcoder temporary directory" put "/transcode" After changing this setting in Plex, my docker utilization has stopped rising by gigabytes a day. It still rises a little each day, but I no longer have to keep increasing the size of docker.img every few days. It may be that there are other dockers that have a similar setting in the application that cannot be changed in the docker setup screen. If so, it would be a good idea to make a list of such applications and let others know where the relevant settings are in each app. Brit's list of dockers may be particularly useful. Since he doesn't share our problem, apparently all of his dockers can be configured correctly from the docker settings screens. This is useful information for the rest of us to know.

@Brit I posted in here to see if anyone else has the same problem so we can collaborate to fix it. If you don't have the problem, that's great. But telling those of us that do have the problem that its our problem and we have to fix it ourselves is not helpful. What would be helpful is if you could tell us which dockers you are using that have not given you any problems so we can possibly eliminate them from the list of potentially misbehaving dockers.