[Fix] Agent incapable of running on Azure Container Instances #3576
Conversation
)" This reverts commit 1bf9027.
michalpristas
added
bug
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
|
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
|
This pull request does not have a backport label. Could you fix it @michalpristas? 🙏
NOTE: |
michalpristas
added
backport-v8.11.0
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsExpand to view the GitHub comments
To re-run your PR in the CI, just comment with:
|
🌐 Coverage report
|
dev-tools/packaging/templates/docker/Dockerfile.elastic-agent.tmpl
Outdated
Show resolved
Hide resolved
…tmpl Co-authored-by: Paolo Chilà <paolo.chila@elastic.co>
|
SonarQube Quality Gate
|
What this change is introducing on top of bringing back work introduced in #3084 is change of ordrer for some operations. Changing owner of a file, discards capabilities set. This becomes a problem with heartbeat as it needs setuid and netraw capabilities to perform properly. So setting capabilities was moved after chown. (cherry picked from commit fa357a8)
…#3614) What this change is introducing on top of bringing back work introduced in #3084 is change of ordrer for some operations. Changing owner of a file, discards capabilities set. This becomes a problem with heartbeat as it needs setuid and netraw capabilities to perform properly. So setting capabilities was moved after chown. (cherry picked from commit fa357a8) Co-authored-by: Michal Pristas <michal.pristas@gmail.com>
…elastic#3576) (elastic#3614)" This reverts commit 7eb6e4a.
…elastic#3576)" This reverts commit fa357a8.
…nstances (elastic#3576)" (elastic#3723)" This reverts commit 29386eb.
Bringing back #3139
What this change is introducing on top of bringing back work introduced in #3084 is change of ordrer for some operations.
Changing owner of a file, discards capabilities set. This becomes a problem with heartbeat as it needs
setuidandnetrawcapabilities to perform properly.So setting capabilities was moved after chown.
How to test
docker run --rm -it --entrypoint /bin/bash {image_id} -c "getcap data/elastic-agent-*/components/heartbeat"-> this needs to have output (capabilities mentioned earlier)I also checked with @justinkambic to see if we can test this with their failing E2E but it seems we need to merge it to see it fail. But it won't fail. OK?
Fixes: #82