-
Notifications
You must be signed in to change notification settings - Fork 327
jammy (Ubuntu 22.04 LTS)- based images #810
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
Comments
@gitpod-io/engineering-workspace do we have any hard dependency on ubuntu version that might break with this change. Things like existing work so far with K3s in gitpod / tailscale etc? We can curate a list and then make sure that we test it before releasing related change to the public. Our existing tests are not enough IMO to just merge a base image verion upgrade change. |
Prebuild system and underlying Kubernetes should be updated. Details were described in the following comment: Versioning with Docker image tagging would be helpful to maintain the stack, like |
Not that I am aware of. |
It would be great if users could start testing with Jammy. Any updates here? |
Hi @tnir @ianhellstrom and @david-bakin, It just so happens that we're updating our documentation to help users create custom images which do not use Gitpod base images. For example, if your workflow cannot use a Gitpod base image, the docs will show customizations that are needed to have a successful image build, as well as a nice development experience in Gitpod. This may also be a good short term solution for you if your workflow requires Jammy. Also, we plan to publish a version of Finally, after we've tested internally and collected feedback from the community, we'll consider making this generally available as Let us know if this helps, or if you have any other questions? |
Uh oh!
There was an error while loading. Please reload this page.
jammy (Ubuntu 22.04 LTS)
is comingis just released.What is the strategy for jammy-based workspace images?
Resources
The text was updated successfully, but these errors were encountered: