github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-03-21 22:12:17 -05:00
Code Issues 79 Packages Projects Releases 78 Wiki Activity

Cant pull docker image due to distribution manifest v1 #5224

New Issue
Closed
opened 2026-03-07 20:17:36 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-03-07 20:17:36 -06:00
Owner
Copy Link

Originally created by @StepanKuklis on GitHub (Apr 30, 2023).

Docker image can't be pulled due to v1 manifest

Hello, when I try to
docker pull vaultwarden/server:latest
I get error
latest: Pulling from vaultwarden/server mediaType in manifest should be 'application/vnd.docker.distribution.manifest.v2+json' not 'application/vnd.oci.image.manifest.v1+json'

I googled a bit, and I think there is nothing I can do from my side, so could you please update the manifest?
I'm doing this on just updated Ubuntu 20.04.6 LTS, Docker version 19.03.3, build a872fc2

thank you

Deployment environment

  • vaultwarden version:
    vaultwarden/server:latest
    DIGEST:sha256:04691aaf1d8531ccb796de620841c030ecfd45613388a2e6a6a9434dc5d14d9d

  • Install method:
    docker image

  • Clients used:

  • Reverse proxy and version:

  • MySQL/MariaDB or PostgreSQL version:

  • Other relevant details:

Steps to reproduce

docker pull vaultwarden/server:latest

Expected behaviour

Pull latest image of vaultwarden docker image.

Actual behaviour

Docker refused to pull latest image ( https://hub.docker.com/layers/vaultwarden/server/latest/images/sha256-04691aaf1d8531ccb796de620841c030ecfd45613388a2e6a6a9434dc5d14d9d?context=explore ).

Troubleshooting data

Originally created by @StepanKuklis on GitHub (Apr 30, 2023). <!-- # ### 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. --> ### Docker image can't be pulled due to v1 manifest <!-- Describe your issue here. --> Hello, when I try to `docker pull vaultwarden/server:latest ` I get error `latest: Pulling from vaultwarden/server mediaType in manifest should be 'application/vnd.docker.distribution.manifest.v2+json' not 'application/vnd.oci.image.manifest.v1+json'` I googled a bit, and I think there is nothing I can do from my side, so could you please update the manifest? I'm doing this on just updated Ubuntu 20.04.6 LTS, Docker version 19.03.3, build a872fc2 thank you ### 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: vaultwarden/server:latest DIGEST:sha256:04691aaf1d8531ccb796de620841c030ecfd45613388a2e6a6a9434dc5d14d9d <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: docker image * 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? --> `docker pull vaultwarden/server:latest` ### Expected behaviour <!-- Tell us what you expected to happen --> Pull latest image of vaultwarden docker image. ### Actual behaviour <!-- Tell us what actually happened --> Docker refused to pull latest image ( https://hub.docker.com/layers/vaultwarden/server/latest/images/sha256-04691aaf1d8531ccb796de620841c030ecfd45613388a2e6a6a9434dc5d14d9d?context=explore ). ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data -->
GiteaMirror commented 2026-03-07 20:17:36 -06:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Apr 30, 2023):

I suggest to update your docker version.
See https://docs.docker.com/engine/install/ubuntu/

@BlackDex commented on GitHub (Apr 30, 2023): I suggest to update your docker version. See https://docs.docker.com/engine/install/ubuntu/
GiteaMirror commented 2026-03-07 20:17:37 -06:00
Author
Owner
Copy Link

@StepanKuklis commented on GitHub (Apr 30, 2023):

Oh, I see now. You are absolutely right. I didn't checked what is the latest version. After manually updating everything is fine. Sorry for such a silly issue..

@StepanKuklis commented on GitHub (Apr 30, 2023): Oh, I see now. You are absolutely right. I didn't checked what is the latest version. After manually updating everything is fine. Sorry for such a silly issue..
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
documentation
duplicate
enhancement
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
SSO
Third party
troubleshooting
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#5224
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?