conversion over docker

docker conversion is broken, the image is not valid (gpg keys), using a mac here

so changed first line in Dockerfile to (debian compatible distribution):

`FROM bitnami/minideb:latest`

then I'am able to create the image

`cd tuya-convert && docker build -t tuya:latest .`

then went into the container

`mkdir newFolder && cd newFolder && docker run -t -i --privileged --network="host" tuya:latest /bin/bash`

from the dockerfile, the files "**config.sh**, **start**, **stop**" are copied to the **/usr/bin** folder...
and the tuya-convert folder contents to **/usr/bin/tuya-convert**
**start** script just calls **./start_flash.sh** inside the tuya-convert folder, so..

`cd /usr/bin/tuya-convert && bash start_flash.sh`

then I got an error not finding **pkill**, and **tput** :) one more dependency to add to Dockerfile

`apt-get install procps ncurses-bin`

then the error! does the mac doesn't support the ap mode?
I just dont understand the "nl80211 not found." same when running `iw list`
default if driver?
any suggestions?

```
root@docker-desktop:/usr/bin/tuya-convert# bash start_flash.sh
tuya-convert v2.4.5
nl80211 not found.
AP mode not supported!
Please attach a WiFi card that supports AP mode.
======================================================
Cleaning up...
No screen session found.
No screen session found.
No screen session found.
No screen session found.
Closing AP
sudo: pkill: command not found
Exiting...
```

Start with Dockerfile and start_flash.sh, then reproduce the reported build and shell commands on the stated macOS Docker environment. Check how the container exposes WiFi and how the script checks nl80211, iw, pkill, and tput. Done means either documenting the supported setup and limitation or providing a validated Docker change that reaches the intended conversion flow.

Written by the indexing model from the issue text.