pixogen

Pro tip: Read the first post and completely remove the old version & reinstall. Simply upgrading did not work. It's nice to have a working version again

I have exactly the same issue. Deluge is removing the write permission from user group on any folder it gets access. So nobody can write/delete the files via SMB. Haven´t changed anything inside the docker, see my config in attachment. Ditto. I kept running new permissions until I realized that it was this deluge docker container that would create new folders with the 0755 permissions instead of 0777. Help!

I was just going to ask about this because I went to recover a file I accidentally deleted and noticed the recycle bin was empty. I guess that's what I get for running a beta version of unRAID

Same issue, just slightly different "otherpid": /usr/sbin/cron: can't lock /var/run/crond.pid, otherpid may be 102: Resource temporarily unavailable /usr/sbin/cron: can't lock /var/run/crond.pid, otherpid may be 102: Resource temporarily unavailable /usr/sbin/cron: can't lock /var/run/crond.pid, otherpid may be 102: Resource temporarily unavailable /usr/sbin/cron: can't lock /var/run/crond.pid, otherpid may be 102: Resource temporarily unavailable /usr/sbin/cron: can't lock /var/run/crond.pid, otherpid may be 102: Resource temporarily unavailable /usr/sbin/cron: can't lock /var/run/crond.pid, otherpid may be 102: Resource temporarily unavailable /usr/sbin/cron: can't lock /var/run/crond.pid, otherpid may be 102: Resource temporarily unavailable /usr/sbin/cron: can't lock /var/run/crond.pid, otherpid may be 102: Resource temporarily unavailable Is there a fix for this?

This plugin keeps saying "Update Ready" on the docker tab, but when I install the update and then re-check for updates, this container says there's another update ready. I'm running 6.2-beta23. The container appears to work fine otherwise. Pulling image: binhex/arch-deluge:latest IMAGE ID [latest]: Pulling from binhex/arch-deluge. Status: Image is up to date for binhex/arch-deluge:latest TOTAL DATA PULLED: 0 B Stopping container: binhex-deluge Successfully stopped container 'binhex-deluge' Removing container: binhex-deluge Successfully removed container 'binhex-deluge' Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="binhex-deluge" --net="bridge" -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -p 8112:8112/tcp -p 58846:58846/tcp -p 58946:58946/tcp -p 58946:58946/udp -v "/mnt/cache/appdata/deluge":"/config":rw -v "/mnt/user/":"/data":rw binhex/arch-deluge 66b33ccea11e42467acf6ff3c7b06f115b3afd2637a7170a93776dea4fe22e69 The command finished successfully!

Running 6.2.0-beta23 and updating to the latest version of this plugin, it no longer starts with the following error: usermod: no changes [info] Env var PUID defined as 99 [info] Env var PGID defined as 100 [info] Permissions already set for /config chown: cannot access '/var/lib/plex': No such file or directory I SSH'd into my server and confirmed that '/var/lib/plex' doesn't exist, but why is it looking for that folder? Edit: Removed the container, deleted the /plex folder from appdata & reinstalled it - same error. Edit2: I removed it again & installed the linuxserver plex docker and it works.

Any chance of creating an Apache-mySQL-PHP5 container or an Apache-mySQL-PHP7 container?