Hey GolamGauseJaman - oakapp.toml is the app definition, so you normally do not turn it into a Dockerfile yourself.
For OAK4 apps, the documented workflow is that oakctl sends the app to the camera and the build happens on the device through oak-agent. After that you can download the resulting .oakapp package and install that same package on another camera later. So the general idea of “build once, then install later” is correct, but the usual path is oakctl app install, not manual SCP. More on this can be found in our docs here.
If your goal is to avoid Hub/cloud, that part is fine too: oakctl works with OAK4 devices over the local network via the preinstalled oak-agent, so a local/offline-style workflow is possible. The main limitation is that the build still happens on the device, so if your app build needs internet for base images, pip, npm, or model downloads, you would still need either internet access, a local registry/cache, or prepackaged dependencies.
Thanks,
Oskar