I successfully ran kpw4 image in docker.

zaoqi · 07-09-2019, 12:55 PM

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?

NiLuJe · 07-09-2019, 02:34 PM

In a shocking twist, start x. Or lab126_gui.

coplate · 07-09-2019, 10:08 PM

Quote:

Originally Posted by 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

zaoqi · 07-11-2019, 01:18 PM

Quote:

Originally Posted by 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.

zaoqi · 07-11-2019, 01:27 PM

Quote:

Originally Posted by 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

coplate · 07-11-2019, 11:30 PM

Quote:

Originally Posted by 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

NiLuJe · 07-12-2019, 12:28 AM

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

.

zaoqi · 07-14-2019, 01:24 AM

Quote:

Originally Posted by 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

zaoqi · 07-14-2019, 01:26 AM

Quote:

Originally Posted by 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

trcm · 07-16-2019, 07:58 AM

If this is basically using Qemu inside Docker, why not just avoid Docker and use Qemu directly?

knc1 · 07-16-2019, 11:00 AM

Quote:

Originally Posted by trcm

If this is basically using Qemu inside Docker, why not just avoid Docker and use Qemu directly?

Actually, its more like running Qemu-static within a chroot.
Ah, but that is what Docker is, anyway.

07-09-2019, 12:55 PM	#1
zaoqi github.com/zaoqi Posts: 87 Karma: 32020 Join Date: Mar 2017 Location: - Zhejiang China Device: Boox c67ml,Note S,Max2,KT3,KPW4,Kobo AurdHD,Touch N905C	I successfully ran kpw4 image in docker. 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? Last edited by zaoqi; 07-16-2019 at 04:06 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Is there anyway I can jailbreak my kpw4 on 5.10.3?	Au3C2	Kindle Developer's Corner	6	05-22-2019 06:56 AM
KPW4 battery life with audiobooks?	ehesh	Amazon Kindle	7	11-27-2018 11:21 PM
I ran over it with my car	iPatty	Amazon Fire	12	09-22-2012 07:53 PM
What if you ran your bookstore like a library?	donovanh	News	14	04-23-2008 10:28 AM

07-09-2019, 02:34 PM	#2
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	In a shocking twist, start x. Or lab126_gui.

07-12-2019, 12:28 AM	#7
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	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 .

07-16-2019, 07:58 AM	#10
trcm Connoisseur Posts: 96 Karma: 100000 Join Date: Dec 2018 Location: London Device: Kobo Libra H2O	If this is basically using Qemu inside Docker, why not just avoid Docker and use Qemu directly?