Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

7 Neutral

About dockerPolice

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

536 profile views
  1. Never could figure out why you've never wanted it published in CA...
  2. Changed via moderation. If/when the template gets updated, I'll reverse my changes
  3. Is all that's wrong is the container port needs to be 22 not 9022?
  4. You would probably be better off switching to OpenVPN-AS published by linuxserver instead.
  5. Yes. Linuxserver.io is rather hypocritical by having their docker compose file directly reference elasticsearch in it, and yet not publishing a template for unRaid.😡
  6. Since PlexInc never seemed to me to be super receptive on templates, I've unilaterally changed the URL for Plex to point to the root of their support thread. You'll be able to hit it via the Apps Tabs, Installed Apps. @Squid will have to do something about the fact that now the URL listed in the Docker / Dashboard pages are incorrect
  7. Since it's not explicitly mentioned, is it recommended for all users of the old app to now migrate to the new one? Is the old app now deprecated?
  8. It sure would be nice if someday someone would actually look at why it doesn't work for certain users (not by any means ALL users) and let limetech know the circumstances.
  9. Ok I see now that they are the same repo, just different tags will rectify
  10. Seems to me that your container is the better choice. Especially considering the first item, and the fact that you were last on 5 minutes ago I try and look for abandoned projects, hence my suggestion to get in touch with Squid
  11. Fair to say then that the existing container does not work with updated unRaid versions? Why not just PM @Squid and create a new repository for CA. Then we can deprecate fannigert's and replace it with yours.
  12. "atribe's Repository": { "atribe/apcupsd-influxdb-exporter": [ "Fatal: No valid Overview Or Description present - Application dropped from CA automatically - Possibly far too many formatting tags present", "No Icon specified within the application template" ],
  13. Reviewed by the community. BUT, all applications present within Apps are either Open Source (therefore reviewed by many users across the spectrum of OS systems) or are Closed Source but from trusted sources (ie: Crashplan, Plex, etc). No Closed source application that is not from a trusted source will be accepted for inclusion to Apps.
  14. Aren't you being rather hypocritical then because the docker compose file listed for diskover does have elasticsearch: container_name: elasticsearch image: docker.elastic.co/elasticsearch/elasticsearch:5.6.9 volumes: - ${DOCKER_HOME}/elasticsearch/data:/usr/share/elasticsearch/data environment: - bootstrap.memory_lock=true - "ES_JAVA_OPTS=-Xms2048m -Xmx2048m" ulimits: memlock: soft: -1 hard: -1 redis: container_name: redis image: redis:alpine volumes: - ${HOME}/docker/redis:/data Shouldn't the references to elasticsearch and redis be removed from the yaml for the same reasoning you just gave for not having a template? Isn't fundamentally a yaml a template?
  15. So you published a template that has a prerequisite for which you don't have a template!?!