Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
steam-runtime-tools
Manage
Activity
Members
Labels
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Analyze
Contributor analytics
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
steamrt
steam-runtime-tools
Commits
627d5d6a
Commit
627d5d6a
authored
5 years ago
by
Simon McVittie
Browse files
Options
Downloads
Patches
Plain Diff
README: Add more hints about how to debug startup failures
Signed-off-by:
Simon McVittie
<
smcv@collabora.com
>
parent
24d28a50
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+9
-2
9 additions, 2 deletions
README.md
with
9 additions
and
2 deletions
README.md
+
9
−
2
View file @
627d5d6a
...
...
@@ -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:
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment