17 Commits

Author SHA1 Message Date
927b13dfa5 troubleshooting: explain setup user: invalid argument
replace an old issue that is not valid anymore, since we support
single UIDs mapped into the namespace.

Closes: https://github.com/containers/libpod/issues/2714

Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2019-03-21 18:53:27 +01:00
d033452b3d Replace skopeo-containers with containers-common
Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com>

Replaces 'skopeo-containers' with 'containers-common' in the files that
I feel comfortable changing it in.  There are a number of rpm building
related files that still have it, but I was hesitant to do so.

Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com>
2019-03-14 09:01:30 -04:00
4bc108d90d Update troubleshooting guide for Podman-in-Podman
Add a small section on the bad things that can happen if you
don't mount in our temporary directories.

Fixes #1602

Signed-off-by: Matthew Heon <matthew.heon@pm.me>
2019-03-11 14:35:45 -04:00
550f9b1f6f Add troublshoot information about SELinux labeling of containers/storage
We have some bug reports about people moving containers storage to new
directories and this troubleshooter should help them fix this.

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
2019-03-08 16:07:59 -05:00
62c8ba527e Add troubleshooting information about running a rootless containers.
Add a problem statement about shadow-utils and missing entries from
/etc/subuid and /etc/subgid.

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
2019-02-10 08:08:22 -07:00
1dd7bd0d0f Add documentation on running systemd on SELinux systems
Lots of users are attempting to run systemd within a container.  They are
being blocked from running SELinux systems since they need the
container_manage_cgroup which is not enabled by default.

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
2019-02-06 05:52:39 -08:00
65e947e111 Add local storage.conf example to troubleshoot
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
2019-01-14 09:53:37 -05:00
d252c2ae08 Add troubleshooting statement for homedirs mounted noexec
This fixes https://bugzilla.redhat.com/show_bug.cgi?id=1651228

Users were surprised when they were not able to run a contianer on a noexec homedir.

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
2019-01-13 06:22:10 -05:00
a25b707fdb Touch up some troubleshooting nits
Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com>
2019-01-02 14:14:50 -05:00
ad36345fde Add troubleshooting for sparse files
A common failure with people building container images is the
creation of large sparse files, particularly useradd creating
the lastlog file.

This PR Documents the failures.

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
2018-12-30 08:08:13 -05:00
4d13262405 Change all 'can not' to 'cannot' for proper usage
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
2018-12-21 10:27:54 -05:00
a4cc7bca60 Merge pull request #1802 from mheon/troubleshooting_rootless
Update troubleshooting guide to deal with rootless path
2018-11-12 10:34:13 -08:00
8bda62e061 Update troubleshooting guide to deal with rootless path
We had a breaking change to rootless containers' temporary files
directories in Podman 0.11.1. Document a workaround to make the
change no longer working.

Signed-off-by: Matthew Heon <matthew.heon@gmail.com>
2018-11-12 12:35:22 -05:00
40f8622742 troubleshooting.md: add a recipe for rootless ping
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2018-11-12 13:03:13 +01:00
f0a3a4329e Add notes to check version on problem
Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com>

Closes: #1462
Approved by: rhatdan
2018-09-13 18:31:21 +00:00
c54b423cb3 troubleshooting: Add console syntax highlighting
These blocks include both shell input and command output.  GitHub uses
Linuguist for syntax highlighting [1].  Linguist defines a
ShellSession language to highlight those [2], although I prefer the
shorter 'console' alias.

This commit also makes this file more consistent about including the
leading prompt and sudo.

I'd also be fine using the traditional '#' prompt for privileged users
instead of '$ sudo', to be less opinionated about *how* the user
acquires the privileges (via sudo or otherwise).  Linguist's
shell-session grammar is from Atom [3], and that grammar recognizes
any of >$#% as the final prompt character [4].  But I've left this
facet alone for now.

[1]: https://help.github.com/articles/creating-and-highlighting-code-blocks/#syntax-highlighting
[2]: https://github.com/github/linguist/blob/v6.1.0/lib/linguist/languages.yml#L4362-L4373
[3]: https://github.com/github/linguist/blame/v6.1.0/vendor/README.md#L335
[4]: https://github.com/atom/language-shellscript/blob/v0.26.3/grammars/shell-session.cson#L22

Signed-off-by: W. Trevor King <wking@tremily.us>

Closes: #796
Approved by: rhatdan
2018-05-18 00:11:10 +00:00
3b02a131cd Add Troubleshooting guide
Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com>

Closes: #793
Approved by: mheon
2018-05-17 17:48:51 +00:00