-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[test] experimental inner loop with isolation network and process tree #15687
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
Conversation
|
started the job as gitpod-build-pd-pd-wskit-2.7 because the annotations in the pull request description changed |
768aab5 to
ea9720f
Compare
467914f to
be4dbfc
Compare
|
/werft run 👍 started the job as gitpod-build-pd-pd-wskit-2.30 |
|
/werft run recreate-vm=true 👍 started the job as gitpod-build-pd-pd-wskit-2.31 |
|
/werft run with-clean-slate-deployment=true 👍 started the job as gitpod-build-pd-pd-wskit-2.32 |
ade34f7 to
c8553ac
Compare
Description
this PR is an experimental inner loop with an isolation network and process tree and special root filesystem, this PR focus on custom docker image
Related Issue(s)
Fixes #
How to test
/.debug/rootfsfolder/.supervisor/supervisor inner-loopto build a new process tree with new root filesystemWeb UI available at http://localhost:23000it means IDE is ready, you add prefixdebug-in your workspace URL, to access debug wokspace.curl lams.sh | shin debug workspace, you will see a notification, click open in browser, you can view this port in debug workspace. (url prefix{port}-debug-{workspaceId})Control + Cto stop debug workspace.Release Notes
Documentation
Werft options:
If enabled this will build
install/previewValid options are
all,workspace,webapp,ide,jetbrains,vscode,ssh