Open
Conversation
added 3 commits
July 27, 2022 09:20
* Added icinga2.conf include parameter to the init script, so that custom configs will be included * Updated documentation with podman informations
I created new variables in the head of compose file to make the container name accessable and reused the variable to create the correct container names.
added 3 commits
July 27, 2022 14:52
…problem is, if grep do not found somethin, the grep command return a bad return code
…ys critical because of the container infrastructure
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
To use the docker-compose file for podman, it needs some modifications.
The following modifications are done:
init-icinga2.shscript. In the past, the custom configuration files inicinga2.conf.dwere not included into icinga2