mst3kroqs

Hi - I'm using the ddns-updater container from repository "qmcgaw/ddns-updater" via the Community Applications installer. Just forced an update today to make sure I had the latest before posting. This thing works gangbusters however I noticed a couple of things: 1) Docker container icon seems broken (throws an error in the Unraid syslog every time Docker management page loads) 2) The Console command from the icon menu doesn't produce a shell window. I have "Console shell command" set to the default: "Shell" value. I *think* the error I'm seeing in the very brief window that pops up says: OCI runtime exec fails: unable to start container process: "sh" executable file not found in $PATH: unknown Thoughts? Thanks!

Thanks for confirming! Might be a thing to add to the wiki ... (add to my to-do list).

First the Background: I'm running 6.11.5. Recently, I finally got around to adding a cache drive to my array. While in the process of migrating data for the 'Prefer' shares (appdata/domains/system) to the Cache drive, all was going smoothly. Mover had completed moving all of the files in appdata, domains and system/libvirt/libvirt.img (VM Manager was disabled), but since Docker was running at the time, /system/docker/docker.img was still open, and so was not copied. I went to Settings, and disabled Docker. Rather than copying the docker.img vDisk file to the Cache, I decided this would be a good opportunity to delete and recreate it. I'm following the guide here: I was following the guide to do this: https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file I disabled Docker, clicked the 'delete vDisk' checkbox and Delete button), and then proceeded to re-enable Docker. This is Where It Goes Horribly Wrong: Things proceeded as expected *however*, when I began re-adding my Containers, I discovered that the Docker Custom Network 'proxynet' which I had previously created to support my swag/reverse proxy configuration was no longer available as an option in the relevant template configs. I stopped Docker again, and I double-checked the Docker Settings, and sure enough 'Preserve User Defined Networks' was still set to Yes, but the 'proxynet' network did not appear in the list of networks at the bottom. So - I checked the contents of the relevant user-defined container templates on the flash in the /config/plugins/dockerMan/templates-user/ directory, and found that they still contained the <Network>proxynet</Network> definition, however if I try to load the template, the Network Type dropdown displays 'None'. Naturally, I do not click 'Apply', and abandon trying to reload the container. It's as if Docker no longer 'knows' about this user-defined Custom Network, and therefore to confirm this, I open a shell and run 'docker network ls', and see: NETWORK ID NAME DRIVER SCOPE 6765c3ac724b bridge bridge local a68bcda794f0 eth0 macvlan local 0ea8978fcdb1 host host local c985aee79164 none null local .. so - no 'proxynet'. These look like the 'default' networks to me ... What am I missing? Is the definition of the Docker Custom Networks not persistent when re-creating Docker.img? Do I have to re-execute 'docker network create proxynet' to re-create this custom network before reloading containers? If they are, where is this configuration file stored (can't find any reference to 'proxynet' in any of the files in the /config/plugins/dockerMan tree ... I'm trying to determine if I inadvertently deleted it, and could possibly be restored from one of several backups I may have. Thanks in advance! -m

I'm getting the same error as McNutty195. I followed the link and learned that as of 2/2022, Google shut down the OOB-method authentication "to make users more secure", and that programmatic changes to OAUTH authentication code would be required to continue to access the API. Bottom line: And I'd be very happy to be corrected, but I don't believe this handy little tool will work any more. Edit: Confirmed: https://github.com/agusalex/grive2Docker/commit/9594b663de439ef1c72dea6496189dcb2a1457e9

Hmmmmm - I took the array home and started it in my home office, and it came up just fine. I'll let you know if I can repeat the problem.

No - Internet connectivity fine, but good thought!

Running unRAID 6.3.5 on a lobotomized Aspire Easystore AH340. I have Settings -> Disk Settings -> Enable auto start: set to "Yes", but the array will not start after reboot. I currently have a trial key installed, but am hesitant to purchase a functional key if I'm dealing with some sort of hardware incompatibility. The array status is: "Stopped. Configuration valid" .. and if I manually start the array, all is well. Working as designed? If not, what could inhibit auto-start when this setting is set to "Yes"? I've checked the logs and nothing looks awry ... Thanks!

Running unraid v6.3.5, and serverlayout plugin v2017.03.03. Running the plugin results in: Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 126 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 126 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 126 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 In addition to this, seeing this in the unraid system log: Jul 9 19:13:57 hydra rc.diskinfo[7805]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 684 Jul 9 19:13:57 hydra rc.diskinfo[7805]: SIGHUP received, forcing refresh of disks info. Tried assigning disks to slots on the Data tab, but the plugin will not Save Data. Let me know if there's anything else I can provide you to assist.

Thanks - I think I was in denial. What this meant was that I had to go into my existing Sonarr database and edit the path for every TV series, in order to avoid having to rebuild the entire thing from scratch, and lose all my watch/monitor status flags. Sigh. -- and then I found this --- https://forums.sonarr.tv/t/change-root-folder-for-all-series-solved/2419 Double sigh. Moving on!

I just completed my upgrade from v5.05 to 6.3.5. All went pretty smoothly, until I tried to get the Sonarr docker to work. I was previously using Phaze's plugin for v5, but was looking forward to the docker functionality. My config directory is on an SSD which I'm mounting to /mnt/disks/ssd using the Unassigned Devices plugin by dlandon. This is a holdover from how I had it setup with the plugin, so I wasn't always spinning up my SATA drives. That's where SABnzbd lives too (I did successfully install the SABnzbd linuxserver's docker successfully). At any rate - my problem is that Sonarrr is unable to access the TV share. Oddly enough, when configuring the template, I can browse to where it is: /mnt/user/TV-Series/, but when the docker starts, and I access Sonarr, it complains about not being able to find the TV root directory. OK - so I try to Add an Existing Series, but when I try to browse the filesystem, I can see /mnt, but nothing under that. It seems like it might be a permissions issue, but I've checked, and the share directory "TV-Series" is 777 and owned by nobody.users, which matches the UID and GID of the docker. I've attached my template config - any help you can provide would be appreciated. Thanks!