Did someone forget the docker image for Confluence 7.18.2?

Confluence Development Confluence Server
1

The Confluence docker image for the “latest” tag is Confluence 7.18.1:
https://hub.docker.com/r/atlassian/confluence-server/tags?page=1&name=latest

but the latest release is 7.18.2:
https://confluence.atlassian.com/doc/issues-resolved-in-7-18-2-1141481868.html

Did someone forget to update the docker image or is this a normal delay?

We can’t really tolerate too much delay in the “latest” docker image (more than a few hours) because our apps are all now a release behind in the compatibility setting in MPAC and we’d like to smoke test each new release before we update the compat… and we rely on the docker image for updating our test servers…

Thanks.

1 Like
2

It appears that someone updated the image. It is downloading now when I “docker-compose pull”

If anyone from Atlassian sees this please look into this because we received several customer requests to update our app compatibility. The customers who are diligent about upgrading Confluence and their plugins notice outdated compat immediately.

Thanks.

3

Hey @turehoefner_appfire,

We didn’t forget to update the docker image, there’s just an expected amount of delay in the process.

There’s up to an hour delay in pushing the image to our internal docker repositories, then there are some additional checks that occur between there and pushing it to docker hub. Generally this process is pretty quick, but it is possible for it to run into delays.

We’d expect to measure this delay in hours (depending on all kinds of timings), so anything beyond that would be unexpected.

If the images aren’t appearing sufficiently rapidly for you, there’s always the option to build the image locally using https://bitbucket.org/atlassian-docker/docker-atlassian-confluence-server/src/master/

Thanks,
James Ponting
Engineering Manager - Confluence Data Center

4

Hey @turehoefner_appfire,

To close the loop here, it turns out we were in the process of rebasing all of our docker images, and the releases got stuck in a queue to be processed. The Docker release ended up being roughly 24 hours after the actual release, so your timing was about right.

Given rebasing is a rare action, and rarer still that it would occur at the same point we are pushing ad hoc releases, I’d expect this won’t happen again (even if I jinxed it by saying this).

Thanks,
James Ponting
Engineering Manager - Confluence Data Center