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

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.