Skip to content

Container not watched, if it has a profile? #1416

@ChekeredList71

Description

@ChekeredList71

Good afternoon!

I don't really understand this behaviour, as I see it as "could be intentional", but the docs don't mention this.

In my case, I have WG in a profile, along with diun:

wireguard:
    image: lscr.io/linuxserver/wireguard:latest
    container_name: wireguard
       ...
    profiles:
      - critical
    labels:
      - "diun.enable=true"
    restart: unless-stopped

The diun instance picks up all my containers with diun.enable=true, that are not in a profile.

Wireguard isn't picked up, until I remove it from critical profile.

Is this intended behaviour?

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions