# Confluence Docker Images: we need a generic "eap" tag **URL:** \ **Category:** Confluence Server\ **Created:** [August 3, 2020, 4:03pm UTC](https://community.developer.atlassian.com/t/confluence-docker-images-we-need-a-generic-eap-tag/40502 "2020-08-03T16:03:44Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![TureHoefner](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/turehoefner/32/38907_2.png) [@TureHoefner](https://community.developer.atlassian.com/u/TureHoefner)\ **Post date:** [August 3, 2020, 4:03pm UTC](https://community.developer.atlassian.com/t/confluence-docker-images-we-need-a-generic-eap-tag/40502/1 "2020-08-03T16:03:44Z")
Atlassian says they have an “eap” label for the latest EAP release: [https://hub.docker.com/r/atlassian/confluence-server/](https://hub.docker.com/r/atlassian/confluence-server/) _“For the latest developer (EAP) release use `atlassian/confluence-server:eap` . This will install our latest milestone (not supported for use in production).”_ It’s not true. There is no such tag in Confluence’s docker hub. We need it. See the tags for the various versions of Confluence server docker images here: [https://hub.docker.com/r/atlassian/confluence-server/tags?page=1&name=eap](https://hub.docker.com/r/atlassian/confluence-server/tags?page=1&name=eap) There is no generic “eap” image so there is no easy way for us to keep an up to date EAP docker image in our test environment. There is a “latest” image and we use that for the latest published version but we need an “eap” label so we don’t have to dig through the various “76-eap-1”, “76-eap-2”, … labels to find the latest EAP image. ---
**Author:** ![BobBergman](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/bobbergman/32/38962_2.png) [@BobBergman](https://community.developer.atlassian.com/u/BobBergman)\ **Post date:** [August 3, 2020, 4:14pm UTC](https://community.developer.atlassian.com/t/confluence-docker-images-we-need-a-generic-eap-tag/40502/2 "2020-08-03T16:14:58Z")
Also note that with Confluence 7.7.0 the `-eap-` naming convention seems to have changed to `-beta-`. This makes it even harder to automate pulling the latest early access image. Please bring some consistency to your image naming conventions. ---
**Author:** ![TureHoefner](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/turehoefner/32/38907_2.png) [@TureHoefner](https://community.developer.atlassian.com/u/TureHoefner)\ **Post date:** [September 7, 2020, 6:43pm UTC](https://community.developer.atlassian.com/t/confluence-docker-images-we-need-a-generic-eap-tag/40502/3 "2020-09-07T18:43:31Z")
Here is a bug for this issue: [[CONFSERVER-60251] Confluence 7.8 EAP Feedback - Create and track feature requests for Atlassian products.](https://jira.atlassian.com/browse/CONFSERVER-60251) ---
**Author:** ![BenPartridge](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/benpartridge/32/38111_2.png) [@BenPartridge](https://community.developer.atlassian.com/u/BenPartridge)\ **Post date:** [September 21, 2020, 11:25pm UTC](https://community.developer.atlassian.com/t/confluence-docker-images-we-need-a-generic-eap-tag/40502/4 "2020-09-21T23:25:27Z")
Thanks for catching this. This is an error in our documentation, I’ve corrected that now. Sorry for the confusion this has caused. We’ve created a ticket to evaluate doing such “:eap” tagging [https://jira.atlassian.com/browse/SCALE-34.](https://jira.atlassian.com/browse/SCALE-34) In the interim, if it’s any easier than watching a page, you can follow the JSON/RSS feed for the latest EAP version across all products as described here: [https://developer.atlassian.com/platform/marketplace/early-access-program/](https://developer.atlassian.com/platform/marketplace/early-access-program/) The EAP version will be the tag for the docker image e.g. confluence-server:7.8.0-beta1