Latest Bitbucket Docker image unable to roll out to SQL 2016 database due to locking issues

Steps to reproduce

1.)Create "bitbucket" database on a SQL 2016 instance (named instance in this test):

CREATE DATABASE bitbucket
GO
USE bitbucket
GO
ALTER DATABASE bitbucket SET ALLOW_SNAPSHOT_ISOLATION ON
GO
ALTER DATABASE bitbucket SET READ_COMMITTED_SNAPSHOT ON
GO
ALTER DATABASE bitbucket COLLATE SQL_Latin1_General_CP1_CS_AS
GO
SET NOCOUNT OFF
GO
USE master
GO
CREATE LOGIN bitbucketuser WITH PASSWORD=N'blahblah', DEFAULT_DATABASE=bitbucket, CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF
GO
ALTER AUTHORIZATION ON DATABASE::bitbucket TO bitbucketuser
GO

2.)Retrieve and launch latest Bitbucket Docker image:

docker run --privileged=true -v /stage/bitbucket:/var/atlassian/application-data/bitbucket --name="bitbucket" -d -p 80:7990 -p 7999:7999 atlassian/bitbucket-server

3.)Create a bitbucket.properties file under $BITBUCKET_HOME/shared to allow the use of a SQL Server named instanced:

tee /stage/bitbucket/shared/bitbucket.properties <<-'EOF'
jdbc.driver=com.microsoft.sqlserver.jdbc.SQLServerDriver
jdbc.url=jdbc:sqlserver://INNO-JFWINAPP01.eagleinvsys.com\SQL2016;databaseName=bitbucket
jdbc.user=bitbucketuser
jdbc.password=blahblah
EOF

4.)Upon launching the UI, the database schema/object rollout from Liquidbase will fail with locking issues (see attached log).