It's caused by the docker container installing the older version of SickRage upon startup. I get around it by renaming the 'sickbeard.db' file to something else(ie 'sickbeard.db.tmp', then letting SickRage start up, then update internally(the top message bar says something about 230 commits behind). After SickRage comes back, I delete the new 'sickbeard.db' file, and rename the 'sickbeard.db.tmp' file back to 'sickbeard.db' then restart SickRage via the tool tab on SickRage's webpage.