Question regarding the wud.tag.include label

[Minstrel27]

I installed WUD a month or so ago and I'm having problems trying to configure it. I have built most of my containers with a specific version pinned and would like to be notified when there is a new tag available. My problem is that the program lists tags which are not wanted.

As an example, below is an excerpt of the WUD display.

In this case, PLEX is showing an update to available tag 168. However, I have the "wud.tag.include" label set to (I believe) only display SEMVAR tags. Below is the contents of the YAML file.

pms-docker:
  image: linuxserver/plex:1.41.3
  container_name: plex
  restart: unless-stopped
  environment:
    - PUID=1000
    - PGID=1000
  labels:
    - wud.tag.include=^\d+\.\d+\.\d+$$
  ports:
    - 32400:32400
  volumes:
    - /etc/localtime:/etc/localtime:ro
    - /mnt/NASData/AppsConfig/Plex/Config:/config
    - /mnt/NASData/Media/Concerts:/media/Concerts
    - /mnt/NASData/Media/TV:/media/TV
    - /mnt/NASData/Media/Music:/media/Music
    - /mnt/NASData/Media/Movies:/media/Movies
networks: {}`

I have the same issue with about a dozen containers. I have this label set for most of my containers, but it only seems to work about half the time. I'm obviously missing something, but I can't figure out what the problem is.

What am I doing wrong?

[Neurology0443]

Not sure here but I'm trying to give you some help !

Change your image link from

image: linuxserver/plex:1.41.3

To

image: lscr.io/linuxserver/plex:1.41.3

Did you also correctly configured WUD to access the linux server container registry?

---

Edit: I tried with your docker compose file and it seems to work on my end so maybe your WUD is wrongly configured here's an abstract of mine maybe this can be helpful !

    environment:
      - WUD_WATCHER_LOCAL_SOCKET=/run/docker.sock
      #Local watcher check  every day at 1am
      - WUD_WATCHER_LOCAL_CRON=0 1 * * *

      #Github username and token to connect to linux server container registry
      - WUD_REGISTRY_LSCR_USERNAME=your-username
      - WUD_REGISTRY_LSCR_TOKEN=your-token

Edit2: tried to break my own WUD container to reproduce the bug and commenting all registries but I'm not able to reproduce this behavior... :/// This could be a NAS networking issue, because on my bare bone server, your compose works as expected... but that's as far as I can help out here (not much sorry ;x thought that was an easy one...)

[Minstrel27]

Thanks for your help. I had initially set my image paths for all the linuxserver containers to be "lscr.io/linuxserver" but changed them because that wasn't working. In most cases, the pull command shown in each docker page excludes the "iscr.io".

However, I hadn't added the registry username and token as shown above. I've dont that now and we'll see if that helps. One question regarding that, in your example above, you list WUD_REGISTRY_LSCR_{USERNAME} as the value to use, however WUD shows the value as WUD_REGISTRY_LSCR_{REGISTRY_NAME}_{USERNAME}. Is the registry name required? I'll try both and see, but just curious.

Thanks

[vnghia]

For qbittorrent, you can see this issue #498. I think the same situation applied for other containers as well :/