android-emulator: api36-v4 — pin emulator 36.1.9; bind socat to pod IP
Two final fixes from the live debugging session: (1) sdkmanager-latest emulator 36.6.11 hangs before executing a single guest instruction in this pod (KVM and TCG alike, every gpu mode, crash-reporting on or off) while 36.1.9 boots Android in ~107s — the entrypoint now pins build 13823996 on the PVC; (2) the emulator already listens on 127.0.0.1:5555, so socat's wildcard bind died with EADDRINUSE and its exit restarted the pod right after a successful boot — socat now binds the pod IP only.
This commit is contained in:
parent
85dbec6108
commit
577267cd97
3 changed files with 23 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-v3 .
|
||||
# docker push forgejo.viktorbarzin.me/viktor/android-emulator:api36-v3
|
||||
# docker build -t forgejo.viktorbarzin.me/viktor/android-emulator:api36-v4 .
|
||||
# docker push forgejo.viktorbarzin.me/viktor/android-emulator:api36-v4
|
||||
FROM eclipse-temurin:17-jdk-jammy
|
||||
|
||||
ENV DEBIAN_FRONTEND=noninteractive
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue