Upgrade Ubuntu container to 22.04 #302
Conversation
Signed-off-by: Victor Vasiliev <vasilvv@google.com>
|
iiuc this will change which distros we can support - ie it will make the envoy binary that is produced incompatible with more distro/versions cc @lizan |
What do we need to do to make forward progress on this? This change will allow us to get C++20 support in Envoy, which is required for at least the Google URL dependency. |
well iiuc then there is not much we can do other than create some path/code for legacy toolchains - this would already be a great thing and would resolve a bunch of tangentially related issues, but its not trivial without that its more of a political decision about when we stop supporting which distro/versions |
What if we only used the new 22.04 image for gcc CI, but use the old imagine for everything else? Would that help? |
with current setup it would mean separating images/build/etc and corresponding images in envoy |
Would that be easier/better than trying to just use 22.04 for everything? |
if we want to support multiple toolchains its not going to be easy whatever way we do it - either in terms of setup or maintenance i think there is a ~right way to do this - not that i necessarily know it at this point, and probs that is the way to pursue |
No description provided.