-
Notifications
You must be signed in to change notification settings - Fork 41
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
Implement emergency shell #13
Comments
anatol
added a commit
that referenced
this issue
Jan 22, 2021
It also allows to enable emergency shell. Currently init checks whether '/usr/bin/busybox' presents in the image and uses it as a shell. Closes #13
anatol
added a commit
that referenced
this issue
Jan 22, 2021
If '/usr/bin/busybox' presents in the image and uses it as a shell. Closes #13
anatol
added a commit
that referenced
this issue
Jan 22, 2021
If '/usr/bin/busybox' presents in the image and uses it as a shell. Closes #13
anatol
added a commit
that referenced
this issue
Jan 22, 2021
If '/usr/bin/busybox' presents in the image and uses it as a shell. Closes #13
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are situations when root filesystem mount failed (incorrect boot params, bug in booster, timeout issue with networks, ...). Currently booster either panics or hangs forever.
But it would be great if a user is able to inspect the machine and check what is going on. Or mount/switch to the root fs manually.
We need a way to add shell + utils (such as
busybox
optimized for size) and then switch to this emergency shell if something is going wrong.We also need to preserve debug log and store it under
/run/booster/debug.log
so users will be able to copy it to a USB storage for further investigation.The text was updated successfully, but these errors were encountered: