# Latest versions of containers for a given update (self-hosted)?

**URL:** <https://community.bitwarden.com/t/latest-versions-of-containers-for-a-given-update-self-hosted/63723>\
**Category:** Password Manager\
**Tags:** app:all, server:selfhost\
**Created:** [February 21, 2024, 3:58pm UTC](https://community.bitwarden.com/t/latest-versions-of-containers-for-a-given-update-self-hosted/63723 "2024-02-21T15:58:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bclingan](https://sea1.discourse-cdn.com/flex001/user_avatar/community.bitwarden.com/bclingan/32/21129_2.png) [@bclingan](https://community.bitwarden.com/u/bclingan)\
**Post date:** [February 21, 2024, 3:58pm UTC](https://community.bitwarden.com/t/latest-versions-of-containers-for-a-given-update-self-hosted/63723/1 "2024-02-21T15:58:37Z")

</div>

When a new version is released, is it listed anywhere what versions of the various container components are for a given release? The docker file I believe tends to use the latest tag. In our configuration as code environment, we prefer to specify versions to control what is being deployed. I know I can manually go look but is a little tedious given the number of containers. I only ask because I’ve noticed not every component gets incremented every time.

---

<div class="post-metadata">

**Author:** ![Nail1684](https://sea1.discourse-cdn.com/flex001/user_avatar/community.bitwarden.com/nail1684/32/47626_2.png) [@Nail1684](https://community.bitwarden.com/u/Nail1684)\
**Post date:** [January 23, 2026, 12:57am UTC](https://community.bitwarden.com/t/latest-versions-of-containers-for-a-given-update-self-hosted/63723/2 "2026-01-23T00:57:02Z")

</div>

Closed on January 23, 2026, 12:57am UTC