android-emulator: api36-v3 — avdmanager must run from inside the SDK root
v2's marker fix proved the install completes, but avdmanager still saw no system images: it IGNORES ANDROID_SDK_ROOT (and has no --sdk_root), deriving the SDK root from its own toolsdir — /opt/android in our image, while packages live on the PVC at /sdk. v3 seeds cmdline-tools into /sdk/cmdline-tools/latest once and runs avdmanager from there, so it resolves the PVC as the SDK root.
This commit is contained in:
parent
5e8a988858
commit
85dbec6108
3 changed files with 14 additions and 5 deletions
|
|
@ -4,8 +4,8 @@
|
|||
# cmdline-tools and the native libraries the emulator needs at runtime.
|
||||
#
|
||||
# Rebuild + push (rare — only when tool/library versions bump):
|
||||
# docker build -t forgejo.viktorbarzin.me/viktor/android-emulator:api36-v2 .
|
||||
# docker push forgejo.viktorbarzin.me/viktor/android-emulator:api36-v2
|
||||
# docker build -t forgejo.viktorbarzin.me/viktor/android-emulator:api36-v3 .
|
||||
# docker push forgejo.viktorbarzin.me/viktor/android-emulator:api36-v3
|
||||
FROM eclipse-temurin:17-jdk-jammy
|
||||
|
||||
ENV DEBIAN_FRONTEND=noninteractive
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue