summaryrefslogtreecommitdiff
path: root/troubleshooting.md
Commit message (Collapse)AuthorAge
* Fix troubleshooting documentation on handling sublemental groups.Daniel J Walsh2021-05-03
| | | | | | Fixes: https://github.com/containers/podman/issues/10166 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
* Merge pull request #10139 from rhatdan/troubleshootOpenShift Merge Robot2021-04-28
|\ | | | | [CI:DOCS] Add troubleshooting advice about the --userns option.
| * Add troubleshooting advice about the --userns option.Josh Berkus2021-04-26
| | | | | | | | | | | | | | | | | | Also a link to the troubleshooting guide into the issue template. Replaces: https://github.com/containers/podman/pull/9770 Signed-off-by: Josh Berkus <josh@agliodbs.com> Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
* | rootless: Tell the user what was led to the error, not just what it isAndrej Shadura2021-04-27
|/ | | | | | | | | | | | | | | | | | Users coming e.g. from Docker do not always read the manual and expect podman to not require sudo or uidmap, for them the default message is not very helpful: Error: Cannot connect to the Podman socket, make sure there is a Podman REST API service running.: cannot find newuidmap: exec: "newuidmap": executable file not found in $PATH Adding a bit more context to this would help to nudge them into the right direction and tell them what to look for in the documentation: command required for rootless mode with multiple IDs: exec: "newuidmap": executable file not found in $PATH Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk> [NO TESTS NEEDED]
* Update troubleshooting.mdxatier2021-02-15
| | | | | | | | | Note that `[registries.search]` (the v1 format) is still supported, but `registries.conf` can not mix v1 with v2 syntax. [1] https://github.com/containers/image/commit/c04fa245754dc2c250424445f4190f348401f27b#diff-968a44bf11ad55a626a0d13a78ade8944ade3a36f53c7a3f985a9036cd64f5a5 Signed-off-by: xatier <xatierlike@gmail.com>
* Switch references of /var/run -> /runDaniel J Walsh2021-01-07
| | | | | | | | | | Systemd is now complaining or mentioning /var/run as a legacy directory. It has been many years where /var/run is a symlink to /run on all most distributions, make the change to the default. Partial fix for https://github.com/containers/podman/issues/8369 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
* Clarify uid range requirementsRodrigo Lourenço2020-12-04
| | | | Signed-off-by: Rodrigo Lourenço <rzl@rzl.ooo>
* correct numbering typoSeth Jones2020-11-18
| | | | | | Based on PR from @sethjones. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
* Fix issues found with codespellDaniel J Walsh2020-11-12
| | | | Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
* Add tip re. typical root cause of "Exec format error" to troubleshooting.mdMichael Vorburger ⛑️2020-11-03
| | | | Signed-off-by: Michael Vorburger <mike@vorburger.ch>
* Document how to enable CPU limit delegationJordan Christiansen2020-10-27
| | | | Signed-off-by: Jordan Christiansen <xordspar0@gmail.com>
* Document --read-only --rootfs requirementsDaniel J Walsh2020-09-11
| | | | | | | | | Add entry to troubleshooting to document how to setup a read-only rootfs to use with Podman. Fixes: https://github.com/containers/podman/issues/5895 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
* [CI:DOCS] Add note on run image fuse problem - try 2TomSweeneyRedHat2020-09-04
| | | | | | | | | | | | | | | | | | We've recently had a number of issues reported against our pre-fabricated images on quay.io and a couple of rhel repositories throwing a fuse error when run: ``` fuse: device not found, try 'modprobe fuse' first ``` The tip on modprobe fuse is not always seen by or displayed to the end user. Adding a couple of doc pointers to hopefully help. Arises from this BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1867892 and several others. Replaces: 7453 where I was going crazy with whitespace and merge issues. Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com>
* Note port publishing needs in pods for create/runTomSweeneyRedHat2020-08-19
| | | | | | | | | | Add notes to the podman-create and podman-run man pages to note that ports do not need to be published and should not be, for containers that will be part of a pod. Addresses: #6769 Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com>
* Switch references from libpod.conf to containers.confDaniel J Walsh2020-07-20
| | | | Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
* Remove reference to "upcoming" RHEL 7.7Matthew Heon2020-06-02
| | | | | | | | | 7.7 has been released for a while now, so change troubleshooting reference to indicate that. Fixes #6349 Signed-off-by: Matthew Heon <matthew.heon@pm.me>
* Add information on detach-keysDaniel J Walsh2020-06-01
| | | | Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
* Update troubleshoot pageDaniel J Walsh2020-05-19
| | | | | | | | | Add information about podman with SELinux and using container_init_t. Add informantion about Centos7 as well as RHEL7 init containers not working on a cgroups V2 system. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
* Fix typo in pathTom Fenech2020-05-08
| | | | Signed-off-by: Tom Fenech <tomjwfenech@gmail.com>
* [CI:DOC] Add linger to troubleshootingTomSweeneyRedHat2020-05-04
| | | | | | | | | Adding a troubleshooting note about how to configure systemd to linger for detached containers in rootless mode. This came up in an email stream on the Podman mailing list today and answered by @mheon Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com>
* 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
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-06 17:37:11 +0000