starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-02-05 00:29:40 +03:00
Code Issues 32 Packages Projects Releases 10 Wiki Activity

podman - Error: error getting default registries to try: short-name "vaultwarden/server:latest" #1156

New Issue
Closed
opened 2026-02-05 00:08:52 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-05 00:08:52 +03:00
Owner
Copy Link

Originally created by @rapkin61 on GitHub (Nov 30, 2021).

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). <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue <!-- Describe your issue here. --> 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 <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> * Reverse proxy and version: <!-- if applicable --> * MySQL/MariaDB or PostgreSQL version: <!-- if applicable --> * Other relevant details: ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> ### Expected behaviour <!-- Tell us what you expected to happen --> ### Actual behaviour <!-- Tell us what actually happened --> ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data -->
OVERLORD commented 2026-02-05 00:09:01 +03:00
Author
Owner
Copy Link

@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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
troubleshooting
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#1156
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?