atd entered FATAL state, too many start retries too quickly

## 🐛 Bug Report

Operating System: Ubuntu 18.04 inside Virtualbox(virtualization is enabled already)

Docker Image: budtmo/docker-android-x86-10.0

Docker Version: 19.03.5-ce

Docker-compose version (Only if you use it): 1.23.2, build 1110ad0

Docker Command to start docker-android: docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -e DEVICE="Samsung Galaxy S10" --name android-container budtmo/docker-android-x86-10.0

## Expected Behavior
Access localhost:6080 from the browser successfully connecting to the AVD running inside docker

## Actual Behavior
docker container logs show some processes keep on exiting. The logs are as follows and show that "atd", "screen-copy" and "auto-recording" all enter FATAL state
```
$ docker container logs -f android-container
2020-03-25 06:58:33,056 CRIT Supervisor running as root (no user in config file)
2020-03-25 06:58:33,060 INFO supervisord started with pid 7
2020-03-25 06:58:34,065 INFO spawned: 'xvfb' with pid 10
2020-03-25 06:58:34,068 INFO spawned: 'port-forward' with pid 11
2020-03-25 06:58:34,069 INFO spawned: 'novnc' with pid 12
2020-03-25 06:58:34,070 INFO spawned: 'openbox' with pid 13
2020-03-25 06:58:34,071 INFO spawned: 'x11vnc' with pid 14
2020-03-25 06:58:34,072 INFO spawned: 'screen-copy' with pid 15
2020-03-25 06:58:34,072 INFO spawned: 'docker-appium' with pid 16
2020-03-25 06:58:34,073 INFO spawned: 'atd' with pid 17
2020-03-25 06:58:34,074 INFO spawned: 'auto-recording' with pid 18
2020-03-25 06:58:34,075 INFO spawned: 'adb-utils' with pid 19
2020-03-25 06:58:34,343 INFO exited: screen-copy (exit status 0; not expected)
2020-03-25 06:58:34,343 INFO exited: atd (exit status 0; not expected)
2020-03-25 06:58:35,137 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-03-25 06:58:35,137 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-03-25 06:58:35,137 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-03-25 06:58:35,137 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-03-25 06:58:35,137 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-03-25 06:58:35,137 INFO success: docker-appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-03-25 06:58:35,137 INFO success: auto-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-03-25 06:58:35,137 INFO success: adb-utils entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-03-25 06:58:35,551 INFO spawned: 'screen-copy' with pid 135
2020-03-25 06:58:35,552 INFO spawned: 'atd' with pid 136
2020-03-25 06:58:35,555 INFO exited: screen-copy (exit status 0; not expected)
2020-03-25 06:58:35,562 INFO exited: atd (exit status 0; not expected)
2020-03-25 06:58:37,566 INFO spawned: 'screen-copy' with pid 142
2020-03-25 06:58:37,567 INFO spawned: 'atd' with pid 143
2020-03-25 06:58:37,570 INFO exited: screen-copy (exit status 0; not expected)
2020-03-25 06:58:37,571 INFO exited: atd (exit status 0; not expected)
2020-03-25 06:58:40,351 INFO exited: auto-recording (exit status 0; expected)
2020-03-25 06:58:41,352 INFO spawned: 'screen-copy' with pid 202
2020-03-25 06:58:41,354 INFO spawned: 'atd' with pid 203
2020-03-25 06:58:41,359 INFO exited: atd (exit status 0; not expected)
2020-03-25 06:58:41,359 INFO gave up: atd entered FATAL state, too many start retries too quickly
2020-03-25 06:58:41,360 INFO exited: screen-copy (exit status 0; not expected)
2020-03-25 06:58:42,361 INFO gave up: screen-copy entered FATAL state, too many start retries too quickly
2020-03-25 06:58:42,541 INFO exited: docker-appium (exit status 0; expected)
```