As an Administrator I would like to upgrade my Bitbucket Mirror Container without recreating it

At present, as per documentation in our Docker Hub, we should be able to upgrade Bitbucket Server and Data Center instances running on the Docker container. Unfortunately, there is no procedure available for Bitbucket Mirror instances, running on Docker Containers, as Bitbucket Mirror instances use a totally different profile for Bitbucket and there are a lot of variables and peculiarities that surround it, like SSH Keys and the H2 Database. So, whenever you bring up a new docker container, with a new version of Bitbucket, lots of things related to that container are refreshed, even though you have the same volume in place. That's why we see issues like the following log snippet:

Registration with the upstream server failed (A request to the configured upstream was rejected as untrusted. (Status code: 401, message: '')). Retrying in 10s

That basically tells you that the upstream server cannot recognize that instance anymore, as it thinks it is not legit

What is expected?

To be able to upgrade the Bitbucket Mirror instance, running on Docker, to a new version without having to recreate it.

What is currently happening?

Bitbucket Mirror instance is not working anymore once we upgrade the docker instance to run with a new version, using the same volume, getting an unauthorized error for that upgraded mirror instance.

Workaround

The only workaround available is to re-create / re-register the mirror once again, and that is not what we expect to do that using docker containers.
There should be a way of upgrading it to a new version without having to recreate/re-register it.