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

FeatureRequest: Can diun if it has an update target container function use docker labels? #1

Closed
Leopere opened this issue Jun 10, 2019 · 3 comments

Comments

@Leopere
Copy link

Leopere commented Jun 10, 2019

With a number of other things like Watchtower and Ouroboros you can establish container labels these labels can present triggers to other docker controlling and monitoring systems.

The thing I would love to see is for Diun to look for labels and just automatically detect the container's source and run checks against the upstream repository.

One such example is in the ouroboros documentation where the label determines to the Ouroboros appliance if the container should be handled by Ouroboros.

In this case, you could have a few labels I'm sure.

@crazy-max
Copy link
Owner

Hi @Leopere,

Perhaps I misunderstood your request, but I would like to point out that unlike other tools like WatchTower, Diun is not intended to update containers but only to send notifications when an image is updated on a registry.

On the other hand, I have planned in my TODO list to check images running via the Docker daemon. We could potentially use labels to filter those we want to analyze.

@Leopere
Copy link
Author

Leopere commented Jun 10, 2019 via email

@Leopere
Copy link
Author

Leopere commented Jun 10, 2019

Closed in lieu of the creation of #3

@Leopere Leopere closed this as completed Jun 10, 2019
moqmar added a commit to moqmar/diun that referenced this issue Oct 12, 2019
This can probably be improved a lot (e.g. what to do with undefined environment variables, how to treat escaping of variables, adding conditional clauses, and so on), but by then it would probably be wise to just use a prebuilt config parser with environment support.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants