bitwarden-mssql 2026.6.1 container crashes immediately on startup (2026.6.0 works)

[puni2k]

Steps To Reproduce

Description

After upgrading Bitwarden self-hosted stack to 2026.6.1, the MSSQL container (ghcr.io/bitwarden/mssql:2026.6.1) fails to start and enters a restart loop.

Downgrading to 2026.6.0 resolves the issue immediately with no changes to data.

Steps to reproduce
Run Bitwarden self-hosted installation (Docker-based)
Update to version 2026.6.1
Start stack:
./bitwarden.sh start
Observe MSSQL container:
docker ps -a | grep mssql

Result:

Container constantly restarts (Restarting (1))

errorlog

2026-06-28 00:00:01.03 Backup Database backed up. Database: vault, creation date(time): 

2022/08/30(08:25:55), pages dumped: 1211, first LSN: 53:18294:1, last LSN: 53:18297:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'/etc/bitwarden/mssql/backups/vault_FULL_20260628_000000.BAK'}). This is an informational message only. No user action is required. 

2026-06-28 00:00:01.07 Backup BACKUP DATABASE successfully processed 1201 pages in 0.230 seconds (40.767 MB/sec). 2026-06-28 02:00:04.62 spid13s Always On: The availability replica manager is going offline because SQL Server is shutting down. This is an informational message only. No user action is required. 

2026-06-28 02:00:04.62 spid13s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required. 

2026-06-28 02:00:04.63 spid13s .NET Framework runtime has been stopped. 

2026-06-28 02:00:04.76 spid13s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
<EOF>

Ubuntu 24.04.4 LTS
Capture info: Processor topology
Capture info: Process mounts
Capture info: Process statistics
Capture info: Process status
Capture info: Process memory maps
Capture info: Process memory maps (detailed)
Capture info: Core Dump filter
Capture info: Process CGroup information
Capture info: Process scheduler information
Capture info: Process list
Capture info: Process handle information
Capture info: Process environment variables
Capture info: System package list (dpkg)
Capture info: Current application configuration
Sun Jun 28 05:41:24 UTC 2026 Capturing program information
Sun Jun 28 05:41:25 UTC 2026 Attempting to capture a dump with paldumper for pid 43
WARNING: Capture attempt failure detected
Attempting to capture a filtered dump with paldumper for pid 43
WARNING: Attempt to capture dump failed.  Reference /var/opt/mssql/log/core.sqlservr.43.temp/log/paldumper-debug.log for details
Sun Jun 28 05:41:25 UTC 2026 Attempting to capture a dump with gdb
WARNING: Unable to capture crash dump with GDB. You may need to
allow ptrace debugging, enable the CAP_SYS_PTRACE capability, or
run as root. See log in: /var/opt/mssql/log/core.sqlservr.43.temp/log/gdb.log
Sun Jun 28 05:41:26 UTC 2026 Capturing program binaries
Sun Jun 28 05:41:26 UTC 2026 Not compressing the dump files, moving instead to: /var/opt/mssql/log/core.sqlservr.06_28_2026_05_41_23.43.d
Executing: /opt/mssql/bin/handle-crash.sh with parameters
     handle-crash.sh
     /opt/mssql/bin/sqlservr
     39
     /opt/mssql/bin
     /var/opt/mssql/log/
     
     764625d2-e5b1-4857-858c-d68550f3b72e
     8a7ae74c-e68c-42f7-b9c3-6a99d5087594

bitwarden@bitwarden:/opt/bitwarden/bwdata/logs/mssql$ less core.sqlservr.6_28_2026_6_43_56.39.log
06/28/2026 06:43:56.133329547 Info [paldumper] <0000000040/0x00000000> Executing PalDumper against PID: 39
06/28/2026 06:43:56.133372218 Info [paldumper] <0000000040/0x00000000>                       Dump type: miniplus
06/28/2026 06:43:56.133380634 Info [paldumper] <0000000040/0x00000000> Stopping target
06/28/2026 06:43:56.133393097 Info [paldumper] <0000000040/0x00000000> Target stopped
06/28/2026 06:43:56.133399650 Info [paldumper] <0000000040/0x00000000> Attaching to target threads
06/28/2026 06:43:56.133469071 Warning [paldumper] <0000000040/0x00000000> Yama PTRACE mode: 1-Restricted
06/28/2026 06:43:56.133644863 Info [paldumper] <0000000040/0x00000000>   Ptrace command for pid 39: succeeded
06/28/2026 06:43:56.133694587 Info [paldumper] <0000000040/0x00000000>   Ptrace command for pid 42: succeeded
06/28/2026 06:43:56.133737447 Info [paldumper] <0000000040/0x00000000>   Ptrace command for pid 43: succeeded
06/28/2026 06:43:56.133779116 Info [paldumper] <0000000040/0x00000000>   Ptrace command for pid 44: succeeded
06/28/2026 06:43:56.133796499 Info [paldumper] <0000000040/0x00000000> Parsing /proc/39/smaps for region coverage
06/28/2026 06:43:56.152994690 Info [paldumper] <0000000040/0x00000000> Virtual memory region count: 300
06/28/2026 06:43:56.153017193 Info [paldumper] <0000000040/0x00000000>     Using ThreadInfo::m_Head at: 0x000064483B784788
06/28/2026 06:43:56.153021311 Info [paldumper] <0000000040/0x00000000>     Using ProcessList at: 0x00003FFF9CDD16B0
06/28/2026 06:43:56.153024887 Info [paldumper] <0000000040/0x00000000>      Using m_ProtocolVersion at: 0x000064483B783310
06/28/2026 06:43:56.153028274 Info [paldumper] <0000000040/0x00000000>      Using sm_SOSNodeManager at: 0x00003FFF9CD90340
06/28/2026 06:43:56.153031630 Info [paldumper] <0000000040/0x00000000>   Using sm_MemoryNodeManager at: 0x00003FFF9CD905F0
06/28/2026 06:43:56.153035036 Info [paldumper] <0000000040/0x00000000> Using sm_GlobalSchedulerList at: 0x00003FFF9CD905C0
06/28/2026 06:43:56.153038453 Info [paldumper] <0000000040/0x00000000>        Using ELF module list at: 0x00007D8F7559F2E0
BEGIN IMAGE LIST
linux-vdso.so.1
/lib/x86_64-linux-gnu/libnuma.so.1
/lib/x86_64-linux-gnu/libgssapi_krb5.so.2
/lib/x86_64-linux-gnu/libkrb5.so.3
/lib/x86_64-linux-gnu/libk5crypto.so.3
/lib/x86_64-linux-gnu/libcom_err.so.2
/lib/x86_64-linux-gnu/libsss_nss_idmap.so.0
/lib/x86_64-linux-gnu/libuuid.so.1
/lib/x86_64-linux-gnu/libpam.so.0
/lib/x86_64-linux-gnu/libm.so.6
/lib/x86_64-linux-gnu/liblber.so.2
/lib/x86_64-linux-gnu/libldap.so.2
/lib/x86_64-linux-gnu/libudev.so.1
/lib/x86_64-linux-gnu/libssl.so.3
/lib/x86_64-linux-gnu/libcrypto.so.3
/opt/mssql/lib/libc++.so.1
/opt/mssql/lib/libc++abi.so.1
/lib/x86_64-linux-gnu/libgcc_s.so.1
/lib/x86_64-linux-gnu/libc.so.6
/lib64/ld-linux-x86-64.so.2
bitwarden@bitwarden:/opt/bitwarden/bwdata/logs/mssql$ 


itwarden@bitwarden:/opt/bitwarden/bwdata/logs/mssql/core.sqlservr.06_28_2026_06_43_56.39.d$ less crash.txt 
This program has encountered a fatal error and cannot continue running at Sun Jun 28 06:43:56 2026
The following diagnostic information is available:

         Reason: 0x00000004
        Message: ASSERT: Expression=(NT_SUCCESS(status)) File=LibOS\Windows\Kernel\DRtl\sqlpalstubs.cpp Line=887
    Stack Trace:
                 file://package6/windows/system32/sqlpal.dll+0x000000000000A5D6
                 file://package6/windows/system32/sqlpal.dll+0x0000000000009909
                 file://package6/windows/system32/sqlpal.dll+0x00000000000055D4
                 file://package6/windows/system32/sqlpal.dll+0x0000000000005465
                 file://package6/windows/system32/sqlpal.dll+0x00000000000E8F54
                 file://package6/windows/system32/sqlpal.dll+0x00000000000AB031
                 file://package6/windows/system32/sqlpal.dll+0x00000000000AB6E4
                 file://package6/windows/system32/sqlpal.dll+0x00000000000AAC2A
                 file://package6/windows/system32/sqlpal.dll+0x00000000000AD050
                 file://package6/windows/system32/sqlpal.dll+0x0000000000006FCC
                 file://package6/windows/system32/sqlpal.dll+0x00000000000065CE
                 file://package6/windows/system32/sqlpal.dll+0x0000000000006A59
                 file://package6/windows/system32/sqlpal.dll+0x0000000000122651
        Process: 39 - sqlservr
         Thread: 44 (application thread 0x8)
    Instance Id: 3b567007-9e95-444b-adc0-d17ed827ff38
       Crash Id: 85b15a91-2576-4974-b2fe-7b7e155f7224
    Build stamp: a9417035daf3b2a89a07f56779392396b49edc6d655162ab6d7ffb0aa99e12d9
   Distribution: Ubuntu 24.04.4 LTS
     Processors: 2
   Total Memory: 134904156160 bytes
      Timestamp: Sun Jun 28 06:43:56 2026
     Last errno: 22
Last errno text: Invalid argument

Expected Result

MSSQL container starts successfully
SQL Server initializes normally
Bitwarden services connect to database
No restart loop

Actual Result

MSSQL container exits immediately on startup
No login possible, browser addon cannot connect to vault
No usable SQL Server ERRORLOG is generated
Only crash dump / paldumper logs appear
Container never reaches normal SQL initialization

Screenshots or Videos

No response

Additional Context

No response

Build Version

2026.6.1

Environment

Self-Hosted

Environment Details

Proxmox PVE 8.4.19 LXC container
Linux bitwarden 6.8.12-30-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-30 (2026-06-11T10:10Z) x86_64 GNU/Linux
Docker version 29.6.1, build 8900f1d

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-39719
Link (for internal use): https://bitwarden.atlassian.net/browse/PM-39719

[rmcdowell-bitwarden]

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

[puni2k]

Some additional information that may help narrow this down.

2026.6.1 includes PR #7806, which updates the MSSQL container from SQL Server 2022-CU22 on Ubuntu 22.04 to SQL Server 2025-CU5 on Ubuntu 24.04.

In my environment, rolling back only the bitwarden/mssql image to 2026.6.0 immediately restores functionality using the exact same database, volumes and Bitwarden configuration. Replacing it with 2026.6.1 consistently causes the SQL Server container to fail during startup.

From the crash dump of the failing container. The relevant part is:

ASSERT: Expression=(NT_SUCCESS(status))
File=LibOS\Windows\Kernel\DRtl\sqlpalstubs.cpp
Last errno: 22 (Invalid argument)

My deployment runs Docker inside an unprivileged Proxmox VE 8 LXC container (Debian 12). Has been doing so for years.

I can't say whether the LXC environment is the root cause, but given that the regression coincides with the SQL Server/Ubuntu base image update, and the assertion occurs in SQLPAL before SQL Server fully initializes, it may be worth investigating whether there is a compatibility regression with this environment.

If it helps, I'm happy to test candidate images or provide additional logs.

Edit: I think that in the meantime a SQL Server 2025-CU6 image has become available

[djc0739]

I am having the same issue when upgrading from 2026.6.0 to 2026.6.1. Reverting back to 2026.6.0 corrected the issue.

I am running the full version of Bitwarden in a Docker Container on a Synology NAS running DSM 7.3 and have been for about 5 years without issue.

When running the update I see the following error:

Unhandled exception. Microsoft.Data.SqlClient.SqlException (0x80131904): A netwo rk-related or instance-specific error occurred while establishing a connection t o SQL Server. The server was not found or was not accessible. Verify that the in stance name is correct and that SQL Server is configured to allow remote connect ions. (provider: TCP Provider, error: 35 - An internal exception was caught)
---> System.Net.Sockets.SocketException (00000001, 11): Resource temporarily un available
at System.Net.Dns.GetHostEntryOrAddressesCore(String hostName, Boolean justAd dresses, AddressFamily addressFamily, Nullable1 activityOrDefault) at System.Net.Dns.GetHostAddresses(String hostNameOrAddress, AddressFamily fa mily) at Microsoft.Data.SqlClient.ManagedSni.SniTcpHandle.GetHostAddressesSortedByP reference(String serverName, SqlConnectionIPAddressPreference ipPreference)+Move Next() at Microsoft.Data.SqlClient.ManagedSni.SniTcpHandle.Connect(String serverName , Int32 port, TimeoutTimer timeout, SqlConnectionIPAddressPreference ipPreferenc e, String cachedFQDN, SQLDNSInfo& pendingDNSInfo) at Microsoft.Data.SqlClient.ManagedSni.SniTcpHandle..ctor(String serverName, Int32 port, TimeoutTimer timeout, Boolean parallel, SqlConnectionIPAddressPrefer ence ipPreference, String cachedFQDN, SQLDNSInfo& pendingDNSInfo, Boolean tlsFir st, String hostNameInCertificate, String serverCertificateFilename) at Microsoft.Data.SqlClient.Connection.SqlConnectionInternal.OnError(SqlExcep tion exception, Boolean breakConnection, Action1 wrapCloseInAction)
at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserState Object stateObj, SqlCommand command, Boolean callerHasConnectionLock, Boolean as yncClose)
at Microsoft.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlConne ctionInternal connHandler, TimeoutTimer timeout, SqlConnectionString connectionO ptions, Boolean withFailover)
at Microsoft.Data.SqlClient.Connection.SqlConnectionInternal.AttemptOneLogin( ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Timeo utTimer timeout, Boolean withFailover)
at Microsoft.Data.SqlClient.Connection.SqlConnectionInternal.LoginNoFailover( ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boole an redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
at Microsoft.Data.SqlClient.Connection.SqlConnectionInternal.OpenLoginEnlist( TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential crede ntial, String newPassword, SecureString newSecurePassword, Boolean redirectedUse rInstance)
at Microsoft.Data.SqlClient.Connection.SqlConnectionInternal..ctor(DbConnecti onPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential cr edential, DbConnectionPoolGroupProviderInfo providerInfo, String newPassword, Se cureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionStrin g userConnectionOptions, SessionData reconnectSessionData, Boolean applyTransien tFaultHandling, String accessToken, IDbConnectionPool pool, Func3 accessTokenCa llback, SspiContextProvider sspiContextProvider) at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectio nOptions options, DbConnectionPoolKey poolKey, DbConnectionPoolGroupProviderInfo poolGroupProviderInfo, IDbConnectionPool pool, DbConnection owningConnection, D bConnectionOptions userOptions) at Microsoft.Data.SqlClient.SqlConnectionFactory.CreatePooledConnection(DbCon nection owningConnection, IDbConnectionPool pool, DbConnectionPoolKey poolKey, D bConnectionOptions options, DbConnectionOptions userOptions) at Microsoft.Data.SqlClient.ConnectionPool.WaitHandleDbConnectionPool.CreateO bject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionIn ternal oldConnection) at Microsoft.Data.SqlClient.ConnectionPool.WaitHandleDbConnectionPool.UserCre ateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnect ionInternal oldConnection) at Microsoft.Data.SqlClient.ConnectionPool.WaitHandleDbConnectionPool.TryGetC onnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boole an allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) at Microsoft.Data.SqlClient.ConnectionPool.WaitHandleDbConnectionPool.TryGetC onnection(DbConnection owningObject, TaskCompletionSource1 taskCompletionSource , DbConnectionOptions userOptions, DbConnectionInternal& connection)
at Microsoft.Data.SqlClient.SqlConnectionFactory.TryGetConnection(DbConnectio n owningConnection, TaskCompletionSource1 retry, DbConnectionOptions userOption s, DbConnectionInternal oldConnection, DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal (DbConnection outerConnection, SqlConnectionFactory connectionFactory, TaskCompl etionSource1 retry, DbConnectionOptions userOptions)
at Microsoft.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnect ion outerConnection, SqlConnectionFactory connectionFactory, TaskCompletionSourc e1 retry, DbConnectionOptions userOptions) at Microsoft.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource1 retry)
at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retr y, SqlConnectionOverrides overrides)
at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrid es)
at Microsoft.Data.SqlClient.SqlConnection.Open()
at Bit.Migrator.DbMigrator.PrepareDatabase(CancellationToken cancellationToke n) in /source/util/Migrator/DbMigrator.cs:line 89
at Bit.Migrator.DbMigrator.MigrateMsSqlDatabaseWithRetries(Boolean enableLogg ing, Boolean repeatable, String folderName, Boolean dryRun, CancellationToken ca ncellationToken) in /source/util/Migrator/DbMigrator.cs:line 45
at Bit.Setup.Program.PrepareAndMigrateDatabase() in /source/util/Setup/Progra m.cs:line 278
at Bit.Setup.Program.Update(Application application) in /source/util/Setup/Pr ogram.cs:line 242
at Bit.Setup.Program.MainCore(String[] args, Application application) in /sou rce/util/Setup/Program.cs:line 77
at Bit.Setup.Program.Main(String[] args) in /source/util/Setup/Program.cs:lin e 28
ClientConnectionId:00000000-0000-0000-0000-000000000000
Error Number:11002,State:0,Class:20

[grafnull]

I also have the same issue on Almalinux 9 with all system updates applied. Reverting back to the previous version works.

[tommy-ng0]

Same here on Debian bullseye. Reverted back to ghcr.io/bitwarden/mssql:2026.6.0 work

[Steffenkt]

I ran into the same crash on my end, running Bitwarden inside a Proxmox LXC container (Ubuntu Server 24.04). I can't say for certain yet whether it's related to a recent Proxmox update or something specific to the LXC environment itself.

Downgrading to 2026.6.0 wasn't an option for me, since the database had already been upgraded and there's no supported downgrade path.

What did work was moving the whole setup to a regular Ubuntu VM instead of the LXC container. After that, mssql started up without any issues right away. So my guess is that this is more of an LXC related problem than an actual bug in Bitwarden itself.

[grafnull]

I run it directly on an Almalinux root server. So it is not limited to VM Systems or containers.

[brouna]

Same issue on Proxmox 9.2.3, LXC Ubuntu 24.04.4 LTS

[puni2k]

I did some additional tests in my environment with the plain MSSQL image on an otherwise virgin set of containers:

mcr.microsoft.com/mssql/server:2025-CU5-ubuntu-24.04 (bundled with bitwarden-mssql 2026.1) - crashes on startup
mcr.microsoft.com/mssql/server:2025-CU6-ubuntu-24.04 (latest 2025 version) - crashes on startup
mcr.microsoft.com/mssql/server:2025-CU6-ubuntu-22.04 (latest 2025 version but older base image) - crashes on startup
mcr.microsoft.com/mssql/server:2022-CU25-ubuntu-22.04 (latest 2022 version) - works

Edit:
Found this reference stating that MSSQL 2025 has compatibility issues with Proxmox PVE 9 LXC containers community-scripts/ProxmoxVE#11824 (comment)
However it also states that PVE 8 should not be affected.

[djc0739]

Can Bitwarden please provide a status update with some estimated timeline for correcting this issue?

Thanks.

[puni2k]

Another small tidbit.
I migrated my bitwarden installation to a fresh QEMU VM running Debian 13 on PVE8:

Linux bitwarden 6.12.95+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.95-1 (2026-07-04) x86_64 GNU/Linux

There 2026.6.1 ( including ghcr.io/bitwarden/mssql:2026.6.1 ) seems to run fine so far.
However i just see this as a workaround.