Ubuntu 22 builders now available for GCP Buildpacks #271
Replies: 2 comments 1 reply
-
|
The latest tag still appears to be pointing to google-22, anything come up recently that prevents this update? |
Beta Was this translation helpful? Give feedback.
-
|
Good question! We were planning to switch over March 6, but we ran into some hiccups. Its taken a bit longer than we expected to update the PHP buildpacks to support 8.2 We wanted to wait until we had support for all 7 languages before flipping over to We're also pumping the brakes on the switchover because we're worried about the potential for breaking |
Beta Was this translation helpful? Give feedback.
-
|
We're attempting to port over as many languages from the |
Beta Was this translation helpful? Give feedback.
-
April 25, 2023 Update
We are now targeting June 5, 2023 for the switchover from
latesttogoogle-22April 24, 2023 Update
In order to reduce the chance of breaking users between
v1andgoogle-22, we're increasing the language support ingoogle-22by adding:Ruby 3.0These languages are still in support by their respective OSS communities, so we feel comfortable adding those in.
April 6, 2023 Update:
We're pumping the brakes on the switchover because we're worried about the potential for breaking
cloud run deploy --source. Trying to create a few more guardrails for those users before making the official cutover. Will try to keep this thread updated with datesHi folks!
Today, we're excited to introduce the Ubuntu 22 (Jammy Jellyfish) builders into GCP’s buildpacks. This new builder uses Ubuntu 22 as the base image for both the run and build environments. You can find the new builder under the
:google-22tag here https://gcr.io/buildpacks/builder:google-22IMPORTANT With the release of this builder we will also be planning to switch over the
:latesttag to point to:google-22onMarch 6, 2023June 5, 2023.Why is this important?
Ubuntu 18 ESM
Using the GCP’s buildpacks project, the default builder
gcr.io/buildpacks/builder:v1uses Ubuntu 18 as the container base image. With Ubuntu 18 moving into Extended Security Maintenance in April, 2023, it will be receiving fewer security and maintenance updates.Support for Node.js 18 and newer languages
When Node.js 18 launched last year (2022), it was built with a newer version of
glibc/Ubuntuthat wasn’t available on Ubuntu 18 (#248). The introduction of the Ubuntu 22 builder fixes this. Moving forward, we will be pushing to make the Ubuntu 22 builder the default builder image so that our users get full use of modern OS environments.Improved Security & Smaller Images
Ubuntu 22 currently falls under Canonical’s Standard Support until April 2027. As some of ya'll have already pointed this out to us in #232, #236 and #270, this leads to container images that have "fixable" CVEs in them.
The Ubuntu 22 builder utilizes the updated jammy packages repo with updated dependencies. Using the Ubuntu 22 builder, you can produce images that are ~27% smaller and with half as many CVEs:
Building a sample-go app we see the following improvements between the builders:
Using the new Builder
The new build can be found at https://gcr.io/buildpacks/builder:google-22
There are three ways to use the new builder:
packCLILocally with pack CLI
You can utilize the
--builderflag to specify the newgoogle-22tag on the builder image as follows:For more detailed instructions on building an image with
pack, see Local builds with GCP’s buildpacksRemotely with Cloud Build
Cloud Build supports additional parameters on the
--packflag. Note that the fields after--packis one continuous string, with the two parameters separated by a comma,For more detailed instructions on building an image remote with Cloud Build, see Remote builds with GCP’s buildpacks
Supported Language Version
I'll be updating our docs page soon, but the new builder supports the following language versions:
Other questions you might have
Where can I find the builder code and image?
What packages are installed onto the builder images
Each builder comes with a build image and a run image.
Why is there still 1 fixable CVE in the sample app?
We think it has to do with an outdated dependency, likely the pack CLI. We’ve gotten in touch with the Skaffold team and have requested them to update their images with the newest version of pack. This work is being tracked here GoogleContainerTools/skaffold#8290
Will this break existing apps?
No...not yet! By default, gcr.io/buildpacks/builder points to the latest tag, which in turn points to the v1 tag for our most up-to-date Ubuntu 18 builder.
What's the switchover plan to make
google-22the default builder?Our plan is as follows:
Announcement
March 6, 2023June 5, 2023,:latestwill point to:v1Feedback
google-22builderSwitchover
March 6, 2023June 5, 2023:latestpoints to:google-22:v1tag will still be available for users who want to build with the older environmentBeta Was this translation helpful? Give feedback.
All reactions