fix accel - add docker-compose - fix keys

README.md

@@ -45,10 +45,38 @@ Without SDK and emulator  |      414 MB      |    138 MB    |
 
 By default, a build will bundle the Android SDK, platform tools and emulator with the image.
 
+with docker-compose:
+
+```bash
+docker compose up android-emulator
+```
+
+or with GPU acceleration
+```bash
+docker compose up android-emulator-cuda
+```
+
+or for example with GPU acceleration and google playstore
+```bash
+docker compose up android-emulator-cuda-store
+```
+
+with only docker
+
+
 ```bash
 docker build -t android-emulator .
 ```
 
+## Keys
+
+To run google_apis_playstore image, you need to have same adbkey between emulator and client.
+
+You can generate one by running `adb keygen adbkey`, that generates 2 files - adbkey and adbkey.pub.
+
+override them inside ./keys directory.
+
+
 ### Running the container
 
 Once the image is built, you can mount your KVM driver on the container and expose its ADB port.
@@ -113,6 +141,17 @@ docker build \
   --tag android-emulator .
 ```
 
+### Variables
+
+#### Disable animation
+DISABLE_ANIMATION=false
+
+#### Disable hidden policy
+DISABLE_HIDDEN_POLICY=true
+
+#### skip adb authentication
+SKIP_AUTH=false
+
 ### Mount an external drive in the container
 
 It might be sometimes useful to have the entire Android SDK folder outside of the container (stored on a shared distributed filesystem such as NFS for example), to significantly reduce the size and the build time of the image.