Skip to content
Snippets Groups Projects
Commit 627d5d6a authored by Simon McVittie's avatar Simon McVittie
Browse files

README: Add more hints about how to debug startup failures

parent 24d28a50
No related branches found
No related tags found
No related merge requests found
......@@ -352,7 +352,7 @@ configured.
are available in `/overrides` inside that filesystem, while selected
files from the host are visible in `/run/host`.
* To test something manually:
* To test something manually, or to debug startup issues:
- cd to the directory that you want to be the current working directory
inside the container
......@@ -361,13 +361,20 @@ configured.
/opt/pressure-vessel/bin/pressure-vessel-test-ui -- ./whatever-game
or:
or for the low-level version:
/opt/pressure-vessel/bin/pressure-vessel-wrap -- ./whatever-game
Optionally add more options before the `--`, such as `--runtime`,
`--xterm` and `--interactive`.
In particular, if the `xterm` can't be launched and you are debugging
why, use the `--interactive` option to get a shell in the container.
If `bwrap` is failing to start up and so you can't get a shell in the
container at all, construct a simpler-but-simpler `bwrap` command-line
(based on what `pressure-vessel-wrap` logs to stderr) and try that.
* For interactive testing from Steam, if your runtime (if used) or host
system (if no runtime) contains an `xterm` binary, you can use
something like:
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment