aboutsummaryrefslogtreecommitdiff
path: root/troubleshooting.md
Commit message (Collapse)AuthorAge
* Add SELinux volume information to troubleshoot.mdDaniel J Walsh2020-04-16
| | | | | | | This issue happens enough that we need to put it on the top of the troubleshoot guide. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
* Fix path of tmp_dirxcffl2020-03-17
| | | | Signed-off-by: xcffl <xcffl@protonmail.com>
* Missing double quotes in troubleshooting guide.Tony Benoy2020-03-15
| | | | Signed-off-by: Tony Benoy <me@tonybenoy.com>
* Add codespell to validate spelling mistakes in code.Daniel J Walsh2020-01-11
| | | | | | Fix all errors found by codespell Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
* docs: add workaround for --device with rootless containersStefan Becker2019-12-17
| | | | | | Fixes #4477 Signed-off-by: Stefan Becker <chemobejk@gmail.com>
* troubleshooting.md: rebased master and bumped 18 to 19nitrocode2019-12-13
| | | | Signed-off-by: nitrocode <nitrocode@users.noreply.github.com>
* troubleshooting: warn about secure bootBrian Fallik2019-12-02
| | | | | | | | | | Add an additional troubleshooting item to warn users that Secure Boot can prevent Podman from running containers. The error messages and initial debugging steps don't make it clear that this all stems from a BIOS setting. Hopefully adding this item to the troubleshooting doc will avoid future headaches. Signed-off-by: Brian Fallik <brian@clypd.com>
* troubleshooting.md: document lingering modeGiuseppe Scrivano2019-10-17
| | | | Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
* troubleshooting: fix useradd no-log-init argumentSimon Li2019-10-06
| | | | | | --log-no-init should be --no-log-init Signed-off-by: Simon Li <spli@dundee.ac.uk>
* Replace "podman" with "Podman"xcffl2019-09-07
| | | | Signed-off-by: xcffl <xcffl@outlook.com>
* docs: add note about failing rhel7 systemd on cgroups v2Giuseppe Scrivano2019-09-02
| | | | | | Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1747933 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
* Add invalid credentials fix to docsTomSweeneyRedHat2019-08-06
| | | | | | | | | | Add an entry to the troubleshooting guide detailing how to get around the problem of invalid credentials when pulling an image that shouldn't require credentials. Fixes: #1963 Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com>
* Add rootless NFS and OverlayFS warnings to docsTomSweeneyRedHat2019-08-02
| | | | | | | | Add warnings/work arounds about NFS and OverlayFS to the troubleshooting guide and also the main podman page. Verified that these warnings are on the rootless page already. Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com>
* troubleshooting.md: add note about updating subuid/subgidGiuseppe Scrivano2019-05-17
| | | | Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
* troubleshooting: explain setup user: invalid argumentGiuseppe Scrivano2019-03-21
| | | | | | | | | 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>
* Replace skopeo-containers with containers-commonTomSweeneyRedHat2019-03-14
| | | | | | | | | | 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>
* Update troubleshooting guide for Podman-in-PodmanMatthew Heon2019-03-11
| | | | | | | | | 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>
* Add troublshoot information about SELinux labeling of containers/storageDaniel J Walsh2019-03-08
| | | | | | | 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>
* Add troubleshooting information about running a rootless containers.Daniel J Walsh2019-02-10
| | | | | | | 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>
* Add documentation on running systemd on SELinux systemsDaniel J Walsh2019-02-06
| | | | | | | | 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>
* Add local storage.conf example to troubleshootDaniel J Walsh2019-01-14
| | | | Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
* Add troubleshooting statement for homedirs mounted noexecDaniel J Walsh2019-01-13
| | | | | | | | 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>
* Touch up some troubleshooting nitsTomSweeneyRedHat2019-01-02
| | | | Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com>
* Add troubleshooting for sparse filesDaniel J Walsh2018-12-30
| | | | | | | | | | 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>
* Change all 'can not' to 'cannot' for proper usageDaniel J Walsh2018-12-21
| | | | Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
* Merge pull request #1802 from mheon/troubleshooting_rootlessOpenShift Merge Robot2018-11-12
|\ | | | | Update troubleshooting guide to deal with rootless path
| * Update troubleshooting guide to deal with rootless pathMatthew Heon2018-11-12
| | | | | | | | | | | | | | | | 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>
* | troubleshooting.md: add a recipe for rootless pingGiuseppe Scrivano2018-11-12
|/ | | | Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
* Add notes to check version on problemTomSweeneyRedHat2018-09-13
| | | | | | | Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com> Closes: #1462 Approved by: rhatdan
* troubleshooting: Add console syntax highlightingW. Trevor King2018-05-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Add Troubleshooting guideTomSweeneyRedHat2018-05-17
Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com> Closes: #793 Approved by: mheon