Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ofelia interferes with other docker compose stacks (solution inside) #5775

Closed
5 tasks done
Kitof opened this issue Mar 4, 2024 · 2 comments
Closed
5 tasks done

Ofelia interferes with other docker compose stacks (solution inside) #5775

Kitof opened this issue Mar 4, 2024 · 2 comments
Labels
bug stale Please update the issue with current status, unclear if it's still open/needed.

Comments

@Kitof
Copy link

Kitof commented Mar 4, 2024

Contribution guidelines

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

  • ... I understand that not following the below instructions will result in immediate closure and/or deletion of my issue.
  • ... I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
  • ... I have understood that answers are voluntary and community-driven, and not commercial support.
  • ... 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 Kitof added the bug label Mar 4, 2024
Kitof added a commit to Kitof/mailcow-dockerized that referenced this issue Mar 5, 2024
@Kitof
Copy link
Author

Kitof commented Mar 5, 2024

Made a simple PR #5776

@milkmaker
Copy link
Collaborator

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

@milkmaker milkmaker added the stale Please update the issue with current status, unclear if it's still open/needed. label May 4, 2024
@milkmaker milkmaker closed this as not planned Won't fix, can't repro, duplicate, stale May 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug stale Please update the issue with current status, unclear if it's still open/needed.
Projects
None yet
Development

No branches or pull requests

2 participants