[GH-ISSUE #6619] Docker image tag alpine no longer updated, despite being referenced previously #19259

New Issue

GiteaMirror · 2026-04-25T21:48:11-05:00

GiteaMirror commented

2026-04-25 21:48:11 -05:00

Originally created by @twiesing on GitHub (Dec 29, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6619

Originally assigned to: @dfunkt on GitHub.

Hi,

for many years I have been using the Docker image vaultwarden/server:alpine, as this used to be the standard / recommended Alpine-based image (at least to my knowledge).

Recently I noticed that my instance did not automatically update to version 1.35.0, which resulted in Bitwarden clients showing the following error:

"The client copy of this cipher is out of date. Resync the client and try again."

After investigating, I realized that the tag vaultwarden/server:alpine no longer seems to be updated with new releases. The current Alpine-based image now appears to be published as:

vaultwarden/server:latest-alpine

What confused me is that the vaultwarden/server:alpine image has been referenced by the project maintainer in the past, for example here:

https://github.com/dani-garcia/vaultwarden/issues/1180

Because of this, I assumed the :alpine tag would continue to receive updates. I could not find a clear changelog entry, release note, or documentation update that mentioned the deprecation or replacement of this tag.

As a result, my setup silently stayed on an outdated server version, which only became apparent once clients started showing sync errors.

I’m not sure if I missed an announcement, but I wanted to raise this issue in case it helps improve visibility or documentation for others who might still be using the old :alpine tag.

Thanks for maintaining Vaultwarden and for all the great work!

Originally created by @twiesing on GitHub (Dec 29, 2025). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6619 Originally assigned to: @dfunkt on GitHub. Hi, for many years I have been using the Docker image `vaultwarden/server:alpine`, as this used to be the standard / recommended Alpine-based image (at least to my knowledge). Recently I noticed that my instance did **not** automatically update to version **1.35.0**, which resulted in Bitwarden clients showing the following error: > **"The client copy of this cipher is out of date. Resync the client and try again."** After investigating, I realized that the tag `vaultwarden/server:alpine` no longer seems to be updated with new releases. The current Alpine-based image now appears to be published as: ```text vaultwarden/server:latest-alpine ``` What confused me is that the `vaultwarden/server:alpine` image has been referenced by the project maintainer in the past, for example here: - https://github.com/dani-garcia/vaultwarden/issues/1180 Because of this, I assumed the `:alpine` tag would continue to receive updates. I could not find a clear changelog entry, release note, or documentation update that mentioned the deprecation or replacement of this tag. As a result, my setup silently stayed on an outdated server version, which only became apparent once clients started showing sync errors. I’m not sure if I missed an announcement, but I wanted to raise this issue in case it helps improve visibility or documentation for others who might still be using the old `:alpine` tag. Thanks for maintaining Vaultwarden and for all the great work!

GiteaMirror added the bug label 2026-04-25 21:48:11 -05:00

GiteaMirror closed this issue

2026-04-25 21:48:12 -05:00

GiteaMirror commented

2026-04-25 21:48:14 -05:00

@BlackDex commented on GitHub (Dec 29, 2025):

Thanks for reporting, it seems that this has been skipped indeed.
I have a fix in progress, though, not sure if we can add this tag on the current images easily.

@BlackDex commented on GitHub (Dec 29, 2025): Thanks for reporting, it seems that this has been skipped indeed. I have a fix in progress, though, not sure if we can add this tag on the current images easily.

GiteaMirror commented

2026-04-25 21:48:14 -05:00

@dfunkt commented on GitHub (Dec 29, 2025):

@BlackDex: I already have a PR ready for this if you want to take a look at it.
@twiesing: This was my mistake. Seems like I forgot about this particular line when I refactored the release workflow:
https://github.com/dani-garcia/vaultwarden/blob/main/docker/docker-bake.hcl#L246

# If the base_tag contains latest, and the suffix contains `-alpine` add a `:alpine` tag too
base_tag == "latest" ? suffix == "-alpine" ? ["${registry}:alpine${platform}"] : [] : [],

@dfunkt commented on GitHub (Dec 29, 2025): @BlackDex: I already have a PR ready for this if you want to take a look at it. @twiesing: This was my mistake. Seems like I forgot about this particular line when I refactored the release workflow: https://github.com/dani-garcia/vaultwarden/blob/main/docker/docker-bake.hcl#L246 ``` # If the base_tag contains latest, and the suffix contains `-alpine` add a `:alpine` tag too base_tag == "latest" ? suffix == "-alpine" ? ["${registry}:alpine${platform}"] : [] : [], ```

GiteaMirror commented

2026-04-25 21:48:15 -05:00

@twiesing commented on GitHub (Dec 29, 2025):

@dfunkt No problem :) Thank you for your efforts!

@twiesing commented on GitHub (Dec 29, 2025): @dfunkt No problem :) Thank you for your efforts!

GiteaMirror commented

2026-04-25 21:48:16 -05:00

@crusy commented on GitHub (Dec 29, 2025):

Thank you, that was fast! Noobie question, though: Will this merge automatically (or manually, for that matter) trigger an update of the docker image? Or do we have to wait for a future release?

@crusy commented on GitHub (Dec 29, 2025): Thank you, that was fast! Noobie question, though: Will this merge automatically (or manually, for that matter) trigger an update of the docker image? Or do we have to wait for a future release?

GiteaMirror commented

2026-04-25 21:48:16 -05:00

@dani-garcia commented on GitHub (Dec 29, 2025):

We don't have an easy way to retroactively tag the release, but we have plans for a new .1 release containing this and #6629 in the next couple of days

@dani-garcia commented on GitHub (Dec 29, 2025): We don't have an easy way to retroactively tag the release, but we have plans for a new .1 release containing this and #6629 in the next couple of days

GiteaMirror commented

2026-04-25 21:48:17 -05:00

@dani-garcia commented on GitHub (Dec 30, 2025):

alpine tag should be updated again with release 1.35.1

@dani-garcia commented on GitHub (Dec 30, 2025): `alpine` tag should be updated again with release `1.35.1`

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#19259