dockerPolice

Members
  • Posts

    115
  • Joined

  • Last visited

Everything posted by dockerPolice

  1. If changes to the template are required, you should talk to LinuxServer on their discord about making those changes.
  2. dockerPolice

    Hotio v CA

    Welcome to my life... Fundamentally nothing (if anything) While slightly differing versions of the same app aren't a bad thing (backup versions etc), this is one of those apps where future versions being submitted to CA will probably be declined to avoid confusion and the same question. https://forums.unraid.net/topic/87144-ca-application-policies-notes/ This is one of the apps where the moderators of CA *may* remove without warning one of the scrutiny apps present within CA... In this particular case IF one of the versions gets removed it would either be self hosters or hotio
  3. https://pydio.com/en/features/why-migrating-pydio-8-cells
  4. Am I correct in assuming then that linuxserver/pydio is now deprecated (since it is Pydio-8 which Pydio is recommending to migrate to pydio-cells)?
  5. They're all from prior to his joining lsio, and since DigiKam had no direct replacement in another active repository, it stayed within Apps. Now it's officially deprecated, (along with JDownloader2 - as there's other replacements for that one also)
  6. Along with the repository that it's pulling from. Not to mention that the original displays Seems to me that the template should be updated
  7. Certainly appears to be as of a week ago. (https://blog.linuxserver.io/2020/08/21/introducing-swag/) I would expect that @aptalca will shortly adjust the Unraid template to reflect this change.
  8. While I usually do an annual / semi annual spanking of the template maintainers, a new check on all the templates is necessitating a whipping of the maintainers. There is obviously some confusion regarding the <WebUI> entry This entry can never directly reference a specific IP address. (http://192.5.0.1 is not acceptable as an entry) While you shouldn't ever directly reference a specific port, *technically* it is ok if the container does not run in bridge mode. All references to [PORT:xx] reference the container port. It does NOT reference the host port IE: Everything should be http://[IP]:[PORT:xx]/ where xx is the container port. This allows the user to change the ports as much as they want without having to switch to template authoring mode and advanced view in order to also change the WebUI entry. Keeping with the right format significantly lowers the support requests here on the forum. While the application feed is now going to do it's best to automatically adjust the WebUI entry to what it should be, all maintainers should update their templates accordingly. IMO, having 157 errors present in the appfeed (most of which are corrected by the feed itself) isn't really acceptable. (Also, the common mistake of creating a category out of thin air is so prevalent that it's not even counted any more. unRAID uses categories, not tagging.) Additionally, v1 templates have been deprecated now since 6.2.0. There are a few entries regarding non-existent webUI ports below where the maintainer has for some reason chosen to make a v2 template by hand by manually editing a previously existing v1 template and add in a few <Config> entries and not add in all of them that would technically be required. (eg: They have ports defined in the v1 section but not in the v2 section). While this does currently work, there is no guarantee that it will work in the future. The easiest way to create a template is by simply entering in the appropriate information into Add Template screen and hitting SAVE. 90% of the following errors (excluding the WebUI errors) would not exist if that happened. Aggie1999's Repository wbynum/qemubackup: No Icon specified within the application template Port referenced in webUI does not correspond with a container port defined.Port Referenced does not exist in Config alturismo's Repository dnsforge/xteve:latest: No Support Link Present Andrew207's Repository atunnecliffe/splunk: Hardcoded port found in webUI entry aptalca's Repository aptalca/docker-zoneminder: Fatal: No valid Overview Or Description present - Application dropped from CA automatically - Possibly far too many formatting tags present atribe's Repository atribe/apcupsd-influxdb-exporter: No Icon specified within the application template achumchal/plex_data_collector_for_influxdb: No Icon specified within the application template barrycarey/speedtest-for-influxdb-and-grafana: No Icon specified within the application template bashNinja's Repository bashninja/docker-pritunl: Port referenced in webUI does not correspond with a container port defined. Entry changed to https://[IP]:[PORT:443] Bender's Repository traefik:latest: Not a valid Registry entry set. Creating from Repository setting Hardcoded IP address for webUI. It should always be [IP] instead. Hardcoded port found in webUI entry boerderij/varken: Invalid WebUI acockburn/appdaemon: No Registry entry set. Created from Repository setting Hardcoded IP address for webUI. It should always be [IP] instead. Hardcoded port found in webUI entry Bungy's Repository sameersbn/gitlab: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80]/ jshridha/motioneye:latest: No category entry present Blacklisted: Obvious CA conversion templates are disallowed owncloud: No category entry present Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80]/ jshridha/rdiffweb: No Icon specified within the application template Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:8080] centurylink/watchtower: No category entry present No Icon specified within the application template CaptInsano's Repository captinsano/koel: No category entry present Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:8080]/ captinsano/legacyrutorrent: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80]/ captinsano/rutorrent: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80]/ cheesemarathon's Repository coderaiser/cloudcmd: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:8000] minio/minio: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:9000]/ chvb's Repository chvb/docker-apache-php: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80]/ chvb/docker-kerio-connect: Unknown category Network:Email clowrym's Repository hexparrot/mineos: No category entry present ninjaneer/plex-discord-bot: Unknown category Uncategorized: No Icon specified within the application template No Support Link Present cmer's Repository cmer/minio: Fatal: Multiple Repositories Found - Removing application from lists Conmyster's Repository zabbix/zabbix-agent:latest: Multiple Category tags present - using longest one CorneliousJD's Repository acockburn/appdaemon: No Registry entry set. Created from Repository setting d8ahazard's Repository digitalhigh/flextv: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80] digitalhigh/huedream: Not a valid Registry entry set. Creating from Repository setting Port referenced in webUI does not correspond with a container port defined.Port Referenced does not exist in Config d8sychain's Repository d8sychain/mediawiki: Port referenced in webUI does not correspond with a container port defined.Port Referenced does not exist in Config DavidSpek's Repository rocker/rstudio: No Support Link Present dee31797's Repository djaydev/motioneye: Unknown category Media: Unknown category Servers: dibbz' Repository quimnut/brewpi-wifi: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80]/ quimnut/cloud9ide: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:8080]/ gogs/gogs: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:3000]/ digiblur's Repository homeassistant/amd64-hassio-supervisor: Port referenced in webUI does not correspond with a container port defined.Port Referenced does not exist in Config adolfintel/speedtest: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80] raymondmm/tasmoadmin: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80]/ danmed/tasmobackupv1: Port referenced in webUI does not correspond with a container port defined.Port Referenced does not exist in Config iotreboot/tasui:latest: Port referenced in webUI does not correspond with a container port defined.Port Referenced does not exist in Config nico640/docker-unms: Port referenced in webUI does not correspond with a container port defined. Entry changed to https://[IP]:[PORT:443] docgyver's Repository https://raw.githubusercontent.com/docgyver/unraid-v6-plugins/master/denyhosts.plg: No Icon specified within the application template https://raw.githubusercontent.com/docgyver/unraid-v6-plugins/master/ssh.plg: No Icon specified within the application template ElectricBrainUK's Repository electricbrainuk/unraidapi: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80] eXisTa's Repository xirixiz/dsmr-reader-docker: Port referenced in webUI does not correspond with a container port defined.Port Referenced does not exist in Config fanningert's Repository guacamole/guacd: Unknown category Network:Mangament No Support Link Present frakman1's Repository gitlab/gitlab-runner: No category entry present Blacklisted: Obvious CA conversion templates are disallowed gfjardim's Repository needo/nzbdrone: Multiple Descriptions Found Fatal: No valid Overview Or Description present - Application dropped from CA automatically - Possibly far too many formatting tags present https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/plugins/statistics.sender.plg: No Support Link Present Grack's Repository gregyankovoy/chowdown: No category entry present gregyankovoy/goaccess: No category entry present gregyankovoy/lftp-mirror: No category entry present No Icon specified within the application template hernandito's Repository hernandito/hernando-apachephp-docker: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80]/ hernandito/docker-apache-php-adminer: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80]/ hernandito/docker-resourcespace: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80]/ ich777's Repository ich777/doh-client: No category entry present No Support Link Present ich777/doh-server: No category entry present ich777/jenkins: No category entry present ich777/mtaserver: Port referenced in webUI does not correspond with a container port defined.Port Referenced does not exist in Config ich777/online-check-pushover: No category entry present ich777/remmina: No category entry present ich777/stun-turn-server: No Support Link Present zabbix/zabbix-server-mysql: No category entry present zabbix/zabbix-web-nginx-mysql: No category entry present JBartlett's Repository jbartlett777/diskspeed: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:8888]/ JCloud's Repository quantumobject/docker-cacti: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80]/cacti analogic/poste.io: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80]/ jcreynolds' Repository jcreynolds/flextv: Unknown category Media: Unknown category Applications: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80] No Support Link Present jj9987's Repository janarj/cloudflare-ddns:1.1: No Icon specified within the application template No Support Link Present josywong's Repository ipfs/go-ipfs: No Icon specified within the application template angelics/unraid-docker-ipxe-buildweb: Unknown category Services: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80] angelics/unraid-docker-zelcore-wallet: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:5800] knex666's Repository knex666/mopidy:3-experimental: No Support Link Present nextcloud:latest: No Registry entry set. Created from Repository setting knex666/rssnotipy: No category entry present kevineye/snapcast: No category entry present No Support Link Present doudou34/tor-server: No Registry entry set. Created from Repository setting No Support Link Present Kru-X's Repository wekanteam/wekan: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:8080]/ wordpress: Port referenced in webUI does not correspond with a container port defined.Port Referenced does not exist in Config linuxserver's Repository linuxserver/codiad: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80]/ linuxserver/sickgear: No category entry present malvarez00's Repository gitlab/gitlab-ce: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80] No Support Link Present malvarez00/docker-unifi-video: Unknown category Media: Unknown category Servers: MarkusMcNugen's Repository markusmcnugen/sftp:latest: No Registry entry set. Created from Repository setting MrChunky's Repository storjlabs/storagenode:beta: No Support Link Present Mudislander's Repository mudislander/fogproject: Invalid WebUI No Support Link Present bl0m1/xtevedocker: No category entry present CPU pinning removed from template No Icon specified within the application template p.wrangles' Repository wranglatang/bluelinky: No Icon specified within the application template rix's Repository rix1337/docker-myjd-api: No category entry present rix1337/docker-ripper: Multiple Category tags present - using longest one rix1337/docker-verarbeitung: No category entry present runraid's Repository ronnieroller/ddns: No Support Link Present kthulu120/liquid_dl: Port referenced in webUI does not correspond with a container port defined.Port Referenced does not exist in Config No Support Link Present kmb32123/youtube-dl-server: No Support Link Present sdesbure's Repository sdesbure/T411Torznab: Fatal: Invalid repository found. Only lowercase is allowed seim's Repository seafileltd/seafile: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80] Selfhosters Unraid Discord Repository nmtan/chevereto: Port referenced in webUI does not correspond with a container port defined.Port Referenced does not exist in Config anojht/invoiceninja: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80]/ sharelatex/sharelatex: Port referenced in webUI does not correspond with a container port defined.Port Referenced does not exist in Config syncarr/syncarr: No Icon specified within the application template Siwat2545's Repository siwatinc/adguard_home: Unknown category DNS: No Registry entry set. Created from Repository setting Port referenced in webUI does not correspond with a container port defined.Port Referenced does not exist in Config siwatinc/esphomeyaml: No Registry entry set. Created from Repository setting machinebox/facebox: Port referenced in webUI does not correspond with a container port defined.Port Referenced does not exist in Config siwatinc/home_assistant_control_panel_unraid_ab: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80] siwatinc/nginx-pagespeed: No Registry entry set. Created from Repository setting Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80]/ onlyoffice/communityserver: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80] onlyoffice/documentserver: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80] siwatinc/phlex: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80] siwatinc/ubuntu-playground: Not a valid Registry entry set. Creating from Repository setting smdion's beta Repository smdion/docker-keybox: No Icon specified within the application template smdion's Repository smdion/docker-h5ai: Invalid WebUI snoopy86's Repository snoopy86/emoncms-docker: Port referenced in webUI does not correspond with a container port defined. Entry changed to http://[IP]:[PORT:80]/ stuckless' Repository stuckless/crushftp: Unknown category Productivity:Tools Multiple Icons found thetarkus' Repository thetarkus/funkwhale: Port referenced in webUI does not correspond with a container port defined.Port Referenced does not exist in Config No Support Link Present thomast_88's Repository gitlab/gitlab-runner: No category entry present Blacklisted: Obvious CA conversion templates are disallowed ulisses1478's Repository ulisses1478/docker-android: No category entry present No Registry entry set. Created from Repository setting No Support Link Present ulisses1478/bitcoinwallet-gui: No Support Link Present ulisses1478/mongo-express: No Registry entry set. Created from Repository setting No Support Link Present phpmyadmin/phpmyadmin: No Support Link Present ulisses1478/shinobi: No Support Link Present ulisses1478/zcashwallet: No Support Link Present zyphermonkey's Repository zyphermonkey/splunk: No Support Link Present _DC_'s Repository jc5x/firefly-iii:latest: No category entry present Port referenced in webUI does not correspond with a container port defined.Port Referenced does not exist in Config No Support Link Present
  9. Because They're now being removed from CA and a notice will go out via FCP
  10. Removed due to zero support, no updates in 3 years+, fundamentally very limited drivers included that would work on an ancient printer that isn't commonly available nowadays and far far better alternatives to what was available within CA by enabling Docker Hub Searches within CA and then searching for CUPS. IE: Not much point in keeping an app within CA that for the most part doesn't work as advertised. https://forums.unraid.net/topic/37549-support-gfjardims-docker-repository/page/14/?tab=comments#comment-827842 Review the last page or 2 of the linked content to see some of the examples of alternatives that actually work.
  11. And, unlike the other F@H app, it won't automatically join Team unRaid (quite understandable). The team # if you care is 227802
  12. For the next little while, the moderators of CA will try and keep those two applications on the main landing page of CA (New Apps) to gain some further exposure
  13. Both (Security as a category being added was listed as a separate entity). So far as the security enhancement was concerned, it was previously possible for a malicious template author (ie: an asshole) to craft a template for a docker container that would either Arbitrarily execute code directly on the server simply by loading the template or Completely hide a path mapping from the user even if template authoring mode was enabled in Settings - Docker This code change simply brought dockerMan up to speed with what Community Applications already does for those 1 or 2 users that still add in repositories via the Template Repositories tab (ugh) instead of utilizing the Apps Tab. CA goes medieval in it's enforcement of any violation of security
  14. There is no requirement that the support thread be hosted here and cannot be pointed at the app's own thread. Probably the majority of questions regarding any given app aren't actually applicable to the unRaid installation, but are rather application specific questions. On the face of it based upon the title of this thread (Slow Uploads), I'd call that app specific. But that is rather immaterial as it is semantics. Personally, I'd love for every single app to have a dedicated support thread per app. In practice, its not going to happen. Where and how the support threads are hosted and what I am able to discern about any given support level does however highly impact any moderation that may (or may not) one day be required on.
  15. I think that I'm going to remove CUPS from CA. It's one of those abandoned applications. While it does somewhat work, it's not particularly populated with printer drivers that are more commonly used today, and there are many more choices for CUPS available @ dockerHub that are kept more up to date and have a better selection of drivers within them.
  16. My understanding is that the author(s) of organizr themselves have deprecated the original and it is now advised to switch to v2 of the application. Hence the linuxserver app of organizr is now deprecated. There is the official version of organizr-v2 available within the Apps Tab. And no, I have no idea about the procedure (if any) involved in switching over your existing data to the updated app. This does not mean that you HAVE to switch. Even if you don't switch, this app will still be available within the apps tab if you have previously installed it and need to reinstall it via the previous apps section NEW installations of this app are blocked by default by the Apps Tab.
  17. Because based upon support requests here in the forum and activity of the OP of the thread, you can reasonably expect no support via the official channels here in this forum regarding any unRaid specific issues. The support on the whole for emby via their own forum / discord / whatnot may be amazing, but my recommendations are based upon support you can get here. And it's purely a personal opinion...
  18. At the heart of it, there is no fundamental difference. ie: Emby is emby is emby. Difference lies in some subtleties. and as @jonathanm stated support regarding hardware transcoding. lsio issues updates for the containers if the base OS has an update (security patch), or emby get's updated pretty much the minute that it happens. binhex issues updates for the containers whenever the arch upstream repository for emby gets updated (which will lag behind the actual updates) emby issues updates for the containers whenever they release a new stable version (ie: 2 months ago) or if you installed the beta version 2 days ago. No clue about their security policies. If you're going to be using the nVidia plugin, you're definitely going to want to run the lsio version, as it'll at least be tested with the nvidia hardware transcoding. Everything else probably only supports intel GPU transcoding if you passthrough the appropriate commands and have a compatible (ie: older iGPU) All else being equal and if you're not doing hardware transcoding, you're looking at either lsio or @binhex ie: Long story short, you're not the first to ask this type of question (although usually it's about Plex), CA has this policy
  19. I was actually concerned that br0 wasn't available by default, but since it is this isn't really that big a deal
  20. Does this have to run on it's own IP??? Would it be better to have the default for the template set to be bridge with the appropriate ports mapped through?
  21. Stop one at a time and see when the traffic to "weird sites" stops.
  22. Nothing says you can't run ps3netsrv. Only that mccloud/ps3netsrv now will install cryptomining software. AFAIK there are other ps3netsrv's available on dockerHub that will work fine for you (enable dockerHub searches within the apps tab)
  23. mccloud/ps3netsrv and mccloud/ps3netsrv:latest will have a warning go out via FCP regarding its infection with crypto mining software. However, it should be noted that this apparent breach of mccloud's GitHub repo happened in and around 10 hours ago today. PS3Netsrv has NOT been available within Community Applications for a while now, as the tags utilized by the templates within CA were no longer available to be downloaded. At that point, all of the users of the previous tags for ps3netsrv (:alpine, :debian, etc) were also notified via Fix Common Problems that the containers were blacklisted because of the tags no longer being available. At no point has the :latest tag with regards to ps3netsrv from McCloud ever been available within CA as the template maintainer never updated the templates to reflect the new tags. (The :latest tag is the one with the crypto mining software) While this breach doesn't affect any applications that are available within Community Applications (Apps), the moderators of CA take very seriously the security and integrity of the applications present within.
  24. FWIW, the app from linux server is set up correctly... A PR has been issued against the template to fix this. If not accepted within a reasonable time (since the template maintainer has not been online for months), then this particular version will be removed from CA in favour of the one from linuxserver.