-
Notifications
You must be signed in to change notification settings - Fork 3.3k
build: Update iptables-wrapper
in runtime image
#39996
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Largely inspired from build-gops.sh
for consistency
# Update ubuntu packages to the most recent versions | ||
RUN apt-get update && \ | ||
apt-get upgrade -y && \ | ||
apt-get install -y jq |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved/merged with images/runtime/install-runtime-deps.sh
|
||
x86_64-linux-gnu-strip /out/linux/amd64/bin/gops | ||
aarch64-linux-gnu-strip /out/linux/arm64/bin/gops |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Manually striping the binaries is not necessary as they are already built with -ldflags "-s -w"
:
-s Omit the symbol table and debug information.
-w Omit the DWARF symbol table.
I think that with this change making changes to the base images, we'll need to more actively shepherd this in. Typically these images are maintained by folks with write privileges into the repo ("Reviewer" on the community ladder) and we will push a PR branch to this repo in order to update the image. The "Base Image Release Build" workflow can then push an updated commit into the tree to ensure that the base image change propagates into all the relevant dockerfiles. I've approved the workflow to do that update but given that the PR is opened from outside the repository, I expect it will fail due to lack of permissions to push to your branch. However you may be able to just update the same files as what that action is doing and re-push, then the base image lint workflow will test whether the change was right (and hopefully just pass). |
Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
5ef49c1
to
319a460
Compare
Now that you're a reviewer, I would suggest opening a fresh PR by pushing a branch like |
Thanks, I opened #40099 to replace this PR |
The current
iptables-wrapper
version is 3 years old.iptables-wrapper
has since been rewritten from a bash script to a small go binary.This PR updates
iptables-wrapper
to the latest version (diff) and adapts thecilium-runtime
image Dockerfile to account for the fact that it's now a go binary that needs to be built.Test:
Please ensure your pull request adheres to the following guidelines:
description and a
Fixes: #XXX
line if the commit addresses a particularGitHub issue.
Fixes: <commit-id>
tag, thenplease add the commit author[s] as reviewer[s] to this issue.