Jump to content
  • Docker templates are no longer grouped by repo


    ezhik
    • Annoyance

    I have multiple docker repo's added and all of the docker template are grouped within the same 'Default Templates' group. This changed in 6.6.0/6.6.1.

     

    I did not find a setting to change the display settings for the templates.

     

    Can we either change it back or have a setting to group templates based on repo?

     

    Cheers!




    User Feedback

    Recommended Comments

    Why is this urgent? Looks more an annoyance.

    Does your server crash or has data loss?

    Edited by bonienl
    • Upvote 1
    Link to comment
    8 hours ago, bonienl said:

    Why is this urgent? Looks more an annoyance.

    Does your server crash or has data loss?

    I've changed it from urgent to annoyance, but It is a SIGNIFICANT one. I have to go through template ONE BY ONE to see what is what. I don't normally complain and try to be supportive, but I had to setup a few servers this weekend and this has caused me a great amount of pain and time wasted.

     

    And don't take this personally, I still heavily support unRAID :)

    Link to comment
    19 minutes ago, ezhik said:

    have to go through template ONE BY ONE to see what is what.

    Alternative though is to simply forget about using repositories altogether and use Apps for everything instead.  It DOES support "private" repositories which you may have added

    Edited by Squid
    Link to comment
    4 minutes ago, Squid said:

    Alternative though is to simply forget about using repositories altogether and use Apps for everything instead.  It DOES support "private" repositories which you may have added

    Can you elaborate please on the use of 'Apps' in this case or link me to a guide so I can educate myself? Thanks.

    Link to comment

    If you're using "private" repositories (ie: ones that you've created yourself and not shared, or other ones that aren't available in CA), then create a path /config/plugins/community.applications/private/nameOfRepository on the flash drive and toss all of the applicable xml files in there.

     

    IE: I've tried to make CA such that anything you can do with the Repositories section in the docker tab you can do with CA.

    Edited by Squid
    Link to comment
    2 hours ago, Squid said:

    If you're using "private" repositories (ie: ones that you've created yourself and not shared, or other ones that aren't available in CA), then create a path /config/plugins/community.applications/private/nameOfRepository on the flash drive and toss all of the applicable xml files in there.

     

    IE: I've tried to make CA such that anything you can do with the Repositories section in the docker tab you can do with CA.

     

    Yeah I am using the following repo's:

     

    https://github.com/limetech/docker-templates
    https://github.com/binhex/docker-templates
    https://github.com/linuxserver/docker-templates
    https://github.com/linuxserver/beta-templates

     

    Your reference to CA is Community Applications? Just want to be clear on the terminology here.

     

    Edited by ezhik
    Link to comment
    1 hour ago, ezhik said:

    Your reference to CA is Community Applications?

    Yes.  Apps tab

     

    1 hour ago, ezhik said:

    All stock repositories.  While it doesn't change anything about the issue / bug, most people don't even bother adding any repositories, and just to CA for everything  Much easier to handle things.

    • Upvote 1
    Link to comment

    It is highly recommended to use "Community Applications" as the way to install docker containers.

    The repository system is likely to be deprecated in future releases.

    Link to comment
    8 hours ago, bonienl said:

    It is highly recommended to use "Community Applications" as the way to install docker containers.

    The repository system is likely to be deprecated in future releases.

    Oh... Well hello there news. :)

    Link to comment
    20 minutes ago, ezhik said:

    What you are saying, the proper route to go in this case is to install this plugin:

     

    Yup.  IMHO not just in this case, but in all cases. 

    20 minutes ago, ezhik said:

    Which is maintained by @Squid ?

     

    Yes, along with @dockerPolice and @pluginCop

     

    20 minutes ago, ezhik said:

    Or is this going to become part of unRAID 'core' in the near future?

    Unknown.  But, it is directly linked to on LT's website as the "unRaid Appstore"

    Edited by Squid
    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...