Conversation
Contributor
Author
|
/hold |
aledbf
approved these changes
Feb 21, 2023
|
started the job as gitpod-build-cw-cgroupv2.2 because the annotations in the pull request description changed |
Contributor
Author
|
/werft run 👍 started the job as gitpod-build-cw-cgroupv2.3 |
Contributor
Author
|
/hold cancel |
Contributor
|
/hold cancel |
roboquat
added
deployed: workspace
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
We've been running on cgroup v2 for a while now, and any Gitpod installation on cgroup v1 is indicative of a configuration issue. On cgroup v1 core functionality of Gitpod does not function.
This PR removes the last remnant of cgroupv1 support, and enforces cgroupv2 within ws-daemon.
How to test
Run on a cgroupv1 system and observe ws-daemon failing to start.
Release Notes
Documentation
Build Options:
Experimental feature to run the build with GitHub Actions (and not in Werft).
leeway-target=components:all
Run Leeway with
--dont-testPublish Options
Installer Options
Add desired feature flags to the end of the line above, space separated
Preview Environment Options:
If enabled this will build
install/previewIf enabled this will create the environment on GCE infra
Valid options are
all,workspace,webapp,ide,jetbrains,vscode,ssh