Mobileread
I successfully ran kpw4 image in docker.
#1  zaoqi 07-09-2019, 11:55 AM
preparation:
configure binfmt-support on the Docker host (works locally or remotely, i.e: using boot2docker)
Code
$ docker run --rm --privileged multiarch/qemu-user-static:register --reset

Dockerfile:
Code
FROM multiarch/busybox:armel
ADD update_kindle_all_new_paperwhite_v2_5.11.2_rootfs.tgz /
generate update_kindle_all_new_paperwhite_v2_5.11.2_rootfs. tgz:
Code
$ kindletool extract update_kindle_all_new_paperwhite_v2_5.11.2.bin .
$ gzip -d rootfs.img.gz
$ gnome-disk-image-mounter rootfs.img ## or mount rootfs.img ...
$ cd <mount point>
$ sudo tar -czvf <path to update_kindle_all_new_paperwhite_v2_5.11.2_rootfs.tgz> .

to run it
Code
$ docker build -t kpw4 .
$ docker run -it --rm kpw4 /bin/sh
at least cvm works:
Code
$ docker run -it --rm kpw4 /bin/sh
# /usr/java/bin/cvm
Does anyone know how to start the system UI?
Reply 

#2  NiLuJe 07-09-2019, 01:34 PM
In a shocking twist, start x. Or lab126_gui.
Reply 

#3  coplate 07-09-2019, 09:08 PM
Quote zaoqi
preparation:
configure binfmt-support on the Docker host (works locally or remotely, i.e: using boot2docker)
Code
$ docker run --rm --privileged multiarch/qemu-user-static:register --reset

Dockerfile:
Code
FROM multiarch/alpine:armhf-edge
ADD update_kindle_all_new_paperwhite_v2_5.11.2_rootfs.tgz /
generate update_kindle_all_new_paperwhite_v2_5.11.2_rootfs. tgz:
Code
$ kindletool extract update_kindle_all_new_paperwhite_v2_5.11.2.bin .
$ gzip -d rootfs.img.gz
$ gnome-disk-image-mounter rootfs.img ## or mount rootfs.img ...
$ cd <mount point>
$ sudo tar -czvf <path to update_kindle_all_new_paperwhite_v2_5.11.2_rootfs.tgz> .

Does anyone know how to start the system UI?


What is your docker run command to start the kindle image?

I'm trying with PW, but I'm not great with docker and am getting :

Code
coplate@ubuntu:~/PW10$ sudo docker run pw10
docker: Error response from daemon: No command specified.
Edit:
re-ran the tar on real linux, not windows 10, and now it is working, well: bash is runnign, but not sure what is running.

it mostly looks like standard alpine, with a bunch of extra files in folders
Reply 

#4  zaoqi 07-11-2019, 12:18 PM
Quote coplate
What is your docker run command to start the kindle image?

it mostly looks like standard alpine, with a bunch of extra files in folders
at least cvm works.
Reply 

#5  zaoqi 07-11-2019, 12:27 PM
Quote coplate
What is your docker run command to start the kindle image?

Edit:
re-ran the tar on real linux, not windows 10, and now it is working, well: bash is runnign, but not sure what is running.
It's busybox of Kindle

Code
$ docker run -it --rm multiarch/alpine:armhf-edge /bin/sh
/ # ls -lh /bin/busybox
-rwxr-xr-x 1 root root 929.2K Jun 12 17:57 /bin/busybox
/ # ls -lh /bin/sh
lrwxrwxrwx 1 root root 12 Jul 3 11:01 /bin/sh -> /bin/busybox
$ docker run -it --rm kpw4 /bin/sh
/ # ls -lh /bin/busybox
-rwxr-xr-x 1 root root 886.5K May 22 22:12 /bin/busybox
/ # ls -lh /bin/sh
lrwxrwxrwx 1 root root 7 May 22 22:52 /bin/sh -> busybox
Reply 

#6  coplate 07-11-2019, 10:30 PM
Quote zaoqi
preparation:
configure binfmt-support on the Docker host (works locally or remotely, i.e: using boot2docker)
Code
$ docker run --rm --privileged multiarch/qemu-user-static:register --reset

Dockerfile:
Code
FROM multiarch/alpine:armhf-edge
ADD update_kindle_all_new_paperwhite_v2_5.11.2_rootfs.tgz /
generate update_kindle_all_new_paperwhite_v2_5.11.2_rootfs. tgz:
Code
$ kindletool extract update_kindle_all_new_paperwhite_v2_5.11.2.bin .
$ gzip -d rootfs.img.gz
$ gnome-disk-image-mounter rootfs.img ## or mount rootfs.img ...
$ cd <mount point>
$ sudo tar -czvf <path to update_kindle_all_new_paperwhite_v2_5.11.2_rootfs.tgz> .

to run it
Code
$ docker build -t kpw4 .
$ docker run -it --rm kpw4 /bin/sh
at least cvm works:
Code
$ docker run -it --rm kpw4 /bin/sh
# /usr/java/bin/cvm
Does anyone know how to start the system UI?


'start x' or 'start framework' would work in "upstart" processes were working in docker, but apparently that doesn't really work?

You can try '/bin/sh /etc/upstart/framework' but you'll get a lot of errors
Reply 

#7  NiLuJe 07-11-2019, 11:28 PM
Yeah, I honestly wouldn't have expected the GUI to work. Nor a lot of other things.

It's a giant game of dominoes, and one wrong move means nothing works. And theses dominoes expect some very peculiar things you'll never see anywhere but on a real Kindle HW.

It *is* probably useful for poking at mostly standalone/inert things in a slightly easier manner, though, if that's your kind of thing .
Reply 

#8  zaoqi 07-14-2019, 12:24 AM
Quote coplate
'start x' or 'start framework' would work in "upstart" processes were working in docker, but apparently that doesn't really work?

You can try '/bin/sh /etc/upstart/framework' but you'll get a lot of errors
https://duckduckgo.com/?q=docker+x11

x11 cannot work directly in docker
Reply 

#9  zaoqi 07-14-2019, 12:26 AM
Quote coplate
'start x' or 'start framework' would work in "upstart" processes were working in docker, but apparently that doesn't really work?

You can try '/bin/sh /etc/upstart/framework' but you'll get a lot of errors
`cvm` may need to be started manually
Reply 

#10  trcm 07-16-2019, 06:58 AM
If this is basically using Qemu inside Docker, why not just avoid Docker and use Qemu directly?
Reply 

  Next »  Last »  (1/2)
Today's Posts | Search this Thread | Login | Register