empty sqlite database after migration

try this cmd and after try to migrate it.

php artisan config:clear

try the following

Check Database Path: Ensure that the database.sqlite file is in the correct location and that Laravel is indeed using this file for SQLite. Sometimes, the file might be created in a different directory if the path is not specified correctly.

Check Migrations: Confirm that your migrations are running correctly and actually creating the tables in the SQLite database. You can check this by looking at the migration files in the database/migrations directory and comparing them with your database schema in TablePlus.
Check Connection: Double-check your .env file to ensure that the DB_CONNECTION is set to sqlite. Also, make sure that there are no other conflicting database configurations that might be causing Laravel to use a different database driver.

File Permissions: Since you mentioned setting chmod 777 for the database.sqlite file, permissions shouldn't be an issue. However, ensure that the file is accessible and writable by the web server or the user running the Laravel commands.

Clear Cache: Sometimes, Laravel's cache can cause issues with database connections or migrations. Try running php artisan cache:clear and php artisan config:clear to clear any cached configurations.

Reset Database: If none of the above solutions work, you can try resetting the database entirely. Run php artisan migrate:fresh to drop all tables and then migrate again with php artisan migrate.

Check Docker Settings: Since you're using Docker and WSL2, ensure that your Docker setup is correctly configured to mount the Laravel project directory and that there are no issues with file paths or permissions within Docker.

Ensure that the path to the SQLite database file in your Laravel project is correctly configured for the WSL2 environment. This means that the path should be something like /mnt/c/path/to/your/project/database.sqlite if your project is located in the Windows filesystem (C:\path\to\your\project).

Also, Check the permissions of the SQLite database file within the WSL2 environment. Use the ls -l command in the terminal to view the permissions. The file should be accessible and writable by the user running the Laravel commands (www-data or your WSL2 user).