# Container image release schedule

**URL:** <https://community.traefik.io/t/container-image-release-schedule/1106>\
**Category:** Traefik v2\
**Tags:** docker\
**Created:** [August 1, 2019, 7:24pm UTC](https://community.traefik.io/t/container-image-release-schedule/1106 "2019-08-01T19:24:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![seh](https://sea2.discourse-cdn.com/flex020/user_avatar/community.traefik.io/seh/32/487_2.png) [@seh](https://community.traefik.io/u/seh)\
**Post date:** [August 1, 2019, 7:24pm UTC](https://community.traefik.io/t/container-image-release-schedule/1106/1 "2019-08-01T19:24:26Z")

</div>

I've noticed that the container images for Traefik version 2 [published to Docker Hub](https://hub.docker.com/_/traefik?tab=tags) come out approximately every 2.5 weeks. Is there some document or GitHub issue query we can follow that would allow us to better understand how far away we are from each release?

Our goal is to track development more closely. When a change gets committed that we'd like to try, should we be building our own image? Is there a "nightly" (or similarly fresh) image published elsewhere that we can use?

---

<div class="post-metadata">

**Author:** ![daniel.tomcej](https://sea2.discourse-cdn.com/flex020/user_avatar/community.traefik.io/daniel.tomcej/32/262_2.png) [@daniel.tomcej](https://community.traefik.io/u/daniel.tomcej)\
**Post date:** [August 1, 2019, 7:59pm UTC](https://community.traefik.io/t/container-image-release-schedule/1106/2 "2019-08-01T19:59:18Z")

</div>

Published releases get pushed when they are ready 😉

Unfortunately the release tracking is internal, so it's not something you can query.

You can always use the `containous/traefik` image, with the experimental tags, that are built off the head of each release branch:

`containous/traefik:experimental-v2.0` will give you the most recent build on the 2.0 release.

Please be aware that this is a development image, and may be subject to change, and is not guaranteed to work, or be functional, as it is not a release image.