Docker atlassian/confluence-server container shows version 6.15.2 but tag is 6.15.8

[Justin Monti]

Based on the recent critical security vulnerability notification, I was trying to upgrade our Confluence server to 6.15.8. This runs in a Docker container and we use the Atlassian official builds from Docker Hub.  Below is the Image line from our Docker Compose file.

 image: atlassian/confluence-server:ubuntu-18.04-adoptopenjdk8

However, when it starts up we see the below message in the log and the UI also reports the version as 6.15.2.

2019-08-29 02:58:05,784 INFO [Catalina-utility-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 6.15.2 [build 8100 based on commit hash 4410012ac87e845516b70bc69b6f7a893eabaa5a] - synchrony version 2.1.0-master-9d112c9d

I also tried this with the :6.15.8 tag and 6.15-ubuntu-18.04-adoptopenjdk8 tag with the same results... 

Any idea why it would be reporting this older version?

[Dave Chevell · Accepted solution]

Hi Justin,

I'm not able to reproduce this:

$ docker run atlassian/confluence-server:6.15.8-adoptopenjdk8 2>&1 | grep "Starting Confluence"
2019-09-04 22:16:16,219 INFO [Catalina-utility-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 6.15.8 [build 8100 based on commit hash 6ef1ce95c788ac159314a8fa6387047b8d1cc9fb] - synchrony version 2.1.0-release-confluence_6.15-32f7299a

 Note that 6.15.9 has been released, so when using the generic tag you mentioned, 5.16.9 is now shown:

docker run atlassian/confluence-server:ubuntu-18.04-adoptopenjdk8 2>&1 | grep "Starting Confluence"
2019-09-04 22:19:57,687 INFO [Catalina-utility-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 6.15.9 [build 8100 based on commit hash 5084f018d64a97dc638ca9a178856f851ea353ff] - synchrony version 2.1.0-release-confluence_6.15-32f7299a

Would you be able to test this again and report back?

Cheers,

Dave

[Justin Monti]

Dave,

OK, turns out I had the entire /opt/atlassian/confluence/confluence/WEB-INF being mounted from my host into the Docker container - thus even though I was pulling the new container, the jars under here were taking over keeping me at 6.15.2 which was the original version it was built with.

Once I changed the volume mount to address the specific Duo plugin JAR files and web.xml file, it started up and correctly showed version 6.15.9

Thanks for the help and thanks for the Docker images - a huge help to have these official images!

Justin