MySQL deployment issue on IBM Cloud’s Managed Kubernetes Service due to lost+found directory




MySQL Statefulset manifest
2019-08-25T15:36:470279Z 0 [ERROR] --initialize specified but the data directory has files in it. Aborting2019-08-09T15:36:470367Z 0 [ERROR] Aborting 
mysql container’s entrypoint script checks if DATADIR/mysql (in my case it was /var/lib/mysql) exists. If not, it run --initialize, but if DATADIR/mysql contains any files other than ones starting with . or specified with --ignore-db-dir, --initialize will fail with the above error message.

What purpose does lost+found serve?


Init container manifest
Final MySQL manifest for IBM Cloud

MySQL Data Backup

Final Thoughts

DevSecOps Engineer

DevSecOps Engineer