mirror of
https://github.com/containers/podman.git
synced 2025-08-02 17:22:30 +08:00
c54b423cb3
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
61 lines
2.1 KiB
Markdown
61 lines
2.1 KiB
Markdown
|
|
|
|
# Troubleshooting
|
|
|
|
## A list of common issues and solutions for Podman
|
|
|
|
---
|
|
### 1) No such image or Bare keys cannot contain ':'
|
|
|
|
When doing a `podman pull` or `podman build` command and a "common" image can not be pulled,
|
|
it is likely that the `/etc/containers/registries.conf` file is either not installed or possibly
|
|
misconfigured.
|
|
|
|
#### Symptom
|
|
|
|
```console
|
|
$ sudo podman build -f Dockerfile
|
|
STEP 1: FROM alpine
|
|
error building: error creating build container: no such image "alpine" in registry: image not known
|
|
```
|
|
|
|
or
|
|
|
|
```console
|
|
$ sudo podman pull fedora
|
|
error pulling image "fedora": unable to pull fedora: error getting default registries to try: Near line 9 (last key parsed ''): Bare keys cannot contain ':'.
|
|
```
|
|
|
|
#### Solution
|
|
|
|
* Verify that the `/etc/containers/registries.conf` file exists. If not, verify that the skopeo-containers package is installed.
|
|
* Verify that the entries in the `[registries.search]` section of the /etc/containers/registries.conf file are valid and reachable.
|
|
* i.e. `registries = ['registry.fedoraproject.org', 'quay.io', 'registry.access.redhat.com']`
|
|
|
|
---
|
|
### 2) http: server gave HTTP response to HTTPS client
|
|
|
|
When doing a Podman command such as `build`, `commit`, `pull`, or `push` to a registry,
|
|
tls verification is turned on by default. If authentication is not used with
|
|
those commands, this error can occur.
|
|
|
|
#### Symptom
|
|
|
|
```console
|
|
$ sudo podman push alpine docker://localhost:5000/myalpine:latest
|
|
Getting image source signatures
|
|
Get https://localhost:5000/v2/: http: server gave HTTP response to HTTPS client
|
|
```
|
|
|
|
#### Solution
|
|
|
|
By default tls verification is turned on when communicating to registries from
|
|
Podman. If the registry does not require authentication the Podman commands
|
|
such as `build`, `commit`, `pull` and `push` will fail unless tls verification is turned
|
|
off using the `--tls-verify` option. **NOTE:** It is not at all recommended to
|
|
communicate with a registry and not use tls verification.
|
|
|
|
* Turn off tls verification by passing false to the tls-verification option.
|
|
* I.e. `podman push --tls-verify=false alpine docker://localhost:5000/myalpine:latest`
|
|
---
|