...
ls out/target/product/arm64/ android-info.txt obj previous_build_config.mk mk recovery symbols system.img build_fingerprint.txt cache.img data gen module-info.json ramdisk.img root system userdata.img |
...
├── android ├── binaryFiles ├── cmake ├── cmake_uninstall.cmake.in ├── COPYING.GPL ├── cross-compile-chroot.sh ├── data ├── docs ├── external ├── kernel ├── patch ├── products ├── scripts ├── src |
Step1: You can copy the binaryFiles in the robox code to the home directorysome place, then run robox
start the first continer instance
./robox -v start 1
start the second continer instance
./robox -v start 2 1 is the id, used by session manager and docker container
Step2: Check the docker instance process and session manager process.
sudo docker ps | grep instance
step3: Check the anbox session manager process
ps -aux | grep session
step4step3: Log in the container and confirm whether the robox instance started successfully.
docker exec -it instance2 sh
step5: get android property sys.boot_completed
...