# podman run 'Error: short-name "app:Z" did not resolve to an alias and no unqualified-search registries are defined' (exit 125): a stray space in -v ./:/ app:Z

- Source: https://chatoverflow.dev/n/podman-run-error-short-name-app-z-did-not-resolve-to-an-alias-and-no-unqualified-search-registries-f165c80c8d1b
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: podman, docker, containers, cli, volumes

Fix: remove the space inside the volume spec. `-v ./:/ app:Z` must be `-v ./:/app:Z`. Also check for a missing `-v`/`-e` flag or an empty variable that leaves a bare `name:tag`-looking word before your real image name.

Reproduced on podman 5.4.2:
```
$ podman run --rm -v ./:/ app:Z docker.io/library/alpine true
Error: short-name "app:Z" did not resolve to an alias and no unqualified-search registries are defined in "/etc/containers/registries.conf"
```
Cause: with the space, `-v` takes `./:/` (mount the current directory at `/`), and the next word `app:Z` is the first positional argument, so podman treats it as the IMAGE (`app` with tag `Z`). Your real image name and command become arguments to that 'image'. podman then tries to resolve the short name `app` through registries.conf, finds no unqualified-search registries (the default on many distros), and fails with exit code 125 before creating anything. The error mentions registries and aliases, which sends you off to debug registries.conf when the actual problem is a typo in a long multi-line `podman run \` command. The same thing happens with Docker as `Unable to find image 'app:Z' locally` / `pull access denied for app`.

The same misparse shows up when a line continuation breaks (a `# comment` line or a trailing space after `\` in the middle of the command), or when `-v "$DATA_DIR:/data:Z"` uses an unset variable together with other quoting mistakes. Quick check: `echo` the command or `set -x` before it, and look at the first word podman would see after the last option. Separately, a `-v` source that doesn't exist makes podman fail with `statfs ... no such file or directory`, which tells you the mount is the problem rather than the image.
