github/kata-containers
1
0
Fork 1
mirror of https://github.com/kata-containers/kata-containers.git synced 2025-08-14 22:24:14 +00:00
Code Issues Projects Releases Wiki Activity

Merge ee9a8b7d98 into 9379a18c8a

Browse Source
This commit is contained in:
MAjjzYWH 2025-08-12 09:31:18 +01:00 committed by GitHub
commit 7ad6438d05
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/Debug-shim-guide.md
View File

@ -5,7 +5,7 @@ process that is run by the runtime manager (containerd/CRI-O), and controlled by
sending gRPC requests to it.
Starting the shim with a debugger then just gives you a process that waits for
commands on its socket, and if the runtime manager doesn't start it, it won't
send request to it.
send requests to it.
A first method is to attach a debugger to the process that was started by the
runtime manager.
@ -17,7 +17,7 @@ and the actual shim binary. This allows to start the shim with a debugger, and
wait for a client debugger connection before execution, allowing debugging of the
kata runtime from the very beginning.
## Prerequisite
## Prerequisites
At the time of writing, a debugger was used only with the go shim, but a similar
process should be doable with runtime-rs. This documentation will be enhanced

2
docs/Developer-Guide.md
View File

@ -27,7 +27,7 @@ to build the Kata Containers components from source.
> **Note:**
>
> If you decide to build from sources, you should be aware of the
> If you decide to build from source, you should be aware of the
> implications of using an unpackaged system which will not be automatically
> updated as new [releases](https://github.com/kata-containers/kata-containers/releases) are made available.