Hi all,

I default to using linuxserver.io containers, I just so happened to notice that in Community Apps when I search for qBittorrent, it does not have the 'installed' flag as my other containers do.

Is there a broken linkage that I can fix?

Thanks!

Did you rename it from the default? If so that'll "break the link".

On 5/1/2026 at 8:39 AM, Kilrah said:

Did you rename it from the default? If so that'll "break the link".

Are you referring to the name of the container? This spot:

I can't image putting in a custom name, will break a link to the repository? This broken update link is happening on custom names and on default names. I would only position that if the name is changed, the 'update' check should point and reference the repository and not search for whatever name I call it. And if changing the name breaks something, then why are we allowed to change it?

I can manually click Check for Updates, and they will find updates appropriately.

Changing the name will only make the cosmetic "installed" tag not show up, everything else including updates still works normally.

Edited May 16May 16 by Kilrah

On 5/16/2026 at 7:46 AM, Kilrah said:

Changing the name will only make the cosmetic "installed" tag not show up, everything else including updates still works normally.

So how does the CA reference/compare the docker containers? Purely the the default CA name <> the name you designate?

This is above my knowledge, so I'm not judging it. But I would assume there could be a way to identify which docker container is being used. Similar to the updates.

5 hours ago, shelfactor said:

But I would assume there could be a way to identify which docker container is being used.

Could be the image repo, but that doesn't work since there can be multiple templates in CA referencing the same repo, if it used that it'd then show "installed" on a template that is not the one you actually installed.

So the name is the most "unique" way to identify an installed template, and since 1) most people would not change it unless they really needed to (e.g. to install multiple instances) and 2) it literally does nothing but put the cosmetic "installed" flag and has no functional effect it's probably the most appropriate.

Edited May 18May 18 by Kilrah

@Kilrah Thanks for the info. I understand what you are saying, and agree that it's cosmetic. It just seems like something that could be fixed (again, past my knowledge).