Enable Docker Wordpress image to start new WordPress container directly with SQLite

It has been very silent around the sqlite integration. I think a lot more people might test it, if the setup would not require an additional external database to start. I tried to create a Dockerfile using FROM Wordpress:latest, but it seems there are a couple of challenges.

To get a smooth experience, we need

1. Integration of the required SQLite dependencies into the Docker WordPress image (Dockerfile)
   (sqlite3, libsqlite3-dev, php-sqlite3, pdo_sqlite?)
2. Enable install of WP SQLite plugin during first startup, maybe by using an ENV VAR (docker-entrypoint.sh)
3. Skip required MYSQL during setup, maybe by using an ENV VAR (setup-config.php)
4. Add the necessary SQLite settings, maybe by using an ENV VAR (probably in setup-config.php)

It doesn't look too complicated to me, it just needs a coordinated effort. Who can implement those changes (shell, php) and who is controlling those files to update them? How is the regular process? Who needs to agree to this?

The Docker Wordpress image size is 230MB, I don't think the SQL dependencies of around 1-3MB really matter. And I assume if not used, they should not introduce any kind of security issue.

Imagine you can spin up a new Wordpress with a simple example docker-compose.yml for wordpress:

services:
  wordpress:
    image: wordpress
    restart: always
    ports:
      - 8080:80
    environment:
      WORDPRESS_USE_SQLITE: true
    volumes:
      - wordpress:/var/www/html

Start by reviewing the linked Dockerfile, docker-entrypoint.sh, and WordPress setup-config.php to understand where the requested SQLite dependencies, plugin installation, and setup behavior belong. Use the example docker-compose.yml as the acceptance scenario: a new WordPress container should start with WORDPRESS_USE_SQLITE enabled without requiring an external MySQL database.