docker: migrate to python

README.adoc

@@ -418,7 +418,7 @@ docker ps -a
 ....
 * `./run-docker start`: start the container as daemon on the background.
 +
-Needed only after reboot, or if you call `stop` to save CPU or memory resources.
+Needed only after reboot, or if you run `./run-docker stop` to save CPU or memory resources.
 +
 The container can now be seen on the list of running containers:
 +
@@ -427,14 +427,12 @@ docker ps
 ....
 * `./run-docker sh`: open a shell on a previously started Docker daemon.
 +
-Quit the shell as usual with `Ctrl`
+Quit the shell as usual with `Ctrl-D`
 +
-Can be called multiple times to open multiple shells.
+Can be called multiple times from different host terminals to open multiple shells.
 
 The host git top level directory is mounted inside the guest with a link:https://stackoverflow.com/questions/23439126/how-to-mount-a-host-directory-in-a-docker-container[Docker volume], which means for example that you can use your host's GUI text editor directly on the files. Just don't forget that if you nuke that directory on the guest, then it gets nuked on the host as well!
 
-TODO make files created inside Docker be owned by the current user in host instead of `root`: https://stackoverflow.com/questions/23544282/what-is-the-best-way-to-manage-permissions-for-docker-shared-volumes
-
 In order to use functionality such as <<gdb>> from inside Docker, you need a second shell inside the container. You can either do that from another shell with:
 
 ....
@@ -478,6 +476,8 @@ To actually delete the Docker build, run:
 # sudo rm -rf out.docker
 ....
 
+TODO make files created inside Docker be owned by the current user in host instead of `root`: https://stackoverflow.com/questions/23544282/what-is-the-best-way-to-manage-permissions-for-docker-shared-volumes
+
 [[prebuilt]]
 === Prebuilt Buildroot setup