Dockerfile: Include an entrypoint script for ejabberdctl #4071
Conversation
This file contains 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
This serves as a placeholder, so that custom images can use an actual entrypoint script, e.g. for initiating ejabberd clusters.
|
Deleted the branch by accident, will open again if necessary. |
|
I think, I don't. For my particular case, I discovered two options to override |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi @badlop
The entrypoint script serves as a placeholder, so that admins can replace it with an actual entrypoint script, e.g. for initiating ejabberd clusters, through mounting it to the path
/usr/local/bin/run.sh.This PR does not change anything of the existing functions of the image.
Motivation:
I would like to use the image as basis for the helm-chart with these scripts and not rely on a custom image in the end.