Hi friends....I installed a Qbittorrent container about 3 years ago from the app store. I recently went in to change some paths and find the container listed as a 3rd party container and I do not have the option to click the name and edit its settings. Not sure why it is 3rd party now. I have only installed containers from the app store and never used docker compose. I am wondering why it is now a 3rd party app and how can I change the setting variables for the container. 

 

 

 

 

Just to follow up to this.....I realized the container has not been updated since 2021. I installed the current binhex version and got it running so I will be deleting the outdated version of qbittorent.

it shows 3rd party if you use docker run comand from the terminal.

it was not creted by the unriad doker gui nor compose file...

I have never used docker compose with unraid. I couldn't tell you how to do it. When I first installed the container over 3 years ago it was a native unraid app and I used the usual template. I can only assume that the app not being updated in 3 years has something to do with it being changed.

all I know is that order for it to say 3rd party... you had to have ran a termanl comand to launch a docker run...



netprobe is a docker compose example and what it would show... all others are unraid template. Note the docker test... see the terminal windows....

This is why it says 3rd party... you may have pulled the docker run at one time removed the image and ran it in terminal... 
 

I know this is an old topic, but found this on search...  Just noticed this when upgrading to 7.0 and realized the 3rd Party listing is also added for those containers that were built based on old Apps entries that were removed and/or replaced.  A good example is the Official Plex image.  In Apps the official one is listed as "Plex-Media-Server".   When I originally installed Plex years ago from the official repo, it was from Apps just listed as "Plex" and pointing to here for "more info:" https://hub.docker.com/r/plexinc/pms-docker/ .  Now that I upgraded to 7.0 I can no longer update my customized folder and env settings in the GUI even in Advanced Mode because of the 3rd Party tagging, even though it was perfectly able to be edited in 6.12.14.  I'd call that a pretty serious regression.

12 hours ago, jedimstr said:

I know this is an old topic, but found this on search...  Just noticed this when upgrading to 7.0 and realized the 3rd Party listing is also added for those containers that were built based on old Apps entries that were removed and/or replaced.  A good example is the Official Plex image.  In Apps the official one is listed as "Plex-Media-Server".   When I originally installed Plex years ago from the official repo, it was from Apps just listed as "Plex" and pointing to here for "more info:" https://hub.docker.com/r/plexinc/pms-docker/ .  Now that I upgraded to 7.0 I can no longer update my customized folder and env settings in the GUI even in Advanced Mode because of the 3rd Party tagging, even though it was perfectly able to be edited in 6.12.14.  I'd call that a pretty serious regression.

I can't help you, but I figured I would let you know that I never resolved this. I wound up removing the container and installing a different one. 

Same problem here for ALL my containers

LE: Even the delay for autostart can't be changed

 

Edited January 11, 20251 yr by topunraid
New info

32 minutes ago, topunraid said:

Same problem here for ALL my containers

LE: Even the delay for autostart can't be changed

 

 

 

Wow! Hopefully you can get this resolved! That would suck.

I updated from 6.9.2 which was pretty old to begin with, maybe that could be the issue if nobody else has problems from newer versions

That suggests the templates are missing from your flash drive. If you have them in a backup you should be able to put them back. 

I do have a backup of them but they are not missing in my opinion, since Backup/Restore Appdata can see the delay I set in 6.9.2.

 

Or is the folder structure wrong ? I alsoo see dockerMan/templates, maybe I need to move them to there under a new folder structure, can I have some examples from you ? Thanks!

 

If you are seeing this for containers created via Dockerman/CA that have not been updated or recreated in a long time try recreating the container. The simplest way is to edit the container make a minor change like adding and removing a character in the name and then clicking the apply button. Dockerman now uses a container label which it applies to all the containers it creates to indicate that they are managed by Dockerman and not a third party tool. If your containers have not been recreated in a while they will be missing this label.

3 minutes ago, primeval_god said:

If you are seeing this for containers created via Dockerman/CA that have not been updated or recreated in a long time try recreating the container. The simplest way is to edit the container make a minor change like adding and removing a character in the name and then clicking the apply button. Dockerman now uses a container label which it applies to all the containers it creates to indicate that they are managed by Dockerman and not a third party tool. If your containers have not been recreated in a while they will be missing this label.

Those containers with "3rd party" labeling even though they're from App and not 3rd party, just old, also don't have an Edit option in the rightclick menu.  So how do you do this without deleting the container and starting those from scratch?

I had some containers that needed an update and they now appear ok, I don't see any way of editing the 3rd party from GUI.

9 minutes ago, jedimstr said:

Those containers with "3rd party" labeling even though they're from App and not 3rd party, just old, also don't have an Edit option in the rightclick menu.  So how do you do this without deleting the container and starting those from scratch?

If there is not an option to edit them, and no option to update or force update them, then you would need to remove the container and recreate it from its template. I would check that the template exists before removing the container by clicking "Add Container" on the docker screen and looking for the template in the dropdown under user templates. If the template is there it should have all your settings still intact. You should be able to remove the container and then recreate it via "Add Container" and selecting the template.

Edited January 11, 20251 yr by primeval_god

I also just upgraded from 6.9.x to 7.0 (I know big jump) and am having the same issue. My template files are fine so that's not the issue.

 

As @primeval_god says I've found that I can either delete and recreate the container, or I can update the container (for those that have an update available) and that resolves the issue.

 

I notice that when the containers get recreated they get given some labels like `net.unraid.docker.managed=dockerman`. I wonder if these are missing on my old containers and that's what is causing the issue.

On 1/11/2025 at 6:11 PM, jedimstr said:

Those containers with "3rd party" labeling even though they're from App and not 3rd party, just old, also don't have an Edit option in the rightclick menu.  So how do you do this without deleting the container and starting those from scratch?

Go to your Docker page, at the bottom click Add Container, open the drop down and look if you got <CONTAINERNAME> under [User-Tempates], select it and you should see all your custom made settings (double check if everything is correct and really the template that you customized for your needs).

 

I'm not 100% sure if you can just click Apply but if you can't it is safe to remove the container and re-deploy it with the steps from above.

This will add the necessary labels to the container.

 

It is really interesting that for some users these labels are not in place?

These images are up do date and not deprecated correct?

What repository is listed in the template?

 

Containers actually don't need to be in the CA App, they just need to have those labels in which up to date images should have since Unraid adds them automatically.

31 minutes ago, jacobtomlinson said:

I notice that when the containers get recreated they get given some labels like `net.unraid.docker.managed=dockerman`. I wonder if these are missing on my old containers and that's what is causing the issue.

Yes i believe this is the issue (I actually mentioned it on another persons post about the same issue). This label is added by dockerman when it creates the container (at least in recent versions). The absence of that label tells dockerman that the container is "Third Party", which mean not managed by Dockerman. Since you updated from 6.9.x your container were likely deployed before dockerman was adding these labels. This could also occur for people who updated from a more recent version if they have a container that has not been redeployed or updated in a very long time (sounds strange but it happens).

Edited January 13, 20251 yr by primeval_god

I guess what peps are asking then is how to fix this...

If i'm understanding this correctly, then...

as in my composes files I add the label that is missing:

 

The recommend way to service future updates....
You will need to record any edits you made over the years and take pictures to verify the data latter.

Essentially:
you will need to remove the docker (DO NOT DELETE THE IMAGE!) and remove the template.
As it appears, the issue lies in the unriad template missing data at creation...

Then go to the CA and install that application. edit/Point and make any edits you may have done over the years per previous docer info and pictures.
as if you maintain the same pathing, setting and variables you had you will have 0 data loss and bring it back into the current docker standards...

So the reason for this is that the templates on your flash drive need extra data when loaded... Or that unraids docker system has a new label that was introduced in later updates... as they are not getting the data due to something missing but that data is not int eh template itself... 

Also, its not easy to edit theses templates manuly via terminal... in unraid, but they are located at

/boot/config/plugins/dockerMan

but this issue isn't with the tempaltes file themselves... as the docker man code gets added later with CA/Docker integrations... From my testing...

 

##############

 

So ? in theory then.. .Might be a temp fix...

 

Passing as a extra parameter

-l net.unraid.docker.managed: 'dockerman'

 

 

But I think this will still break with updates and others without a redownload and install from lattest CA due to template evolutions.... (unraid would still complain about a 3rd party container and not update....

 

as 3rd party has same issues with compose of being reported, their is a update but having to remove the image and re pull to get unraid to say its up to date...

Worth a try...
 

21 minutes ago, bmartino1 said:

Essentially:
you will need to remove the docker (DO NOT DELETE THE IMAGE!) and remove the template.
As it appears, the issue lies in the unriad template missing data at creation...

You should not need to remove the template as far as i understand. Just recreate the container using the existing template. Dockerman should apply the correct label on container creation or update. As far as i know its not part of the template just a flag dockerman adds on creation. The issue seems to be that people have containers that have not been recreated or updated since before upgrading.

Edited January 13, 20251 yr by primeval_god

My containers were almost up to day, so the issue comes from 6.9.2 (in my case) which apparently doesn't add that flag to the containers so when upgrading to 7.0.0 they will appear as 3rd Party. For me, the best "solution" is to wait for an update since most of my containers are bi-weekly updated.

Just now, topunraid said:

My containers were almost up to day, so the issue comes from 6.9.2 (in my case) which apparently doesn't add that flag to the containers so when upgrading to 7.0.0 they will appear as 3rd Party. For me, the best "solution" is to wait for an update since most of my containers are bi-weekly updated.

Recreating a container is easy enough though. Just click the edit button, make and remove a small change (I add and remove a space at the end of the name) so that Dockerman thinks there is something to update, then click apply. Dockerman removes and recreates the container and everything should be correct.

A 3rd Party container cannot be edited

Just now, topunraid said:

A 3rd Party container cannot be edited

Ok that makes sense. Then you really would have to remove and re-add from the saved template.