Use buster for base and web images too#4567
Use buster for base and web images too#4567cpretzer merged 1 commit intolinkerd:masterfrom joakimr-axis:joakimr-axis_buster
Conversation
joakimr-axis
requested review from
adleong,
alpeb,
klingerf,
olix0r and
siggy
as code owners
grampelberg
left a comment
grampelberg
left a comment
There was a problem hiding this comment.
Slick! Does this update the proxy-init image as well?
|
We still have linkerd/linkerd2-proxy-init#3 open -- it should be updated. |
Requires setting iptables-legacy as the iptables provider. Signed-off-by: Joakim Roubert <joakim.roubert@axis.com>
|
yep, I still have that in a branch. I think I need to use Awesome work @joakimr-axis |
alpeb
left a comment
alpeb
left a comment
There was a problem hiding this comment.
From my testing, it appears the latest k8s versions are already ensuring the iptables command is linked against the legacy version without having to manually do it in our images, but it's good to have it anyways for older versions 👍
This is working fine using CNI. I'll test the non-CNI scenario in the linkerd2-proxy-init PR 😉
btw, I ran bin/docker-build-base and published the resulting gcr.io/linkerd-io/base:2020-06-08.01 image 
5 participants
Requires setting iptables-legacy as the iptables provider.
Cred should go to @erikwilson and @codeman9 for suggesting the use of iptables-legacy.
k3s-io/k3s#116 (comment)
#3486 (comment)