Conversation
|
Pinging @elastic/integrations (Team:Integrations) |
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
|
/package |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
|
Updating docker to try to solve issue with dockerlogbeat build: |
ChrsMark
left a comment
There was a problem hiding this comment.
The change looks sane to me if CI agrees :).
|
It will also cover #28464 which has some CI issues. |
|
/test |
|
The issue with the generator is legit, I can reproduce it locally, I am trying to find what happens there. |
|
Ok, the problem is that the generator uses the Here it uses the current working copy: https://github.com/elastic/beats/blob/16aa13e342609adad69cc092d3649982da71ddcd/generator/common/beatgen/setup/setup.go#L48 But the code from the current upstream master: |
This reverts commit 16aa13e342609adad69cc092d3649982da71ddcd.
This reverts commit 3903c0282caca4282be2a815b3d8d96fbc4bbb6e.
16aa13e to
871a199
Compare
| IncludeFiles: []string{"rootfs", "config.json"}, | ||
| } | ||
| archive, err := archive.TarWithOptions(buildDir, archiveOpts) | ||
| archive, err := tar(buildDir, "rootfs", "config.json") |
There was a problem hiding this comment.
@fearful-symmetry could you please take a look to the changes here?
I am doing this because updating containerd broke github.com/docker/docker/pkg/archive. The solution would be to upgrade docker, but upgrading docker breaks community beats (more info in other comment).
I saw that we are already using the tar command in other parts of this magefile, so I guess it is ok to use it here too 🙂 I gave it a try and it seems to work. Could you please double-check?
As a side advantage, after removing github.com/docker/docker/pkg/archive from here, runc doesn't appear anymore in go.mod.
There was a problem hiding this comment.
We can also decide to update docker and break (or remove) community beats in master/8.0, but I would leave this discussion for later.
There was a problem hiding this comment.
Gimme a few, lemme pull this down and poke around.
There was a problem hiding this comment.
So, the build seems to work, I suspect I just did that because I'm not a fan of shelling out when I don't need to.
There was a problem hiding this comment.
Thanks for checking!
I'm not a fan of shelling out when I don't need to.
+1 to this 🙂 But in this case we remove a problematic dependency, and we are already shelling out for other things. If this becomes problematic we can look for a different tar library in the future.
|
There were additional changes since last review, could I have another round? 🙂 |
|
E2E test failures are not related, they are also failing in master. |
|
This pull request is now in conflicts. Could you fix it? 🙏 |
|
/test |
|
E2E failures are unrelated. |
Solve some dependabot warnings (the issues are starting containers and pulling images, something beats don't do). Removes a dependency on runc in dockerlogbeat build scripts. (cherry picked from commit 97818c3) # Conflicts: # NOTICE.txt # go.mod # go.sum
Solve some dependabot warnings (the issues are starting containers and pulling images, something beats don't do). Removes a dependency on runc in dockerlogbeat build scripts. (cherry picked from commit 97818c3) # Conflicts: # go.sum
Solve some dependabot warnings (the issues are starting containers and pulling images, something beats don't do). Removes a dependency on runc in dockerlogbeat build scripts. (cherry picked from commit 97818c3) Co-authored-by: Jaime Soriano Pastor <jaime.soriano@elastic.co>
Solve some dependabot warnings (the issues are starting containers and pulling images, something beats don't do). Removes a dependency on runc in dockerlogbeat build scripts. (cherry picked from commit 97818c3) Co-authored-by: Jaime Soriano Pastor <jaime.soriano@elastic.co>
Solve some dependabot warnings (the issues are starting containers and pulling images, something beats don't do). Removes a dependency on runc in dockerlogbeat build scripts.
What does this PR do?
Update runc and contained dependencies.
Why is it important?
Checklist
I have commented my code, particularly in hard-to-understand areasI have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.