budtmo / docker-android

Android in docker solution with noVNC supported and video recording
Other
9.57k stars 1.27k forks source link

Genymotion : can't launch instance on AWS EC2 #326

Closed atigm closed 1 year ago

atigm commented 2 years ago

Hello,

I followed the documentation to launch an instance on AWS but I can't do it.

I tried with MacOS and Ubuntu server 20, in both cases, no instance is launched.

I run this command : docker run -it --rm -p 4723:4723 -v /pathX/sample_devices:/root/tmp -v /pathX/.aws:/root/.aws -e TYPE=aws budtmo/docker-android-genymotion

/pathX/sample_devices/aws.json content :

[
    {
        "region": "eu-west-1",
        "instance": "t2.medium",
        "AMI": "ami-000c622832298e639",
        "SG": "sg-XXXXXXX",
        "subnet_id": "subnet-XXXXXXX"
    }
]

Container's log :

[geny_start] Available types: saas aws
[geny_start] Selected type of deployment: aws, Template file: /root/tmp/aws.json
2022-05-27 02:02:00,883 CRIT Supervisor running as root (no user in config file)
2022-05-27 02:02:00,885 INFO supervisord started with pid 10
2022-05-27 02:02:01,889 INFO spawned: 'xvfb' with pid 13
2022-05-27 02:02:01,891 INFO spawned: 'port-forward' with pid 14
2022-05-27 02:02:01,894 INFO spawned: 'novnc' with pid 15
2022-05-27 02:02:01,896 INFO spawned: 'openbox' with pid 16
2022-05-27 02:02:01,899 INFO spawned: 'x11vnc' with pid 17
2022-05-27 02:02:01,901 INFO spawned: 'screen-copy' with pid 18
2022-05-27 02:02:01,904 INFO spawned: 'docker-appium' with pid 20
2022-05-27 02:02:01,906 INFO spawned: 'atd' with pid 25
2022-05-27 02:02:01,908 INFO spawned: 'auto-recording' with pid 27
2022-05-27 02:02:01,910 INFO spawned: 'adb-utils' with pid 32
2022-05-27 02:02:01,913 INFO exited: screen-copy (exit status 0; not expected)
2022-05-27 02:02:01,916 INFO exited: atd (exit status 0; not expected)
2022-05-27 02:02:02,945 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-27 02:02:02,945 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-27 02:02:02,945 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-27 02:02:02,946 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-27 02:02:02,946 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-27 02:02:02,948 INFO spawned: 'screen-copy' with pid 320
2022-05-27 02:02:02,949 INFO success: docker-appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-27 02:02:02,951 INFO spawned: 'atd' with pid 321
2022-05-27 02:02:02,951 INFO success: auto-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-27 02:02:02,951 INFO success: adb-utils entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-27 02:02:02,959 INFO exited: atd (exit status 0; not expected)
2022-05-27 02:02:02,960 INFO exited: screen-copy (exit status 0; not expected)
2022-05-27 02:02:05,441 INFO spawned: 'screen-copy' with pid 336
2022-05-27 02:02:05,444 INFO spawned: 'atd' with pid 337
2022-05-27 02:02:05,453 INFO exited: screen-copy (exit status 0; not expected)
2022-05-27 02:02:05,455 INFO exited: atd (exit status 0; not expected)
2022-05-27 02:02:07,920 INFO exited: auto-recording (exit status 0; expected)
2022-05-27 02:02:08,924 INFO spawned: 'screen-copy' with pid 338

BUT no instance is launched on AWS EC2!

Note: There is no problem with the AWS configuration, because I can manually launch an instance with this configuration and it works fine.

Thank you

budtmo commented 1 year ago

Hi @atigm ,

please check again with the latest version. it should work. I will close the ticket but feel free to reopen the ticket if needed