Due to a known bug (QTCREATORBUG-30831), binary has to be transferred by some sort of "general deployment method" from docker to device. There is no rsync or sftp. It works well for relatively simply project. But when the binary is relatively large, then binary is going to be corrupted and crash upon launch. By "large", I run my tests with binary of ~150MB.

Due to size limit, I cannot attach a reproducer here. But it is rather easy to come up with one. The easiest way can be "qt_add_big_resources" a large resource file. The actual content of project is irrelevant. It is only about size.

Build, deploy and run, one can see that the application crashes immediately. Furthermore, one can confirm using md5sum:
1. Binary on macOS local file system and the one inside docker container report the same md5 value
2. Binary deployed to target has a different value.

Then it can be concluded that binary is corrupted during transmission from docker to target.