[{"_1":2,"_159":-5,"_160":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_138":139},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":11,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_27":28,"_29":-5,"_30":11,"_31":11,"_32":33,"_34":35,"_36":-5,"_37":11,"_38":39,"_88":-5,"_89":90,"_129":-5,"_130":11,"_131":21,"_132":11,"_133":-5,"_134":11,"_135":-5,"_136":137},"canonicalUrl","https://hub.docker.com/r/sunnydaydev/android-sdk/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","sunnydaydev","reponame","android-sdk","cloudBuildSource","isAutobuildsAvailable","repo",{"_40":41,"_42":43,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":55,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":74,"_79":11,"_80":81,"_85":33,"_86":87},"categories",[],"content_types",[44],"image","date_registered","2018-02-19T08:03:07.35086Z","description","Docker for android development based on thyrlian/android with latest sdk and tools.","is_private","last_updated","2018-02-20T21:09:28.375054Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[56],"application/vnd.docker.container.image.v1+json","name","pull_count",268,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# AndroidSDK\n\nAndroid SDK development environment Docker image\n\n[![Docker Hub](https://img.shields.io/badge/Docker%20Hub-info-blue.svg)](https://hub.docker.com/r/thyrlian/android-sdk/)\n[![Build Status](https://travis-ci.org/thyrlian/AndroidSDK.svg?branch=master)](https://travis-ci.org/thyrlian/AndroidSDK)\n[![Android Dev Digest](https://img.shields.io/badge/AndroidDevDigest-%23127-green.svg)](https://www.androiddevdigest.com/digest-127/)\n[![Android开发技术周报](https://img.shields.io/badge/Android%E5%BC%80%E5%8F%91%E6%8A%80%E6%9C%AF%E5%91%A8%E6%8A%A5-%23114-yellowgreen.svg)](http://www.androidweekly.cn/android-dev-weekly-issue-114/)\n\n

\n\n $\"Conference$ \n\n## Goals\n\n* It contains the complete Android SDK enviroment, is able to perform all regular Android jobs.\n* Solves the problem of \"*It works on my machine, but not on XXX machine*\".\n* Some tool (e.g. [Infer](https://github.com/facebook/infer)), which has complex dependencies might be in conflict with your local environment. Installing the tool within a Docker container is the easiest and perfect solution.\n* Directly being used as Android CI build enviroment.\n\n## Philosophy\n\nProvide only the barebone SDK (the latest official minimal package) gives you the most flexibility in tailoring your own SDK tools for your project. You can maintain an external persistent SDK directory, and mount it to any container. In this way, you don't have to waste time on downloading over and over again, meanwhile, without having any unnecessary package.\n\n## Caveat\n\nRun Android SDK update directly within the **Dockerfile** or inside the **container** would fail if the storage driver is `AUFS` (by default), it is due to some file operations (during updating) are not supported by this storage driver, but changing it to `Btrfs` would work.\n\nWhat happens if the update fails?\n```bash\nls $ANDROID_HOME/tools/\n#=> empty, nothing is there\n# tools such as: android, sdkmanager, emulator, lint and etc. are gone\n\nandroid\n#=> bash: android: command not found\n\nsdkmanager\n#=> bash: /opt/android-sdk/tools/bin/sdkmanager: No such file or directory\n```\n\nTo know more about the storage driver:\n\n* Check Docker's current storage driver option\n```console\ndocker info | grep 'Storage Driver'\n```\n\n* Check which filesystems are supported by the running host kernel\n```console\ncat /proc/filesystems\n```\n\nTo prevent this problem from happening, and you don't wanna bother dealing with storage driver. The only solution is to mount an external SDK volume from host to container. Then you are free to try any of below approaches.\n\n* Update SDK in the usual way but directly inside container.\n* Update SDK from host directory (**Remember**: the host machine must be the same target architecture as the container - `x86_64 Linux`).\n\nIf you by accident update SDK on a host machine which has a mismatch target architecture than the container, some binaries won't be executable in container any longer.\n\n```bash\ngradle \n#=> Error: java.util.concurrent.ExecutionException: java.lang.RuntimeException: AAPT process not ready to receive commands\n\n$ANDROID_HOME/build-tools/x.x.x/aapt\n#=> aapt: cannot execute binary file: Exec format error\n\nadb\n#=> adb: cannot execute binary file: Exec format error\n```\n\n## Getting Started\n\n```bash\n# build the image\n# set the working directory to the project's root directory first\ndocker build -t android-sdk android-sdk\n# or pull the image\ndocker pull thyrlian/android-sdk\n\n# below commands assume that you've pulled the image\n\n# copy the pre-downloaded SDK to the mounted 'sdk' directory\ndocker run -it --rm -v $(pwd)/sdk:/sdk thyrlian/android-sdk bash -c 'cp -a $ANDROID_HOME/. /sdk'\n\n# go to the 'sdk' directory on the host, update the SDK\n# ONLY IF the host machine is the same target architecture as the container\n# JDK required on the host\nsdk/tools/bin/sdkmanager --update\n# or install specific packages\nsdk/tools/bin/sdkmanager \"build-tools;x.y.z\" \"platforms;android-x\" ...\n\n# mount the updated SDK to container again\n# if the host SDK directory is mounted to more than one container\n# to avoid multiple containers writing to the SDK directory at the same time\n# you should mount the SDK volume in read-only mode\ndocker run -it -v $(pwd)/sdk:/opt/android-sdk:ro thyrlian/android-sdk /bin/bash\n\n# you can mount without read-only option, only if you need to update SDK inside container\ndocker run -it -v $(pwd)/sdk:/opt/android-sdk thyrlian/android-sdk /bin/bash\n\n# to keep and reuse Gradle cache\ndocker run -it -v $(pwd)/sdk:/opt/android-sdk -v $(pwd)/gradle_caches:/root/.gradle/caches thyrlian/android-sdk /bin/bash\n\n# to stop and remove container\n# when the image was pulled from a registry\ndocker stop $(docker ps -aqf \"ancestor=thyrlian/android-sdk\") &> /dev/null && docker rm $(docker ps -aqf \"ancestor=thyrlian/android-sdk\") &> /dev/null\n# when the image was built locally\ndocker stop $(docker ps -aqf \"ancestor=android-sdk\") &> /dev/null && docker rm $(docker ps -aqf \"ancestor=android-sdk\") &> /dev/null\n# more flexible way - doesn't matter where the image comes from\ndocker stop $(docker ps -a | grep 'android-sdk' | awk '{ print $1 }') &> /dev/null && docker rm $(docker ps -a | grep 'android-sdk' | awk '{ print $1 }') &> /dev/null\n```\n\n## SSH\n\nIt is also possible if you wanna connect to container via SSH. There are three different approaches.\n\n* Build an image on your own, with a built-in `authorized_keys`\n\n```bash\n# Put your `id_rsa.pub` under `android-sdk/authorized_keys` (as many as you want)\n\n# Build an image\ndocker build -t android-sdk android-sdk\n\n# Run a container\ndocker run -d -p 2222:22 -v $(pwd)/sdk:/opt/android-sdk:ro android-sdk\n```\n\n* Mount `authorized_keys` file from the host to a container\n\n```bash\ndocker run -d -p 2222:22 -v $(pwd)/authorized_keys:/root/.ssh/authorized_keys thyrlian/android-sdk\n```\n\n* Copy a local `authorized_keys` file to a container\n\n```bash\n# Create a local `authorized_keys` file, which contains the content from your `id_rsa.pub`\n\n# Run a container\ndocker run -d -p 2222:22 -v $(pwd)/sdk:/opt/android-sdk:ro thyrlian/android-sdk\n\n# Copy the just created local authorized_keys file to the running container\ndocker cp $(pwd)/authorized_keys `docker ps -aqf \"ancestor=thyrlian/android-sdk\"`:/root/.ssh/authorized_keys\n\n# Set the proper owner and group for authorized_keys file\ndocker exec -it `docker ps -aqf \"ancestor=thyrlian/android-sdk\"` bash -c 'chown root:root /root/.ssh/authorized_keys'\n```\n\nThat's it! Now it's up and running, you can ssh to it\n\n```console\nssh root@ -p 2222\n```\n\nAnd, in case you need, you can still attach to the running container (not via ssh) by\n\n```console\ndocker exec -it /bin/bash\n```\n\n

\n\n## VNC\n\nRemote access to the container's desktop might be helpful if you plan to run emulator inside the container.\n\n```bash\n# pull the image with VNC support\ndocker pull thyrlian/android-sdk-vnc\n\n# spin up a container\n# with SSH\ndocker run -d -p 5901:5901 -p 2222:22 -v $(pwd)/sdk:/opt/android-sdk android-sdk-vnc\n# or with interactive session\ndocker run -it -p 5901:5901 -v $(pwd)/sdk:/opt/android-sdk android-sdk-vnc /bin/bash\n```\n\nWhen the container is up and running, use your favorite VNC client to connect to it:\n\n* `:5901`\n\n* Password (with control): ***android***\n\n* Password (view only): ***docker***\n\n```bash\n# setup and launch emulator inside the container\n# create a new Android Virtual Device\necho \"no\" | avdmanager create avd -n test -k \"system-images;android-25;google_apis;armeabi-v7a\"\n# launch emulator\nemulator64-arm -avd test -noaudio -no-boot-anim -gpu offscreen\n```\n\nFor more details, please refer to [Emulator section](https://github.com/thyrlian/AndroidSDK#emulator).\n\n

\n\n## NFS\n\nYou can host the Android SDK in one host-independent place, and share it across different containers. One solution is using NFS (Network File System).\n\nTo make the container consume the NFS, you can try either way below:\n* Mount the NFS onto your host machine, then run container with volume option (`-v`).\n* Use a Docker volume plugin, for instance [Convoy plugin](https://github.com/rancher/convoy).\n\nAnd here are instructions for configuring a NFS server (on Ubuntu):\n\n```bash\nsudo apt-get update\nsudo apt-get install -y nfs-kernel-server\nsudo mkdir -p /var/nfs/android-sdk\n\n# put the Android SDK under /var/nfs/android-sdk\n# if you haven't got any, run below commands\nsudo apt-get install -y wget zip\ncd /var/nfs/android-sdk\nsudo wget -q $(wget -q -O- 'https://developer.android.com/sdk' | grep -o \"\\\"https://.*android.*tools.*linux.*\\\"\" | sed \"s/\\\"//g\")\nsudo unzip *tools*linux*.zip\nsudo rm *tools*linux*.zip\nsudo mkdir licenses\necho 8933bad161af4178b1185d1a37fbf41ea5269c55 | sudo tee licenses/android-sdk-license > /dev/null\necho 84831b9409646a918e30573bab4c9c91346d8abd | sudo tee licenses/android-sdk-preview-license > /dev/null\necho d975f751698a77b662f1254ddbeed3901e976f5a | sudo tee licenses/intel-android-extra-license > /dev/null\n\n# configure and launch NFS service\nsudo chown nobody:nogroup /var/nfs\necho \"/var/nfs *(rw,sync,no_subtree_check,no_root_squash)\" | sudo tee --append /etc/exports > /dev/null\nsudo exportfs -a\nsudo service nfs-kernel-server start\n```\n\n## Gradle distributions mirror server\n\nThere is still a little room for optimization: recent distribution of Gradle is around 90MB, imagine different containers / build jobs have to perform downloading many times, and it has high influence upon your network bandwidth. Setting up a local Gradle distributions mirror server would significantly boost your download speed.\n\nFortunately, you can easily build such a mirror server docker image on your own.\n\n```bash\ndocker build -t gradle-server gradle-server\n# by default it downloads the most recent 14 gradle distributions (excluding rc or milestone)\n```\n\nThe download amount can be changed [here](https://github.com/thyrlian/AndroidSDK/blob/master/gradle-server/Dockerfile#L30). Preferably, you should run the [download script](https://github.com/thyrlian/AndroidSDK/blob/master/gradle-server/gradle_downloader.sh) locally, and mount the download directory to the container.\n\n```bash\ngradle-server/gradle_downloader.sh [DOWNLOAD_DIRECTORY] [DOWNLOAD_AMOUNT]\ndocker run -d -p 80:80 -p 443:443 -v [DOWNLOAD_DIRECTORY]:/var/www/gradle.org/public_html/distributions gradle-server\n```\n\n```bash\n# copy the SSL certificate from gradle server container to host machine\ndocker cp `docker ps -aqf \"ancestor=gradle-server\"`:/etc/apache2/ssl/apache.crt apache.crt\n# copy the SSL certificate from host machine to AndroidSDK container\ndocker cp apache.crt `docker ps -aqf \"ancestor=thyrlian/android-sdk\"`:/home/apache.crt\n# add self-signed SSL certificate to Java keystore\ndocker exec -it `docker ps -aqf \"ancestor=thyrlian/android-sdk\"` bash -c '$JAVA_HOME/bin/keytool -import -trustcacerts -file /home/apache.crt -keystore $JAVA_HOME/jre/lib/security/cacerts -storepass changeit -noprompt'\n# map gradle services domain to your local IP\ndocker exec -it `docker ps -aqf \"ancestor=thyrlian/android-sdk\"` bash -c 'echo \"[YOUR_HOST_IP_ADDRESS_FOR_GRADLE_CONTAINER] services.gradle.org\" >> /etc/hosts'\n```\n\nStarting from now on, gradle wrapper will download gradle distributions from your local mirror server, lightning fast! The downloaded distribution will be uncompressed to `/root/.gradle/wrapper/dists`.\n\nIf you don't want to bother with SSL certificate, you can simply change the `distributionUrl` inside `[YOUR_PROJECT]/gradle/wrapper/gradle-wrapper.properties` from `https` to `http`.\n\n## Emulator\n\nARM emulator is host machine independent, can run anywhere - Linux, macOS, VM and etc. While the performance is a bit poor. On the contrary, x86 emulator requires KVM, which means only runnable on Linux.\n\nAccording to [Google's documentation](https://developer.android.com/studio/run/emulator-acceleration.html#accel-vm):\n\n> **VM acceleration restrictions**\n\n> Note the following restrictions of VM acceleration:\n\n> * You can't run a VM-accelerated emulator inside another VM, such as a VM hosted by VirtualBox, VMWare, or Docker. You must run the emulator directly on your system hardware.\n\n> * You can't run software that uses another virtualization technology at the same time that you run the accelerated emulator. For example, VirtualBox, VMWare, and Docker currently use a different virtualization technology, so you can't run them at the same time as the accelerated emulator.\n\n### Preconditions on the host machine (for x86 emulator)\n\nRead [How to Start Intel Hardware-assisted Virtualization (hypervisor) on Linux](https://software.intel.com/en-us/blogs/2012/03/12/how-to-start-intel-hardware-assisted-virtualization-hypervisor-on-linux-to-speed-up-intel-android-x86-emulator) for more details.\n\nRead [KVM Installation](https://help.ubuntu.com/community/KVM/Installation) if you haven't got KVM installed on the host yet.\n\n* Check the capability of running KVM\n```bash\negrep -c '(vmx|svm)' /proc/cpuinfo\n# or\negrep -c ' lm ' /proc/cpuinfo\n# when output > 0 it means the host CPU supports hardware virtualization.\n\nsudo kvm-ok\n# seeing below info means you can run your virtual machine faster with the KVM extensions\nINFO: /dev/kvm exists\nKVM acceleration can be used\n```\n\n* Load KVM module on the host\n```console\nmodprobe kvm_intel\n```\n\n* Check if KVM module is successfully loaded\n```console\nlsmod | grep kvm\n```\n\n### How to run emulator\n\n* Check available emulator system images from remote SDK repository (on the host machine)\n```console\nsdkmanager --list --verbose\n```\n\n* Download emulator system image(s) (on the host machine)\n```bash\nsdkmanager \"system_image_1\" \"system_image_2\"\n# e.g.:\n# system-images;android-24;android-tv;x86\n# system-images;android-24;default;arm64-v8a\n# system-images;android-24;default;armeabi-v7a\n# system-images;android-24;default;x86\n# system-images;android-24;default;x86_64\n# system-images;android-24;google_apis;arm64-v8a\n# system-images;android-24;google_apis;armeabi-v7a\n# system-images;android-24;google_apis;x86\n# system-images;android-24;google_apis;x86_64\n# system-images;android-24;google_apis_playstore;x86\n```\n\n* Run Docker container in privileged mode (not necessary for ARM emulator)\n```bash\n# required by KVM\ndocker run -it --privileged -v $(pwd)/sdk:/opt/android-sdk:ro thyrlian/android-sdk /bin/bash\n```\n\n* Check acceleration ability (not necessary for ARM emulator)\n```bash\nemulator -accel-check\n\n# when succeeds\naccel:\n0\nKVM (version 12) is installed and usable.\naccel\n\n# when fails (probably due to unprivileged mode)\naccel:\n8\n/dev/kvm is not found: VT disabled in BIOS or KVM kernel module not loaded\naccel\n```\n\n* Create a new Android Virtual Device\n```bash\necho \"no\" | avdmanager create avd -n -k \n# e.g.:\necho \"no\" | avdmanager create avd -n test -k \"system-images;android-24;default;armeabi-v7a\"\n```\n\n* List existing Android Virtual Devices\n```bash\navdmanager list avd\n# ==================================================\nAvailable Android Virtual Devices:\n Name: test\n Path: /root/.android/avd/test.avd\n Target:\n Based on: Android 7.0 (Nougat) Tag/ABI: default/armeabi-v7a\n# ==================================================\n\n# or\n\nemulator -list-avds\n# 32-bit Linux Android emulator binaries are DEPRECATED\n# ==================================================\ntest\n# ==================================================\n```\n\n* Launch emulator in background\n```bash\n# use different command per architecture\nemulator64-arm -avd -noaudio -no-boot-anim -no-window -accel on &\n\n# or\nemulator64-mips -avd -noaudio -no-boot-anim -no-window -accel on &\n\n# or\nemulator64-x86 -avd -noaudio -no-boot-anim -no-window -accel on &\n\n# if the container is not running in privileged mode, you should see below errors:\n#=> emulator: ERROR: x86_64 emulation currently requires hardware acceleration!\n#=> Please ensure KVM is properly installed and usable.\n#=> CPU acceleration status: /dev/kvm is not found: VT disabled in BIOS or KVM kernel module not loaded\n# or it's running on top of a VM\n#=> CPU acceleration status: KVM requires a CPU that supports vmx or svm\n```\n\n* Check the virtual device status\n```bash\nadb devices\n# ==================================================\nList of devices attached\nemulator-5554\toffline\n# \"offline\" means it's still booting up\n# ==================================================\n\n# ==================================================\nList of devices attached\nemulator-5554\tdevice\n# \"device\" means it's ready to be used\n# ==================================================\n```\n\nNow you can for instance run UI tests on the emulator (just remember, the performance is POOR):\n```console\n/gradlew connectedAndroidTest\n```\n\n### Access the emulator from outside\n\nDefault adb server port: `5037`\n\n```bash\n# spin up a container\n# with SSH\ndocker run -d -p 5037:5037 -p 2222:22 -v $(pwd)/sdk:/opt/android-sdk android-sdk-vnc\n# or with interactive session\ndocker run -it -p 5037:5037 -v $(pwd)/sdk:/opt/android-sdk android-sdk-vnc /bin/bash\n\n# launch emulator inside the container...\n```\n\nOutside the container:\n\n```bash\nadb connect :5037\nadb devices\n#=> List of devices attached\n#=> emulator-5554\tdevice\n```\n\nMake sure that your **adb client** talks to the **adb server** inside the container, but not your local one.\n\n## Android Device\n\nYou can give a container access to host's USB Android devices.\n```console\n# on Linux\ndocker run -it --privileged -v /dev/bus/usb:/dev/bus/usb -v $(pwd)/sdk:/opt/android-sdk thyrlian/android-sdk /bin/bash\n\n# or\n# try to avoid privileged flag, just add necessary capabilities when possible\n# --device option allows you to run devices inside the container without the --privileged flag\ndocker run -it --device=/dev/ttyUSB0 -v $(pwd)/sdk:/opt/android-sdk thyrlian/android-sdk /bin/bash\n```\n\nNote:\n* Connect Android device via USB on host first;\n* Launch container;\n* Disconnect and connect Android device on USB;\n* Select OK for \"Allow USB debugging\" on Android device;\n* Now the Android device will show up inside the container (`adb devices`).\n\nDon't worry about `adbkey` or `adbkey.pub` under `/.android`, not required.\n\n[Docker for Mac FAQ](https://docs.docker.com/docker-for-mac/faqs/#can-i-pass-through-a-usb-device-to-a-container) says:\n\n> Unfortunately it is not possible to pass through a USB device (or a serial port) to a container.\n\n## Android Commands Reference\n\n* Check installed Android SDK tools version\n```console\ncat $ANDROID_HOME/tools/source.properties | grep Pkg.Revision\ncat $ANDROID_HOME/platform-tools/source.properties | grep Pkg.Revision\n```\n\n> The \"`android`\" command is deprecated. For command-line tools, use `tools/bin/sdkmanager` and `tools/bin/avdmanager`.\n\n* List installed and available packages\n```console\nsdkmanager --list\n# print full details instead of truncated path\nsdkmanager --list --verbose\n```\n\n* Update all installed packages to the latest version\n```bash\nsdkmanager --update\n```\n\n* Install packages\n> The packages argument is an SDK-style path as shown with the `--list` command, wrapped in quotes (for example, `\"extras;android;m2repository\"`). You can pass multiple package paths, separated with a space, but they must each be wrapped in their own set of quotes.\n```bash\nsdkmanager \"extras;android;m2repository\" \"extras;google;m2repository\" \"extras;google;google_play_services\" \"extras;google;instantapps\" \"extras;m2repository;com;android;support;constraint;constraint-layout;1.0.2\" \"build-tools;26.0.0\" \"platforms;android-26\"\n```\n\n* Stop emulator\n```console\nadb -s emu kill\n```\n\n## Demythologizing Memory\n\n### OOM behaviour\n\nSometimes you may encounter OOM (Out of Memory) issue. The issues vary in logs, while you could find the essence by checking the exit code (`echo $?`).\n\nFor demonstration, below examples try to execute [MemoryFiller](https://github.com/thyrlian/AndroidSDK/blob/master/misc/MemoryFiller/MemoryFiller.java) which can fill memory up quickly.\n\n* **Exit Code** `137` (= 128 + 9 = SIGKILL = Killed)\n\n Example code:\n ```bash\n # spin up a container with memory limit (128MB)\n docker run -it -m 128m -v $(pwd)/misc/MemoryFiller:/root/MemoryFiller thyrlian/android-sdk /bin/bash\n # fill memory up\n cd /root/MemoryFiller && javac MemoryFiller.java\n java MemoryFiller\n ```\n\n Logs:\n ```console\n Killed\n ```\n\n Commentary: The process was in extreme resource starvation, thus was killed by the kernel OOM killer. This happens when **JVM max heap size > actual container memory**. Similarly, the logs could look like this when running a gradle task in an Android project: `Process 'Gradle Test Executor 1' finished with non-zero exit value 137`.\n\n* **Exit Code** `1` (= SIGHUP = Hangup)\n\n Example code:\n ```bash\n # spin up a container with memory limit (or without - both lead to the same result)\n docker run -it -m 128m -v $(pwd)/misc/MemoryFiller:/root/MemoryFiller thyrlian/android-sdk /bin/bash\n # fill memory up\n # enable Docker memory limits transparency for JVM\n cd /root/MemoryFiller && javac MemoryFiller.java\n java -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap MemoryFiller\n ```\n\n Logs:\n ```console\n Exception in thread \"main\" java.lang.OutOfMemoryError: Java heap space\n \tat MemoryFiller.main(MemoryFiller.java:13)\n ```\n\n Commentary: With [enabling Docker memory limits transparency for JVM](https://blogs.oracle.com/java-platform-group/java-se-support-for-docker-cpu-and-memory-limits), JVM is able to correctly estimate the max heap size, and it won't be killed by the kernel OOM killer any more. Similarly, the logs could look like this when running a gradle task in an Android project: `Process 'Gradle Test Executor 1' finished with non-zero exit value 1`. In this case, you should either check your code or tweak your memory limit for container (or JVM heap parameters, or even the host memory size).\n\n* **Exit Code** `3` (= SIGQUIT = Quit)\n\n Example code:\n ```bash\n # spin up a container without memory limit\n docker run -it -v $(pwd)/misc/MemoryFiller:/root/MemoryFiller thyrlian/android-sdk /bin/bash\n # fill memory up\n cd /root/MemoryFiller && javac MemoryFiller.java\n # make sure that Docker memory resource is big enough > JVM max heap size\n # otherwise it's better to run with UnlockExperimentalVMOptions & UseCGroupMemoryLimitForHeap enabled\n java -XX:+ExitOnOutOfMemoryError MemoryFiller\n ```\n\n Logs:\n ```console\n Terminating due to java.lang.OutOfMemoryError: Java heap space\n ```\n\n Commentary: JRockit JVM exits on the first occurrence of an OOM error. It can be used if you prefer restarting an instance of JRockit JVM rather than handling OOM errors.\n\n* **Exit Code** `134` (= 128 + 6 = SIGABRT = Abort)\n\n Example code:\n ```bash\n # spin up a container without memory limit\n docker run -it -v $(pwd)/misc/MemoryFiller:/root/MemoryFiller thyrlian/android-sdk /bin/bash\n # fill memory up\n cd /root/MemoryFiller && javac MemoryFiller.java\n # make sure that Docker memory resource is big enough > JVM max heap size\n # otherwise it's better to run with UnlockExperimentalVMOptions & UseCGroupMemoryLimitForHeap enabled\n java -XX:+CrashOnOutOfMemoryError MemoryFiller\n ```\n\n Logs:\n ```console\n Aborting due to java.lang.OutOfMemoryError: Java heap space\n #\n # A fatal error has been detected by the Java Runtime Environment:\n #\n # Internal Error (debug.cpp:308), pid=63, tid=0x00007f208708d700\n # fatal error: OutOfMemory encountered: Java heap space\n #\n # JRE version: OpenJDK Runtime Environment (8.0_131-b11) (build 1.8.0_131-8u131-b11-2ubuntu1.16.04.3-b11)\n # Java VM: OpenJDK 64-Bit Server VM (25.131-b11 mixed mode linux-amd64 compressed oops)\n # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try \"ulimit -c unlimited\" before starting Java again\n #\n # An error report file with more information is saved as:\n # /root/MemoryFiller/hs_err_pid63.log\n #\n # If you would like to submit a bug report, please visit:\n # http://bugreport.java.com/bugreport/crash.jsp\n #\n Aborted\n ```\n\n Commentary: JRockit JVM crashes and produces text and binary crash files when an OOM error occurs. When JVM crashes with a fatal error, an error report file `hs_err_pid***.log` will be generated in the same working directory.\n\n### Facts\n\n* JVM is not container aware, and always guesses about the memory resource.\n* Many tools (such as `free`, `vmstat`, `top`) were invented before the existence of [cgroups](https://en.wikipedia.org/wiki/Cgroups), thus they have no clue about the reso","has_starred","hub_user","immutable_tags_settings",{"_75":11,"_76":77},"enabled","rules",[78],".*","is_automated","permissions",{"_82":21,"_83":11,"_84":11},"read","write","admin","user","storage_size",10633174011,"orgData","recentTags",[91],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":100,"_50":118,"_119":94,"_120":33,"_121":56,"_57":122,"_123":124,"_125":109,"_126":118,"_127":66,"_128":21},"content_type","creator",2626412,"full_size",1964688607,"id",22498710,"images",[101],{"_102":103,"_104":105,"_106":107,"_108":109,"_110":111,"_112":113,"_114":107,"_115":-5,"_116":96,"_63":66,"_117":-5},"architecture","amd64","digest","sha256:d1b41c46d912640ee14b44fada5d5e9b6b427445c4184d2e6cf9c1a9349488a9","features","","last_pulled","2026-09-22T19:46:44.774406894Z","last_pushed","2018-02-20T21:09:28Z","os","linux","os_features","os_version","size","variant","2018-02-20T21:09:27.662878Z","last_updater","last_updater_username","media_type","latest","repository",4175950,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_38":140,"_147":148,"_136":157,"_158":11},{"_40":141,"_42":142,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":143,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":144,"_79":11,"_80":146,"_85":33,"_86":87},[],[44],[56],{"_75":11,"_76":145},[78],{"_82":21,"_83":11,"_84":11},"tags",{"_149":64,"_150":-5,"_151":-5,"_152":153},"count","next","previous","results",[154],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":155,"_50":118,"_119":94,"_120":33,"_121":56,"_57":122,"_123":124,"_125":109,"_126":118,"_127":66,"_128":21},[156],{"_102":103,"_104":105,"_106":107,"_108":109,"_110":111,"_112":113,"_114":107,"_115":-5,"_116":96,"_63":66,"_117":-5},[],"canDeleteTags","actionData","errors"]

sunnydaydev/android-sdk

Tags for sunnydaydev/android-sdk