Jump to content

dockerPolice

Members
  • Posts

    115
  • Joined

  • Last visited

Posts posted by dockerPolice

  1. In an ongoing effort to ensure that only supported and working apps are present within Community Applications, all applications within this repository have now been marked as being deprecated.  If the author / maintainer of this repository feels that this is in error, then they may contact the maintainers / moderators of CA for this to be rectified.

     

    Note that this move only affects new installations of the applicable applications.  Users already having one or more of the affected applications installed will still be able to re-install them via CA's Previous Apps feature without issue.  Should a user wish to install any of these applications without having previously installed them, then they may always enable "Show Deprecated Applications" within CA's settings.

  2. In an ongoing effort to ensure that only supported and working apps are present within Community Applications, all applications within this repository have now been marked as being deprecated.  If the author / maintainer of this repository feels that this is in error, then they may contact the maintainers / moderators of CA for this to be rectified.

     

    Note that this move only affects new installations of the applicable applications.  Users already having one or more of the affected applications installed will still be able to re-install them via CA's Previous Apps feature without issue.  Should a user wish to install any of these applications without having previously installed them, then they may always enable "Show Deprecated Applications" within CA's settings.

  3. In an ongoing effort to ensure that only supported and working apps are present within Community Applications, all applications within this repository have now been marked as being deprecated.  If the author / maintainer of this repository feels that this is in error, then they may contact the maintainers / moderators of CA for this to be rectified.

     

    Note that this move only affects new installations of the applicable applications.  Users already having one or more of the affected applications installed will still be able to re-install them via CA's Previous Apps feature without issue.  Should a user wish to install any of these applications without having previously installed them, then they may always enable "Show Deprecated Applications" within CA's settings.

     

  4. 11 hours ago, shaunmccloud said:

    At any rate, the issue is the template is wrong and needs to be fixed.  Pull request is still outstanding.

    Is all that's wrong is the container port needs to be 22 not 9022?

  5. 7 hours ago, Hammerfest said:

    This came about because I wanted to install diskover, sadly, it requires elasticsearch

    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. 1 minute ago, CHBMB said:

    it was the issue when certain containers don't work through FUSE,

    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.

  8. 1 hour ago, wgstarks said:

    FCP is generating an erroneous report regarding Now Showing V2 docker-

     

    SafariScreenSnapz155.thumb.jpg.d26c9e406708ff5655d6fceaabd02b86.jpg

     

    Now Showing v1 was deprecated, not v2. Not sure if this is an error in a template by @ninthwalker or an error with FCP? This just started for me when I installed RC3 but I believe I saw a report in the docker's support thread about someone getting the same error in RC2.

     

    brunnhilde-diagnostics-20190209-1844.zip

    Ok  I see now that they are the same repo, just different tags   will rectify

  9. 35 minutes ago, dee31797 said:

    he hasn't visited the forum while logged in since June 3, 2018.

     

    6 minutes ago, dee31797 said:

    it being out of date.

    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

  10. 36 minutes ago, atribe said:

    Thought ya'll might be interested in a new docker app I added to community apps under the name apcupsd-influxdb-exporter.

    https://hub.docker.com/r/atribe/apcupsd-influxdb-exporter 

    This is a docker wrapper around a python script that gets metrics out of apcupsd and puts them in influxdb.

    I just barely uploaded the xml to github, so I'm not sure how long that process takes for it to show up. but I've been using it for a few days and it works great.

        "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"
            ],

     

  11. 1 hour ago, WhackyHack said:

    2) Are these plugins reviewed in anyway by Lime-Tech?

    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.

  12. On 11/28/2018 at 2:18 PM, saarg said:

    That is not going to happen I'm afraid. We only do templates for our own containers. 

    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?

  13. 25 minutes ago, cTurtle98 said:

    I believe the client needs updating because it isn't able to process core_a7 work units:

    That's a shame.  Probably best course of action though is to deprecate this application (it isn't even the 64 bit executable, so much slower than it should be) and hope to hell that @CHBMB et al feel generous one day and pop out a replacement over their morning coffee one day and help the world one day become a better place.

×
×
  • Create New...