Closed jmtaysom closed 6 years ago
Looks to work fine now. It might have been that the JIRA version number was accidentally decremented in the Atlassian JSON feed.
Status: Downloaded newer image for cptactionhank/atlassian-jira:latest
executing as current user
.....
.... .NMMMD. ...
.8MMM. $MMN,..~MMMO.
.?MMM. .MMM?.
OMMMMZ. .,NMMMN~
.IMMMMMM. .NMMMN. .MMMMMN,
,MMMMMM$..3MD..ZMMMMMM.
=NMMMMMM,. .,MMMMMMD.
.MMMMMMMM8MMMMMMM,
.ONMMMMMMMMMMZ.
,NMMMMMMM8.
.:,.$MMMMMMM
.IMMMM..NMMMMMD.
.8MMMMM: :NMMMMN.
.MMMMMM. .MMMMM~.
.MMMMMN .MMMMM?.
Atlassian JIRA
Version : 7.9.2
It seems like last week the latest image switched from 7.9.2 back to 7.9.0. When I pulled the latest it was a lower version than the data in the database so I got the build number conflict issue. When I explicitly pulled the 7.9.2 image it worked just fine.