Cherry-pick #18408 to 7.x: Fix jq: command not found #18416
Merged
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
* install jq in separate steps * changelog * move up * comment * embarrasing commit * tidy * Update dev-tools/packaging/templates/docker/Dockerfile.elastic-agent.tmpl Co-authored-by: Blake Rouse <blake.rouse@elastic.co> Co-authored-by: Blake Rouse <blake.rouse@elastic.co>
michalpristas
added
bug
backport
elastic-agent
Ingest Management:alpha1
|
Pinging @elastic/ingest-management (Team:Ingest Management) |
botelastic
bot
added
the
needs_team
kaiyan-sheng
approved these changes
May 11, 2020
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
|
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.
Cherry-pick of PR #18408 to 7.x branch. Original message:
What does this PR do?
Fixes jq command not found issue with generated dockerfile by splitting installation in two steps.
Why is it important?
to have jq present so entrypoint script is able to parse fleet responses
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.How to test it
build Dockerfiles out of templates using
you will find it inside
x-pack/elastic-agent/build/package/elastic-agent/elastic-agent-linux-amd64.docker/docker-buildfrom ^^ directory build docker image and run it
verify that
jqis presentFixes: #18406