[🐛 Bug ]: docker-android device start ... error

[pnthai88]

Operating System

Ubuntu 20.04

Docker Image

lastest

Expected behaviour

The first run is ok, everything work perfect as expected. But when i restart the container, the problem starting ...

2023-07-15 06:26:07,015 INFO success: device entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-15 06:26:07,162 INFO exited: device (exit status 1; not expected)
2023-07-15 06:26:08,165 INFO spawned: 'device' with pid 586
2023-07-15 06:26:09,607 INFO success: device entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-15 06:26:09,772 INFO exited: device (exit status 1; not expected)
2023-07-15 06:26:10,775 INFO spawned: 'device' with pid 590
2023-07-15 06:26:12,204 INFO success: device entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-15 06:26:12,262 INFO exited: device (exit status 1; not expected)
2023-07-15 06:26:13,265 INFO spawned: 'device' with pid 594
2023-07-15 06:26:14,688 INFO success: device entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-15 06:26:14,747 INFO exited: device (exit status 1; not expected)
2023-07-15 06:26:15,750 INFO spawned: 'device' with pid 598
2023-07-15 06:26:17,193 INFO success: device entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-15 06:26:17,289 INFO exited: device (exit status 1; not expected)
2023-07-15 06:26:18,292 INFO spawned: 'device' with pid 602
2023-07-15 06:26:19,687 INFO success: device entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-15 06:26:19,745 INFO exited: device (exit status 1; not expected)
2023-07-15 06:26:20,749 INFO spawned: 'device' with pid 606
2023-07-15 06:26:22,189 INFO success: device entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-15 06:26:22,247 INFO exited: device (exit status 1; not expected)

I tried with the command by reading python code

> shell inside container: docker-android start device

i tried with other command directly from emulator in container

> shell inside container: emulator -list-avds (get list emulator named as "android" in config EMULATOR_NAME': 'android')
> shell inside container: emulator -avd android

Actual behaviour

So, the container is unable to restart or shutdown, if we let it run after create with docker cli, it's all fine. To temporary solve this problem, i need to delete the container and start it again.

Logs

No response

[pnthai88]

Well, it's my misconfig at my end.

[asafe199]

@pnthai88 Have you found the issue? If yes, can you share your solution?

[pnthai88]

@pnthai88 Have you found the issue? If yes, can you share your solution?

i bought the pro version for $30 (affordable and suitable during the software development phase) and will buy the higher priced pro version when the project is complete and profitable

[aogg]

+1

[ghmagi]

@pnthai88 Have you found the issue? If yes, can you share your solution?

i bought the pro version for $30 (affordable and suitable during the software development phase) and will buy the higher priced pro version when the project is complete and profitable

@pnthai88, are you saying that with the pro version you're able to run / stop / start a container, and the emulator comes up reliably each time? As far as you know, is this an feature the pro version provides, but the free one does not?

[chodorenko]

its problem from there

docker-android/cli/src/device/emulator.py

Line 140 in 7064a9b

"sudo sed -i '1d' /etc/passwd")

In first start installs rights for /dev/kvm and remove root user from system.
after reboot container for /dev/kvm present old rights and no can use sudo by not exist root user.

@budtmo Can you explain why this was done? And perhaps it is worth removing the deletion of the root user in the container?