budtmo/docker-android

[Documentation and its use case] Changing init.rc and ramdisk.img

Open

#161 opened on May 26, 2019

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Python (6,668 stars) (1,044 forks)batch import
help wanted

Description

I'm trying to change the init.rc file through the ramdisk.img. I found that the ramdisk.img is saved under /root/system-images/android-26/google_apis/x86/ramdisk.img

I've unpacked the ramdisk.img via the following guide and than repacked it back. http://linuxkernel51.blogspot.com/2016/11/unpack-modify-and-repack-ramdiskimg.html

When I copy the new image to the /root/system-images/android-26/google_apis/x86/ramdisk.img destination and restarting the docker container the container fails to boot.

" 2019-05-26 08:51:30,281 INFO exited: openbox (exit status 1; not expected) 2019-05-26 08:51:30,284 INFO exited: x11vnc (exit status 1; not expected) 2019-05-26 08:51:33,216 INFO exited: auto-recording (exit status 0; expected) 2019-05-26 08:51:34,220 INFO spawned: 'xvfb' with pid 161 2019-05-26 08:51:34,223 INFO spawned: 'openbox' with pid 162 2019-05-26 08:51:34,225 INFO spawned: 'x11vnc' with pid 163 2019-05-26 08:51:34,227 INFO exited: xvfb (exit status 1; not expected) 2019-05-26 08:51:34,233 INFO gave up: xvfb entered FATAL state, too many start retries too quickly 2019-05-26 08:51:34,234 INFO exited: x11vnc (exit status 1; not expected) 2019-05-26 08:51:34,240 INFO gave up: x11vnc entered FATAL state, too many start retries too quickly 2019-05-26 08:51:34,240 INFO exited: openbox (exit status 1; not expected) 2019-05-26 08:51:35,242 INFO gave up: openbox entered FATAL state, too many start retries too quickly 2019-05-26 08:51:36,421 INFO exited: docker-appium (exit status 1; not expected) "

Am I doing something wrong in the process?

Docker Image: budtmo/docker-android-x86-8.0

Expected Behavior

Change in ramdisk.img should apply changes in init.rc file.

Actual Behavior

docker container fails to load.

Contributor guide

Tech stack
dockerandroid
Domain
devops
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Android boot processDocker basicsramdisk.img structureinit.rc syntax
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the ramdisk.img structure for the specific Android image (android 26, google apis, x86) used in the Docker container. Check if the repacked ramdisk.img is properly signed or if the init.rc modifications are compatible. Look at the docker android repository's Dockerfile and startup scripts (e.g., https://github.com/budtmo/docker android/blob/master/Dockerfile) to understand how the ramdisk.img is integrated. Examine the error logs showing xvfb, openbox, x11vnc failure, which may indicate a dependency issue. Consider testing with an unmodified ramdisk.img to confirm the base image works before investigating the modifications.