You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,7 +107,7 @@ runc run mycontainerid
107
107
If you used the unmodified `runc spec` template this should give you a `sh` session inside the container.
108
108
109
109
The second way to start a container is using the specs lifecycle operations.
110
-
This gives you move power of how the container is created and managed while it is running.
110
+
This gives you more power over how the container is created and managed while it is running.
111
111
This will also launch the container in the background so you will have to edit the `config.json` to remove the `terminal` setting for the simple examples here.
112
112
Your process field in the `config.json` should look like this below with `"terminal": false` and `"args": ["sleep", "5"]`.
0 commit comments