MariaDB container managed by Frappe Manager enters a restart loop due to InnoDB failing to acquire an exclusive lock on ibdata1 (error: 11). The failure occurs during startup and persists across restarts when using a bind-mounted datadir on WSL2 + Docker Desktop.
Observed behavior
InnoDB: Unable to lock ./ibdata1 error: 11
InnoDB: Plugin initialization aborted
ERROR: Unknown/unsupported storage engine: InnoDB
Container enters continuous restart loop.
Expected behavior
MariaDB should initialize successfully and acquire required InnoDB locks on ibdata1.
System information:
Frappe Manager: 19.0.0
Docker Desktop: 4.73.1
Additional context
Environment: WSL2 (Ubuntu 24.04) on Windows 11
Docker Desktop with WSL integration
MariaDB 10.6 container
Issue only occurs with bind-mounted /var/lib/mysql
Switching to a Docker named volume resolves the issue, suggesting a filesystem locking incompatibility in WSL2 bind mounts under crash recovery conditions
MariaDB container managed by Frappe Manager enters a restart loop due to InnoDB failing to acquire an exclusive lock on ibdata1 (error: 11). The failure occurs during startup and persists across restarts when using a bind-mounted datadir on WSL2 + Docker Desktop.
Observed behavior
InnoDB: Unable to lock ./ibdata1 error: 11
InnoDB: Plugin initialization aborted
ERROR: Unknown/unsupported storage engine: InnoDB
Container enters continuous restart loop.
Expected behavior
MariaDB should initialize successfully and acquire required InnoDB locks on ibdata1.
System information:
Frappe Manager: 19.0.0
Docker Desktop: 4.73.1
Additional context
Environment: WSL2 (Ubuntu 24.04) on Windows 11
Docker Desktop with WSL integration
MariaDB 10.6 container
Issue only occurs with bind-mounted /var/lib/mysql
Switching to a Docker named volume resolves the issue, suggesting a filesystem locking incompatibility in WSL2 bind mounts under crash recovery conditions