[GH-ISSUE #2122] podman - Error: error getting default registries to try: short-name "vaultwarden/server:latest" #1162

New issue

Closed

opened 2026-03-03 02:06:46 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 02:06:46 +03:00

Owner

Originally created by @rapkin61 on GitHub (Nov 30, 2021).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2122

Subject of the issue

Tried to run vaultwarden using podman as described in the wiki.
But podman does not know how to pull the image. As far as I understood, it needs a FQDN

podman run -d --name vaultwarden -v /var/vw_data/:/data/:Z -e ROCKET_PORT=8080 -p 8080:8080 vaultwarden/server:latest
Error: error getting default registries to try: short-name "vaultwarden/server:latest" did not resolve to an alias and no unqualified-search registries are defined in "/etc/containers/registries.conf"

What is the correct path to the image?

Moreover, podman seems to need some kind of lingering, like:

sudo loginctl enable-linger 1012

where 1012 is the UID of the user that runs the image

Deployment environment

vaultwarden version:

Install method:
Clients used:
Reverse proxy and version:
MySQL/MariaDB or PostgreSQL version:
Other relevant details:

Steps to reproduce

Expected behaviour

Actual behaviour

Troubleshooting data

Originally created by @rapkin61 on GitHub (Nov 30, 2021). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2122   ### Subject of the issue  Tried to run vaultwarden using podman as described in the wiki. But podman does not know how to pull the image. As far as I understood, it needs a FQDN podman run -d --name vaultwarden -v /var/vw_data/:/data/:Z -e ROCKET_PORT=8080 -p 8080:8080 vaultwarden/server:latest Error: error getting default registries to try: short-name "vaultwarden/server:latest" did not resolve to an alias and no unqualified-search registries are defined in "/etc/containers/registries.conf" What is the correct path to the image? Moreover, podman seems to need some kind of lingering, like: sudo loginctl enable-linger 1012 where 1012 is the UID of the user that runs the image ### Deployment environment     * vaultwarden version:  * Install method: * Clients used:  * Reverse proxy and version:  * MySQL/MariaDB or PostgreSQL version:  * Other relevant details: ### Steps to reproduce  ### Expected behaviour  ### Actual behaviour  ### Troubleshooting data

kerem closed this issue

2026-03-03 02:06:47 +03:00

kerem commented

2026-03-03 02:06:47 +03:00

Author

Owner

@davidkna commented on GitHub (Nov 30, 2021):

The FQDN is docker.io/vaultwarden/server:latest. docker.io is usually listed in /etc/containers/registries.conf by default.

@davidkna commented on GitHub (Nov 30, 2021): The FQDN is `docker.io/vaultwarden/server:latest`. `docker.io` is usually listed in `/etc/containers/registries.conf` by default.