-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Modifying the docker container to have two processes: ui and background tasks #127223
Closed
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
stevedodson
added a commit
to stevedodson/kibana-2
that referenced
this pull request
Mar 16, 2022
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.
I ended up not being able to modify the docker container itself to start the two processes.
The docker
CMD
for the cloud image is/app/kibana.sh
. Cloud is mounting a volume to/app/
that overwrites the/app/kibana.sh
included in the container, and the Cloudkibana.sh
calls/usr/share/kibana/bin/kibana
. That's why this PR changesbin/kibana
to spawn the two processes.I also thought about changing the
CMD
to a path that isn't overwritten by Cloud so we'd have full control over the start script, but as far as I can tell, the Cloud allocator is generating thekibana.sh
using a templating language based on variables that we don't have access to any other way.