Hello Thyrlian,

First of all thank You very much for all Your efforts related with current project. Could you explain please why do we need to remove X11, i mean instructions in watchdog.sh

 rm -fv /tmp/.X*-lock >> $log_file
 rm -fv /tmp/.X11-unix/* >> $log_file

Thank You!

I'm using Ubuntu 18 and I get tons of errors when I try to mount the sdk dir into the container using this command:

docker run -it --rm -v sdk bash -c 'cp -a $ANDROID_HOME/. /sdk'

Errors:

cp: read error: I/O error
cp: can't open '/./proc/sys/net/ipv6/route/flush': Permission denied
cp: can't open '/./proc/sys/vm/compact_memory': Permission denied
cp: can't open '/./proc/kmsg': Operation not permitted
cp: can't open '/./proc/sysrq-trigger': Permission denied
cp: read error: I/O error
cp: read error: Invalid argument

Full:
https://pastebin.com/B2mgsf3h

Any possibility for this? I'm using this image as part of a Gitlab CI workflow, and quite a big chunk of time is spent downloading the image each time. This could be sped up quite a bit if the base image were as minimal and small as possible. It would cut the base image size from about 188 MB to 5 MB.

I've follow the steps to run a simple android emulator on my docker container and recieved the following error after running the command emulator -avd test -no-audio -no-boot-anim -accel on -gpu swiftshader_indirect &:

emulator: INFO: QtLogger.cpp:68: Warning: could not connect to display  ((null):0, (null))


emulator: INFO: QtLogger.cpp:68: Info: Could not load the Qt platform plugin "xcb" in "/opt/android-sdk/emulator/lib64/qt/plugins" even though it was found. ((null):0, (null))


Fatal: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: xcb.
 ((null):0, (null))
emulator: INFO: QtLogger.cpp:68: Fatal: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: xcb.
 ((null):0, (null))

Hello.

what it means "Solves the problem of "It works on my machine, but not on XXX machine" ? I intended that your image works on every machine,from windows,to mac to arm32 or 64. It's not like this,the title is misleading. I tried to run your image on the jetson nano and I've got this error :

root@zi-desktop:~/Desktop/zi/Work/I9/Android# docker run -it --rm -v $(pwd)/sdk:/sdk thyrlian/android-sdk bash -c 'cp -a $ANDROID_SDK_ROOT/. /sdk

'WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

standard_init_linux.go:219: exec user process caused: no such file or directory

Description

Some spaces in the image are wasted, should be considered to free up.

Steps

Tool used: dive

dive thyrlian/android-sdk:7.1

Output

│ Image Details │

Image name: thyrlian/android-sdk:7.1
Total Image size: 1.3 GB
Potential wasted space: 7.2 MB
Image efficiency score: 99 %

Count   Total Space  Path
    3        2.2 MB  /var/cache/debconf/templates.dat
    2        1.4 MB  /var/cache/debconf/templates.dat-old
    3        693 kB  /var/log/dpkg.log
    3        667 kB  /var/lib/dpkg/status
    2        579 kB  /var/lib/dpkg/status-old
    2        530 kB  /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_focal_InRelease
    2        228 kB  /var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_focal-security_InRelease
    2        228 kB  /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_focal-updates_InRelease
    2        201 kB  /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_focal-backports_InRelease
    2        133 kB  /var/log/apt/term.log
    3         73 kB  /var/log/apt/history.log
    2         59 kB  /var/log/lastlog
    3         53 kB  /etc/ld.so.cache
    3         45 kB  /var/cache/debconf/config.dat
    3         42 kB  /var/cache/ldconfig/aux-cache
    2         40 kB  /var/cache/debconf/config.dat-old
    3         35 kB  /var/log/alternatives.log
    3         30 kB  /var/log/apt/eipp.log.xz
    3         23 kB  /var/lib/apt/extended_states
    2        6.5 kB  /var/log/faillog
    2        3.5 kB  /opt/license_accepter.sh
    2        1.9 kB  /etc/passwd
    2        1.0 kB  /etc/shadow
    2         903 B  /etc/group
    2         756 B  /etc/gshadow
    2         661 B  /var/lib/dpkg/triggers/File
    2         539 B  /root/.wget-hsts
    2          55 B  /var/lib/ucf/hashfile
    2          38 B  /var/lib/ucf/registry
    2           0 B  /tmp
    2           0 B  /var/lib/apt/lists/lock
    2           0 B  /var/lib/apt/lists/auxfiles
    3           0 B  /var/lib/dpkg/lock-frontend
    3           0 B  /var/lib/dpkg/lock
    2           0 B  /var/lib/dpkg/triggers/Unincorp
    3           0 B  /var/lib/dpkg/updates
    2           0 B  /var/lib/apt/lists/partial
    3           0 B  /var/cache/debconf/passwords.dat
    2           0 B  /etc/.pwd.lock
    3           0 B  /var/cache/apt/archives/partial
    3           0 B  /var/cache/apt/archives/lock
    3           0 B  /var/lib/dpkg/triggers/Lock

Running the following command as described in the readme fails with thousands of lines (one for each sdk file ?) stating that permission is denied.

➜  ~ docker run -it --rm -v $(pwd)/sdk:/sdk thyrlian/android-sdk bash -c 'cp -a $ANDROID_HOME/. /sdk'
cp: cannot create directory '/sdk/./sys/fs/cgroup/cpuset': Permission denied
cp: cannot create directory '/sdk/./sys/fs/cgroup/cpu': Permission denied
cp: cannot create directory '/sdk/./sys/fs/cgroup/cpuacct': Permission denied
cp: cannot create directory '/sdk/./sys/fs/cgroup/blkio': Permission denied
cp: cannot create directory '/sdk/./sys/fs/cgroup/memory': Permission denied
cp: cannot create directory '/sdk/./sys/fs/cgroup/devices': Permission denied
cp: cannot create directory '/sdk/./sys/fs/cgroup/freezer': Permission denied
cp: cannot create directory '/sdk/./sys/fs/cgroup/net_cls': Permission denied
cp: cannot create directory '/sdk/./sys/fs/cgroup/perf_event': Permission denied
cp: cannot create directory '/sdk/./sys/fs/cgroup/net_prio': Permission denied
cp: cannot create directory '/sdk/./sys/fs/cgroup/hugetlb': Permission denied
cp: cannot create directory '/sdk/./sys/fs/cgroup/pids': Permission denied
cp: cannot create directory '/sdk/./sys/fs/cgroup/rdma': Permission denied
cp: cannot create directory '/sdk/./sys/fs/cgroup/systemd': Permission denied
cp: cannot create regular file '/sdk/./sys/fs/ext4/features/lazy_itable_init': Permission denied
cp: cannot create regular file '/sdk/./sys/fs/ext4/features/batched_discard': Permission denied
cp: cannot create regular file '/sdk/./sys/fs/ext4/features/meta_bg_resize': Permission denied
cp: cannot create regular file '/sdk/./sys/fs/ext4/features/metadata_csum_seed': Permission denied
cp: cannot create regular file '/sdk/./sys/fs/ext4/vda1/delayed_allocation_blocks': Permission denied
cp: cannot create regular file '/sdk/./sys/fs/ext4/vda1/session_write_kbytes': Permission denied
cp: cannot create regular file '/sdk/./sys/fs/ext4/vda1/lifetime_write_kbytes': Permission denied
cp: cannot create regular file '/sdk/./sys/fs/ext4/vda1/max_writeback_mb_bump': Permission denied
cp: cannot open '/./sys/fs/ext4/vda1/trigger_fs_error' for reading: Permission denied
cp: cannot create regular file '/sdk/./sys/fs/ext4/vda1/errors_count': Permission denied
cp: cannot create regular file '/sdk/./sys/fs/ext4/vda1/first_error_time': Permission denied
...

I follow the instruction, but this cmd failed:

docker run -it --rm -v $(pwd)/sdk:/sdk thyrlian/android-sdk bash -c 'cp -a $ANDROID_HOME/. /sdk'

error:

docker: Error response from daemon: create $(pwd)/sdk: "$(pwd)/sdk" includes invalid characters for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed. If you intended to pass a host directory, use absolute path.
See 'docker run --help'.

I followed Getting Started , I entered below commands and I get below error:
$docker pull thyrlian/android-sdk
$docker run -it --rm -v $(pwd)/sdk:/sdk thyrlian/android-sdk bash -c 'cp -a $ANDROID_HOME/. /sdk'
$docker pull thyrlian/android-sdk-vnc
$docker run -it -p 5901:5901 -v $(pwd)/sdk:/opt/thyrlian/android-sdk thyrlian/android-sdk-vnc /bin/bash
$sdkmanager "system-images;android-24;default;armeabi-v7a"
$echo "no" | avdmanager create avd -f -n test -k "system-images;android-24;default;armeabi-v7a"
$emulator -avd test -noaudio -no-boot-anim -no-window -accel on &

error:

[1] 123
root@808e0a565ad9:/# ERROR: 32-bit Linux Android emulator binaries are DEPRECATED, to use them
       you will have to do at least one of the following:

       - Use the '-force-32bit' option when invoking 'emulator'.
       - Set ANDROID_EMULATOR_FORCE_32BIT to 'true' in your environment.

       Either one will allow you to use the 32-bit binaries, but please be
       aware that these will disappear in a future Android SDK release.
       Consider moving to a 64-bit Linux system before that happens.

$emulator -avd test -noaudio -no-boot-anim -no-window -force-32bit -accel on &
error:

[1] 434
root@27a7d06b1601:/# [139687693248320]:ERROR:./android/qt/qt_setup.cpp:28:Qt library not found at ../emulator/lib/qt/lib
Could not launch '../emulator/qemu/linux-x86/qemu-system-armel': No such file or directory

[1]+  Exit 2                  emulator -avd test -noaudio -no-boot-anim -no-window -force-32bit -accel on

I'm new to docker :)
Thanks.

Any documentation as to this?

Hi, on my CentOS machine, I run emulator-check, I got

accel:
0
KVM (version 12) is installed and usable.
accel

However, when I run emulator-check in the docker container, I got

accel:
8
/dev/kvm is not found: VT disabled in BIOS or KVM kernel module not loaded
accel

And I cannot run x86_64 emulator, can you help me with this?

I found this project interesting and was trying to install it on my system but I am stuck on an error when trying to update sdk manager-

I searched a bit online but the solutions given are only for java 9 and 10. I have ubuntu 18.04 and java 11. Is there any other solution apart from downgrading java version?

I was concerned about how the Android SDK EULA system would ruin reproducibility, but I saw that you have a solution for that, so I'm wondering a couple of things:

• Can you do a version with the NDK? It's in common use and it would save people from logging into their dockers to install it themselves.
• Can I do a version with the NDK? I'm wondering about those hexadecimal codes. Looks like black magic to me. I don't have to actually use sdkmanager do I? Or is that all done from the command line within the docker? Yeah I'm new...

Many thanks.

I used the docker to start a emulator, but its screen size is 480x320. How could I start a emulator with another size than 480x320

I've been able to get an emulator to start on a macOS in Docker following your instructions... awesome!

However, when ever I start an emulator in Travis (using my own method), it takes almost 5 minutes (on an older ARM emulator).
https://travis-ci.org/brianegan/flutter_architecture_samples/jobs/502926447#L1186

Do you have any suggestions on how I can get an emulator to start faster on Travis?

Should I try running the emulator in docker (doesn't seem like there is any advantage in doing that)?

Or, should I try starting a more recent emulator (which one)?

Or is there an alternative way?

As far as alternatives:

1. Using an emulator default snapshot .
   Seems like it should be possible. The problem is in finding the best way to download the snapshot image (~10GB). Maybe use AWS S3? Or possibly bundle the snapshot image into a docker image and start the emulator in the docker container?
2. Using a Docker checkpoint .

   docker checkpoint create <container name> <checkpointname>
   docker start –checkpoint <checkpointname> <container name>
   

   Still have to find a way to download the checkpoint image to travis (S3?)
   (So far, I have not been able to get this feature to work on my local machine (macOS).)
3. Maintain a running emulator on a server .
   Then connect to it from travis via ssh. Problem is, since travis runs jobs in parallel, would have to maintain multiple emulators and find a way to locate available emulator.
4. Some other way??

(BTW: I tried connecting to Genymotion and it worked. But don't want to pay the price.)

when trying to run some tests using gradlew i'm getting the next error:
Can anyone please help?
Thanks

14:47:51 Checking the license for package Android SDK Build-Tools 28.0.3 in /opt/android-sdk/licenses
14:47:51 Warning: License for package Android SDK Build-Tools 28.0.3 not accepted.
14:47:51 Checking the license for package Android SDK Platform 27 in /opt/android-sdk/licenses
14:47:51 Warning: License for package Android SDK Platform 27 not accepted.
14:47:51
14:47:51 FAILURE: Build failed with an exception.
14:47:51
14:47:51 * What went wrong:
14:47:51 A problem occurred configuring project ':android-sdk'.
14:47:51 > Failed to install the following Android SDK packages as some licences have not been accepted.
14:47:51 platforms;android-27 Android SDK Platform 27
14:47:51 build-tools;28.0.3 Android SDK Build-Tools 28.0.3
14:47:51 To build this project, accept the SDK license agreements and install the missing components using the Android Studio SDK Manager.
14:47:51 Alternatively, to transfer the license agreements from one workstation to another, see http://d.android.com/r/studio-ui/export-licenses.html
14:47:51
14:47:51 Using Android SDK: /opt/android-sdk

At the time of writing, there are 3 different sdkmanager binaries after updating.

$ANDROID_SDK_ROOT/tools/bin/sdkmanager --version #=> 26.1.1
$ANDROID_SDK_ROOT/cmdline-tools/tools/bin/sdkmanager --version #=> 3.6.0
$ANDROID_SDK_ROOT/cmdline-tools/latest/bin/sdkmanager --version #=> 4.0.0

I got problem when run unit test. When run test which uses not ANSI characters it fails.
When I check charmap:
locale charmap it returns
ANSI_X3.4-1968
So is it possible to change default charmap to UTF-8?
I fixed this in container using commands:
apt install locales locale-gen en en_US en_US.UTF-8 update-locale en_US.UTF-8 export LC_ALL=en_US.UTF-8.
But this can be done in more proper way.

android:text="@{$ Packaging appears to become. ???? Abnormal display

I guess license acceptor script could be redundant while there is yes command.

Hey, I am trying all day different configurations and I cannot really make it happen.

When I try to install any .apk I get an error:

root@a717690b4c77:/workspace# adb install /opt/android-sdk/system-images/android-26/google_apis/x86/data/app/SmokeTestApp/SmokeTestApp.apk 
Failed to install /opt/android-sdk/system-images/android-26/google_apis/x86/data/app/SmokeTestApp/SmokeTestApp.apk: Can't find service: package

Listing services of emulator indeed does not return package service and I don't know why.

adb shell service list
Found 6 services:
0	gpu: [android.ui.IGpuService]
1	SurfaceFlinger: [android.ui.ISurfaceComposer]
2	android.service.gatekeeper.IGateKeeperService: []
3	android.security.keystore: [android.security.IKeystoreService]
4	android.hardware.fingerprint.IFingerprintDaemon: []
5	batteryproperties: [android.os.IBatteryPropertiesRegistrar]

Any ideas?

My Dockerfile:

FROM thyrlian/android-sdk
RUN sdkmanager --update
RUN sdkmanager "system-images;android-24;google_apis;armeabi-v7a" --verbose
RUN echo "no" | avdmanager create avd -n test -k "system-images;android-24;google_apis;armeabi-v7a" -b default/armeabi-v7a -f

Hi,
is it possible to customize the screen size at container boot?

I try to create and lunch AVD and here what I get:

$ echo "no" | avdmanager --verbose create avd -n test -k "system-images;android-26;google_apis;x86_64" -b google_apis/x86_64 -f
Picked up _JAVA_OPTIONS: -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap
Do you wish to create a custom hardware profile? [no]
$ avdmanager list avd
Picked up _JAVA_OPTIONS: -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap
Available Android Virtual Devices:
    Name: test
    Path: /root/.android/avd/test.avd
  Target: Google APIs (Google Inc.)
          Based on: Android API 26 Tag/ABI: google_apis/x86_64
$ emulator64-x86 -avd test -no-window -no-boot-anim -noaudio -accel on &
$ ./android-wait-for-emulator
emulator: ERROR: can't find SDK installation directory
emulator: could not find virtual device named 'test'

• What went wrong:
  A problem occurred evaluating project ':app'.

Failed to apply plugin 'com.android.internal.application'.
Android Gradle plugin requires Java 17 to run. You are currently using Java 11.
Your current JDK is located in /usr/lib/jvm/java-11-openjdk-amd64
You can try some of the following options:
- changing the IDE settings.
- changing the JAVA_HOME environment variable.
- changing org.gradle.java.home in gradle.properties.

I am using 'gradlew wrapper' change version to 8.1
but base on some reasons I don't have permission to control our team Jenkins CI such as build args so that I can not type '--build-arg JDK_VERSION=17'

And I think it's time to upgrade your base image because start in AGP 8.x.x, minimum JDK is 17, and you could also upgrade Kotlin version to 1.8.x

I know above requirement upgrading for you seems like period routine, but your image really helps me a lot.

Thanks @thyrlian

hi @thyrlian. i'm facing this issue when try to build image manually using this command : docker build --build-arg GRADLE_VERSION=7.1.1 --build-arg KOTLIN_VERSION=1.6.10 -t android-sdk android-sdk and i got this error

5 107.9 Ign:15 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main i386 Packages
#5 107.9 Ign:16 http://ports.ubuntu.com/ubuntu-ports jammy-updates/multiverse i386 Packages
#5 107.9 Ign:20 http://ports.ubuntu.com/ubuntu-ports jammy-backports/universe i386 Packages
#5 108.1 Ign:23 http://ports.ubuntu.com/ubuntu-ports jammy-security/multiverse i386 Packages
#5 108.1 Ign:25 http://ports.ubuntu.com/ubuntu-ports jammy-security/universe i386 Packages
#5 108.1 Ign:26 http://ports.ubuntu.com/ubuntu-ports jammy-security/restricted i386 Packages
#5 108.1 Ign:28 http://ports.ubuntu.com/ubuntu-ports jammy-security/main i386 Packages
#5 108.1 Err:5 http://ports.ubuntu.com/ubuntu-ports jammy/universe i386 Packages
#5 108.1   404  Not Found [IP: 185.125.190.39 80]
#5 108.1 Ign:6 http://ports.ubuntu.com/ubuntu-ports jammy/restricted i386 Packages
#5 108.1 Ign:8 http://ports.ubuntu.com/ubuntu-ports jammy/multiverse i386 Packages
#5 108.1 Ign:11 http://ports.ubuntu.com/ubuntu-ports jammy/main i386 Packages
#5 108.1 Err:13 http://ports.ubuntu.com/ubuntu-ports jammy-updates/restricted i386 Packages
#5 108.1   404  Not Found [IP: 185.125.190.39 80]
#5 108.1 Ign:14 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe i386 Packages
#5 108.7 Ign:15 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main i386 Packages
#5 108.7 Ign:16 http://ports.ubuntu.com/ubuntu-ports jammy-updates/multiverse i386 Packages
#5 108.7 Err:20 http://ports.ubuntu.com/ubuntu-ports jammy-backports/universe i386 Packages
#5 108.7   404  Not Found [IP: 185.125.190.39 80]
#5 108.7 Err:23 http://ports.ubuntu.com/ubuntu-ports jammy-security/multiverse i386 Packages
#5 108.7   404  Not Found [IP: 185.125.190.39 80]
#5 108.7 Ign:25 http://ports.ubuntu.com/ubuntu-ports jammy-security/universe i386 Packages
#5 108.7 Ign:26 http://ports.ubuntu.com/ubuntu-ports jammy-security/restricted i386 Packages
#5 108.7 Ign:28 http://ports.ubuntu.com/ubuntu-ports jammy-security/main i386 Packages
#5 108.7 Fetched 20.6 MB in 1min 49s (190 kB/s)
#5 108.7 Reading package lists...
#5 108.7 E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/jammy/universe/binary-i386/Packages  404  Not Found [IP: 185.125.190.39 80]
#5 108.7 E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/jammy-updates/restricted/binary-i386/Packages  404  Not Found [IP: 185.125.190.39 80]
#5 108.7 E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/jammy-backports/universe/binary-i386/Packages  404  Not Found [IP: 185.125.190.39 80]
#5 108.7 E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/jammy-security/multiverse/binary-i386/Packages  404  Not Found [IP: 185.125.190.39 80]
#5 108.7 E: Some index files failed to download. They have been ignored, or old ones used instead.
------
executor failed running [/bin/sh -c dpkg --add-architecture i386 &&     apt-get update &&     apt-get dist-upgrade -y &&     apt-get install -y --no-install-recommends libncurses5:i386 libc6:i386 libstdc++6:i386 lib32gcc-s1 lib32ncurses6 lib32z1 zlib1g:i386 &&     apt-get install -y --no-install-recommends openjdk-${JDK_VERSION}-jdk &&     apt-get install -y --no-install-recommends git wget unzip &&     apt-get clean && rm -rf /var/lib/apt/list/*]: exit code: 100

could you please give me some advises for this error? btw i'm using MacPro M1. Thankyou

Following the instructions for Emulator, I get an error:

root@768cc52f988b:~# sdkmanager "platform-tools" "platforms;android-24" "emulator"
Warning: Failed to read or create install properties file.                      
root@768cc52f988b:~#                    ] 10% Installing Android SDK Platform 24

Hello Thyrlian,

First of all, I'd like to thank you for all your effort and these Dockerfiles for the community. Lately, I've been hitting my head against a wall, may be you have an idea about this 👍

I was able to do everything locally in my linux machine, run docker images, unit test and even functional tests with an x86 emulator providing the SDK and project as external volumes. However, I created a small jenkins job with a pipeline and bumped into this problem when executing unit tests. It seems that something is going on with the jenkins slave node.

:presentation:testClasses
:presentation:testURI has a query component
java.lang.IllegalArgumentException: URI has a query component
	at java.io.File.<init>(File.java:427)
	at org.gradle.internal.classloader.ClasspathUtil$1.visitClassPath(ClasspathUtil.java:64)
	at org.gradle.internal.classloader.ClassLoaderVisitor.visit(ClassLoaderVisitor.java:41)
	at org.gradle.internal.classloader.ClassLoaderVisitor.visitParent(ClassLoaderVisitor.java:82)
	at org.gradle.internal.classloader.VisitableURLClassLoader.visit(VisitableURLClassLoader.java:49)
	at org.gradle.internal.classloader.ClassLoaderVisitor.visit(ClassLoaderVisitor.java:38)
	at org.gradle.internal.classloader.ClasspathUtil.getClasspath(ClasspathUtil.java:58)
	at org.gradle.process.internal.worker.DefaultWorkerProcessFactory.create(DefaultWorkerProcessFactory.java:67)
	at org.gradle.api.internal.tasks.testing.worker.ForkingTestClassProcessor.forkProcess(ForkingTestClassProcessor.java:95)
	at org.gradle.api.internal.tasks.testing.worker.ForkingTestClassProcessor.processTestClass(ForkingTestClassProcessor.java:85)
	at org.gradle.api.internal.tasks.testing.processors.RestartEveryNTestClassProcessor.processTestClass(RestartEveryNTestClassProcessor.java:52)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
	at org.gradle.internal.dispatch.FailureHandlingDispatch.dispatch(FailureHandlingDispatch.java:29)
	at org.gradle.internal.dispatch.AsyncDispatch.dispatchMessages(AsyncDispatch.java:133)
	at org.gradle.internal.dispatch.AsyncDispatch.access$000(AsyncDispatch.java:34)
	at org.gradle.internal.dispatch.AsyncDispatch$1.run(AsyncDispatch.java:73)
	at org.gradle.internal.operations.BuildOperationIdentifierPreservingRunnable.run(BuildOperationIdentifierPreservingRunnable.java:39)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
	at java.lang.Thread.run(Thread.java:748)
URI has a query component
java.lang.IllegalArgumentException: URI has a query component ......

This is how the pipeline looks like

pipeline {
  agent {
    dockerfile {
        label 'slave'
        dir 'ci'
        filename 'Dockerfile'
        args '--privileged -v /home/jaime/Android/Sdk:/opt/android-sdk'
     }
  }

  stages {
    stage('Presentation tests'){
      steps {
          sh './gradlew --daemon clean :presentation:test'
       }
    }

    stage('Domain tests'){
      steps{
        sh './gradlew --daemon clean :domainodigeo:test'
      }
    }
  }
}

I know I don't actually need the "clean" (was just doing some testing)

The filename Dockerfile is similar to the VNC one without downloading the android SDK (since I have it in the host machine) and no ssh configuration. As I said, this only happen when working with remote machines, I guess is something related to paths/dirs ?

Cheers,
Thanks :)

Is it possible to add Android SDK platforms to be added in the dockerfile?
Is it reasonable to put it?

I was just wondering if it could speed up builds if the Android SDKs are already added in the Dockerfile rather than adding them after.

        docker {
                        // android sdk环境  构建完成自动删除容器
                        image "thyrlian/android-sdk:latest"
                        // 缓存gradle工具  :ro或者 :rw 前者表示容器只读，后者表示容器对数据卷是可读可写的。默认情况下是可读可写的
                        args " -v /var/cache/gradle:/root/.gradle:rw -v /my/android/sdk:/opt/android-sdk:ro "
                        reuseNode true // 使用根节点
                    }

13:49:49 Warning: License for package Android SDK Platform 28 not accepted.
13:49:49
13:49:49 FAILURE: Build failed with an exception.
13:49:49
13:49:49 * What went wrong:
13:49:49 Could not determine the dependencies of task ':accesscontrol:compileReleaseJavaWithJavac'.
13:49:49 > Failed to install the following Android SDK packages as some licences have not been accepted.
13:49:49 patcher;v4 SDK Patch Applier v4
13:49:49 build-tools;28.0.3 Android SDK Build-Tools 28.0.3
13:49:49 platform-tools Android SDK Platform-Tools
13:49:49 tools Android SDK Tools
13:49:49 platforms;android-28 Android SDK Platform 28
13:49:49 emulator Android Emulator
13:49:49 To build this project, accept the SDK license agreements and install the missing components using the Android Studio SDK Manager.
13:49:49 Alternatively, to transfer the license agreements from one workstation to another, see http://d.android.com/r/studio-ui/export-licenses.html
13:49:49
13:49:49 Using Android SDK: /opt/android-sdk

Hi!

I'm playing with emulator. The goal is to run the emulator and connect to it via VNC.
I've done with the following steps, succeeded to connect to VNC, but saw only a blank rectangle instead of amulator window.
Help me please :)

I've tried these steps on both Docker for Mac and on Cloud computing services pod on Hetzner (Ubuntu 20.04, AMD EPYC 2nd Gen processor). In both cases I've got the same black rectangle.

Here are the steps I've done:
Host
⁃ docker run -it --rm -v $(pwd)/sdk:/sdk thyrlian/android-sdk bash -c 'cp -a $ANDROID_SDK_ROOT/. /sdk'
⁃ docker run -d -p 5901:5901 --name emulator -v $(pwd)/sdk:/opt/android-sdk thyrlian/android-sdk-vnc
⁃ docker exec -it emulator bash

Container
⁃ sdkmanager "platform-tools" "platforms;android-25" "emulator"
⁃ sdkmanager "system-images;android-25;google_apis;armeabi-v7a"
⁃ echo "no" | avdmanager create avd -n test -k "system-images;android-25;google_apis;armeabi-v7a"
⁃ emulator -avd test -noaudio -no-boot-anim -gpu off

Output of the emulator:

emulator: WARNING: encryption is off
emulator: INFO: QtLogger.cpp:68: Warning: XKeyboard extension not present on the X server ((null):0, (null))


NativeEventFilter: warning: cannot get mod mask info
WARNING. Using fallback path for the emulator registration directory.
Your emulator is out of date, please update by launching Android Studio:
 - Start Android Studio
 - Select menu "Tools > Android > SDK Manager"
 - Click "SDK Tools" tab
 - Check "Android Emulator" checkbox
 - Click "OK"

emulator: ERROR: AdbHostServer.cpp:102: Unable to connect to adb daemon on port: 5037
emulator: emulator window was out of view and was recentered

Then on host (Mac) I've connected to VNC server via Screen Sharing.

During the build process, the tools in $ANDROID_HOME/tools/bin are installed but are not marked executable for group or other. Hence, when running this image (for instance, in CI) with a different user, the sdkmanager binary is not directly executable.

Execution failed for task ':app:connectedDebugAndroidTest'.

com.android.builder.testing.api.DeviceException: No connected devices!

Description

I've got this error when make attempts to build image

> [ 7/11] RUN chmod +x /opt/license_accepter.sh && /opt/license_accepter.sh /opt/android-sdk:
#11 0.155 /bin/sh: 1: /opt/license_accepter.sh: not found

Steps To Reproduce

Steps to reproduce the issue (do make sure that you're able to reproduce the issue when following the steps below).

1. Go to root of the project
2. Run docker build -t android-sdk android-sdk

Actual Result

> [ 7/11] RUN chmod +x /opt/license_accepter.sh && /opt/license_accepter.sh /opt/android-sdk:
#11 0.155 /bin/sh: 1: /opt/license_accepter.sh: not found

Expected Behavior

Successfully built image

Environment

• Clonned repo from master
• Windows 10

According to release note

Since Gradle 8.3+, Gradle start to supports running on Java 20, even in Gradle 8.4 also supports Java 21.

I am not sure as my perspective, docker image can use JDK 21 and also compatible for Android JDK 17 based project ?

cc @thyrlian

Please have a look here https://youtrack.jetbrains.com/issue/KT-24946 .

My docker build failed with reported Exception with the latest of your android-sdk images.

android:text="@{$+TicketDetailsViewModel.coupon.saleNum}" Pack the local computer normally

I fixed the Android 28 issue in PR #17. We have been using the latest image but with the v3 upgrade we locked down to the previous version on docker hub, 2.5. Unfortunately our builds fail due to not having android-28 fix, there aren't any tags that contain this working version, unless we also are prepared for the upgraded ubuntu & gradle environment.

Would it be possible to push a 2.6 tag to one of the older build hashes that contains the android 28 fixes prior to v3?

AGP 7.x and Gradle 7.x updates will need JDK 11, thus we might want to start preparing a branch that supports JDK 11.

https://android-developers.googleblog.com/2020/12/announcing-android-gradle-plugin.html

Hi,

I've been using the same Jenkins build with the thyrlian/android-sdk image for a while now. Around May 18 it stopped working with a strange error, see below.
There were no significant changes on my end and according to free there are ~15GB of memory available. Any idea what might cause this?

           +frontend | --> FROM thyrlian/android-sdk
             context | --> local context .
            [...]
           +frontend | --> RUN sdkmanager --install "build-tools;29.0.2" "platforms;android-30"
           +frontend | [0.002s][warning][os,thread] Failed to start thread - pthread_create failed (EPERM) for attributes: stacksize: 1024k, guardsize: 4k, detached.
           +frontend | #
           +frontend | # There is insufficient memory for the Java Runtime Environment to continue.
           +frontend | # Cannot create worker GC thread. Out of system resources.
           +frontend | # An error report file with more information is saved as:
           +frontend | # //hs_err_pid13.log
           +frontend | �[91mCommand /bin/sh -c 'sdkmanager --install "build-tools;29.0.2" "platforms;android-30"' failed with exit code 1
           +frontend | �[0m
           +frontend | ERROR: Command exited with non-zero code: RUN sdkmanager --install "build-tools;29.0.2" "platforms;android-30"
Repeating the output of the command that caused the failure
================================ FAILURE [main] ================================
           +frontend *failed* | FLAVOR_NAME=appTest GRADLE_BUILD_TASK=assembleAppTest
           +frontend *failed* | --> RUN sdkmanager --install "build-tools;29.0.2" "platforms;android-30"
           +frontend *failed* | [0.002s][warning][os,thread] Failed to start thread - pthread_create failed (EPERM) for attributes: stacksize: 1024k, guardsize: 4k, detached.
           +frontend *failed* | #
           +frontend *failed* | # There is insufficient memory for the Java Runtime Environment to continue.
           +frontend *failed* | # Cannot create worker GC thread. Out of system resources.
           +frontend *failed* | # An error report file with more information is saved as:
           +frontend *failed* | # //hs_err_pid13.log
           +frontend *failed* | �[91mCommand /bin/sh -c 'sdkmanager --install "build-tools;29.0.2" "platforms;android-30"' failed with exit code 1
           +frontend *failed* | �[0m           +frontend *failed* | ERROR: Command exited with non-zero code: RUN sdkmanager --install "build-tools;29.0.2" "platforms;android-30"

Hi. I've been using this Docker image today and was successful in getting it running and updating packages etc.

However the APK I am interested in testing only runs on ARM architecture, not x86. I've done the following but can't figure out how to get NoVNC to connect to this new emulator that is running?

root@18bb56082245:/# sdkmanager --list --verbose
root@18bb56082245:/# sdkmanager "system-images;android-25;google_apis;armeabi-v7a"
root@18bb56082245:/# echo "no" | avdmanager create avd -n test -k "system-images;android-25;google_apis;armeabi-v7a"
root@18bb56082245:/# avdmanager list avd
Parsing /root/build-tools/27.0.1/package.xmlParsing /root/emulator/package.xmlParsing /root/patcher/v4/package.xmlParsing /root/platform-tools/package.xmlParsing /root/platforms/android-25/package.xmlParsing /root/system-images/android-25/google_apis/armeabi-v7a/package.xmlParsing /root/system-images/android-25/google_apis/x86_64/package.xmlParsing /root/tools/package.xmlAvailable Android Virtual Devices:
    Name: samsung_galaxy_s6_7.1.1
  Device: Samsung Galaxy S6 (User)
    Path: /root/android_emulator
  Target: Google APIs (Google Inc.)
          Based on: Android 7.1.1 (Nougat) Tag/ABI: google_apis/x86_64
---------
    Name: test
    Path: /root/.android/avd/test.avd
  Target: Google APIs (Google Inc.)
          Based on: Android 7.1.1 (Nougat) Tag/ABI: google_apis/armeabi-v7a
root@18bb56082245:/# ./emulator64-arm -avd test -noaudio -no-boot-anim -no-window -accel on &
root@18bb56082245:/# adb devices
List of devices attached
emulator-5554	device

So I think I have successfully installed and launched the ARM emulator, but I can't figure out how to attach that session to the NoVNC console... Does NoVNC spawn inside of the emulator image itself, or is it something in the Docker rc files that runs it?

Thanks in advance

huhailang@ubuntu:~$ adb connect 127.0.0.1:5037
adb server version (41) doesn't match this client (39); killing...
ADB server didn't ACK
Full server startup log: /tmp/adb.1000.log
Server had pid: 55064
--- adb starting (pid 55064) ---
adb I 11-04 20:16:14 55064 55064 main.cpp:57] Android Debug Bridge version 1.0.39
adb I 11-04 20:16:14 55064 55064 main.cpp:57] Version 1:8.1.0+r23-5ubuntu2
adb I 11-04 20:16:14 55064 55064 main.cpp:57] Installed as /usr/lib/android-sdk/platform-tools/adb
adb I 11-04 20:16:14 55064 55064 main.cpp:57]
error: could not install smartsocket listener: Address already in use

huhailang@ubuntu:~$ ps aux | grep adb
root 55298 0.0 0.1 248128 5896 ? Sl 20:16 0:00 adb -a server nodaemon &
huhaila+ 55457 0.0 0.0 17664 724 pts/1 S+ 20:17 0:00 grep --color=auto adb

The process id 55298 is adb server, it start with the docker container. In addition, no other adb processes were found.
Ive tried multiple variations of this, but none of them seem to work. Any ideas?

We could leverage GitHub Actions to build the images directly here and push them to the registries.

Is there any reason why you aren't building an ARM64 based image variant? With Apple Silicon and AWS Graviton, android developers are more likely to be developing on an ARM based toolchain.

Description

Emulator shows black screen

Steps to reproduce the issue

$ docker run -it --rm -v $(pwd)/sdk:/sdk thyrlian/android-sdk bash -c 'cp -a $ANDROID_SDK_ROOT/. /sdk'
$ docker run -d -p 59.1: 5901 -p 2222:22 -v $(pwd)/sdk:/opt/android-sdk -v ~/.ssh/emulator.pub:/root/.ssh/authorized_keys -v $(pwd)/sdk_builder.sh:/root/sdk_builder.sh -v $(pwd)/com.amazon.kindle.apk:/root/com.amazon.kindle.apk thyrlian/android-sdk-vnc
$ ssh [email protected] -p 2222

root@20448ea13e96:$ bash sdk_builder.sh

I've also tried toggling various gpu options and different system images to no avail.

# sdk_builder.sh

sdkmanager --update
sdkmanager "platform-tools" "platforms;android-24" "platforms;android-25" "emulator"
sdkmanager "system-images;android-24;default;armeabi-v7a"
sdkmanager "system-images;android-25;google_apis;armeabi-v7a"

export QTWEBENGINE_DISABLE_SANDBOX=1

echo 'no' | avdmanager create avd -n 24_test -k "system-images;android-24;default;armeabi-v7a"
echo 'no' | avdmanager create avd -n 25_test -k "system-images;android-25;google_apis;armeabi-v7a"
# INFO: List existing Android Virtual Devices
avdmanager list avd
# launch emulator
 emulator -avd 24_test -no-audio -no-boot-anim -gpu off
# emulator -avd 24_test -no-audio -no-boot-anim -accel on -gpu swiftshader_indirect &

The output looks like that

But rerunning the script a second time round gives just this, without the 'emulator out of date' output

Describe the results you expected

The ability to use the emulator through VNC visually.

The docker file which we are using is below.

FROM thyrlian/android-sdk:6.0

#######################

Node installation

#######################
RUN apt-get update &&
apt-get install -y git wget curl unzip awscli jq
RUN mkdir /usr/local/nvm
ENV NVM_DIR /usr/local/nvm
ENV NODE_VERSION 14.15.1

Install nvm with node and npm

RUN curl https://raw.githubusercontent.com/creationix/nvm/v0.35.3/install.sh | bash
&& . $NVM_DIR/nvm.sh
&& nvm install $NODE_VERSION
&& nvm alias default $NODE_VERSION
&& nvm use default

ENV NODE_PATH $NVM_DIR/v$NODE_VERSION/lib/node_modules
ENV PATH $NVM_DIR/versions/node/v$NODE_VERSION/bin:$PATH
RUN npm --version

#######################

Cordova installation

#######################
ENV CORDOVA_VERSION=10.0.0
CODE_PUSH_CLI_VERSION=3.0.0
# Fix for the issue with Selenium, as described here:
# SeleniumHQ/docker-selenium#87
DBUS_SESSION_BUS_ADDRESS=/dev/null

RUN npm install -g cordova@"$CORDOVA_VERSION" code-push-cli@"$CODE_PUSH_CLI_VERSION" &&
mkdir -p /root/.cache/yarn/

Install Accept Android SDK licenses

RUN yes y | ${ANDROID_HOME}/tools/bin/sdkmanager --licenses

RUN cordova telemetry off

#######################

Additions to android

#######################
WORKDIR /
ENV ANDROID_SDK_ROOT /opt/android-sdk

Preserved for backwards compatibility

ENV ANDROID_HOME /opt/android-sdk

RUN yes | sdkmanager --licenses

RUN touch /root/.android/repositories.cfg

Emulator and Platform tools

RUN yes | sdkmanager "emulator" "platform-tools"

SDKs

Please keep these in descending order!

The yes is for accepting all non-standard tool licenses.

RUN yes | sdkmanager --update --channel=3

Please keep all sections in descending order!

RUN yes | sdkmanager
"platforms;android-29"
"build-tools;29.0.2"
"extras;android;m2repository"
"extras;google;m2repository"
"extras;google;google_play_services"
"add-ons;addon-google_apis-google-24"
"add-ons;addon-google_apis-google-23"
"add-ons;addon-google_apis-google-22"
"add-ons;addon-google_apis-google-21"

Create Cordova App

RUN cordova create android_app

Move to cordova app

WORKDIR /android_app

Adding platform

RUN cordova platform add android

Replacing minimum android support version

RUN sed -i -e 's/android:minSdkVersion=""/android:minSdkVersion="15"/g' platforms/android/CordovaLib/AndroidManifest.xml
RUN sed -i -e 's/defaultMinSdkVersion=""/defaultMinSdkVersion=15/g' platforms/android/build.gradle

WORKDIR /

Add Scripts

ADD /generate_app /.

Add keystore, build.json, remove_permissions.js to app

RUN mkdir -p /android_app/keystore

ADD /keystore/openn_dapper.keystr /android_app/keystore/openn_dapper.keystore
ADD /keystore/openn_v2.keystr /android_app/keystore/openn_v2.keystore

ADD /build.json /android_app/build.json
ADD /remove_permissions.js /android_app/remove_permissions.js

WORKDIR /

during the Jenkins job execution, the error raised

‘Jenkins’ doesn’t have label ‘android’

and here is an error log

Error during callback
com.github.dockerjava.api.exception.BadRequestException: {"message":"OCI runtime create failed: container_linux.go:345: starting container process caused "process_linux.go:430: container init caused \"rootfs_linux.go:58: mounting \\\"/Users/user/Desktop/master/authorized_keys\\\" to rootfs \\\"/var/lib/docker/overlay2/e87c57b43e7a5d998da41741a539ae48a207f42752bd3ab715fb1e65b9d8a434/merged\\\" at \\\"/var/lib/docker/overlay2/e87c57b43e7a5d998da41741a539ae48a207f42752bd3ab715fb1e65b9d8a434/merged/root/.ssh/authorized_keys\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type"}

at com.github.dockerjava.netty.handler.HttpResponseHandler.channelRead0(HttpResponseHandler.java:99)
at com.github.dockerjava.netty.handler.HttpResponseHandler.channelRead0(HttpResponseHandler.java:33)
at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.handler.logging.LoggingHandler.channelRead(LoggingHandler.java:241)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:438)
at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310)
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:284)
at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:253)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:287)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1334)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:926)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:134)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:644)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:579)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:496)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:458)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:138)
at java.lang.Thread.run(Thread.java:748)

Hi,

first of all, this is an awesome Image to build Android applications.

I tried to combine it in a container that is based on jenkins/ssh-slave so it can be used from my Jenkins with Azure Container Instances.

Do you know of any android sdk image that is as great as yours and is based on jenkins/ssh-slave? If not, do you think about creating one?

Regards

Hello @thyrlian ,

Could you update public version docker image Gradle version from 6.7 to 6.8.3 and Kotlin version from 1.4.10 to 1.5.0 ?

I know we can changed version locally but our devOps use public version and I don't have right to modified it

Please update

Thanks !

李先生您好！

請問方便更新一下目前公用的docker image嗎?

我們DevOps目前不採用客製化image且我也沒有權限可以進行修改

因此需要仰賴您的image更新

感謝 !

Hi,

Just an FYI it is illegal to create public docker images containing the Android SDK as per response from Google.

Cheers