Ofelia interferes with other docker compose stacks (solution inside)

[Kitof]

Contribution guidelines

• [X] I've read the contribution guidelines and wholeheartedly agree

I've found a bug and checked that ...

• [X] ... I understand that not following the below instructions will result in immediate closure and/or deletion of my issue.
• [X] ... I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
• [X] ... I have understood that answers are voluntary and community-driven, and not commercial support.
• [X] ... I have verified that my issue has not been already answered in the past. I also checked previous issues.

Description

By default ofelia monitors labels for all docker containers. If other instances of ofelia exist on the system, they may interfere with each other, resulting in recurring duplicate tasks.

However, since the latest version of ofelia, a parameter allowing you to limit the scope of label monitoring has been implemented.

So it's only necessary to replace :

    command: daemon --docker

by

    command: daemon --docker -f label=com.docker.compose.project=${COMPOSE_PROJECT_NAME}

in docker-compose.yml

Logs:

scheduler.go:55 ▶ DEBUG Starting scheduler with 16 jobs

Steps to reproduce:

Have others ofelia containers outside mailcow stack
Have labels outside mailcow stack

Which branch are you using?

master

Which architecture are you using?

x86

Operating System:

Debian 6.1.69-1

Server/VM specifications:

8go, 4 core

Is Apparmor, SELinux or similar active?

no

Virtualization technology:

none

Docker version:

25.0.3

docker-compose version or docker compose version:

2.24.6

mailcow version:

2023-02

Reverse proxy:

Traefik

Logs of git diff:

None

Logs of iptables -L -vn:

Not needed

Logs of ip6tables -L -vn:

Not needed

Logs of iptables -L -vn -t nat:

Not needed

Logs of ip6tables -L -vn -t nat:

Not needed

DNS check:

Not needed

[Kitof]

Made a simple PR https://github.com/mailcow/mailcow-dockerized/pull/5776

[milkmaker]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.