Tiny Core Linux
Tiny Core Extensions => TCE Talk => Topic started by: nuxlli on February 14, 2015, 01:00:51 AM
-
Hello everyone,
I think most people here already know the http://docker.com (http://docker.com), and perhaps a good amount of people also have knowledge of a parallel project that allows the use of Docker in Mac OS X through a virtual machine called https://github.com/boot2docker/boot2docker (https://github.com/boot2docker/boot2docker).
The boot2docker project currently uses a custom x86_64 kernel (having aufs support being the main motivation for this), and a distribution using the x86 packages of Tiny Core Linux.
All this is mounted on a bootable iso on VirtualBox, and here lies a problem and my question. For a full support of VirtualBox resources, VBoxGuest Additions must be installed. But despite the x86_64 kernel from boot2docker, the user space is x86, thus making it impossible to install all the features of VBoxGuest Additions. (more information https://github.com/boot2docker/boot2docker/blob/master/Dockerfile#L131-L151 (https://github.com/boot2docker/boot2docker/blob/master/Dockerfile#L131-L151))
Today, boot2docker is mounted with a user space in x86 because of the lack of three extensions on Tiny Core Linux x86_64: acpid, libiconv and ntpclient.
In my research I found that the "source" for the libiconv generation is in x86 http://www.tinycorelinux.net/5.x/x86/tcz/src/libiconv/ (http://www.tinycorelinux.net/5.x/x86/tcz/src/libiconv/). I believe that porting in this case is simpler. But the acpid and libiconv packages do not offer an extension framework anywhere (at least that I could find).
How could I proceed to have these three extensions on the x86_64 platform? And in the event that I even have to port them for x86_64 what would be the steps to do it (besides probable adjustments in the source code of these extensions)?
-
There is no need for libiconv as the iconv functions are supplied by glibc (for some time now).
Please feel free to submit extensions for acpid and ntpclient - the wiki explains how to do this.
-
Searched for the password for user tc in boot2docker, had to change it before ssh was possible.
What is the default password for user tc ?
login as: tc
tc@192.168.8.157's password:
Access denied
tc@192.168.8.157's password:
## .
## ## ## ==
## ## ## ## ## ===
/"""""""""""""""""\___/ ===
~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ / ===- ~~~
\______ o __/
\ \ __/
\____\_______/
_ _ ____ _ _
| |__ ___ ___ | |_|___ \ __| | ___ ___| | _____ _ __
| '_ \ / _ \ / _ \| __| __) / _` |/ _ \ / __| |/ / _ \ '__|
| |_) | (_) | (_) | |_ / __/ (_| | (_) | (__| < __/ |
|_.__/ \___/ \___/ \__|_____\__,_|\___/ \___|_|\_\___|_|
WARNING: this is a build from test.docker.com, not a stable release.
Could not chdir to home directory /home/tc: No such file or directory
Boot2Docker version 1.12.1-rc1, build HEAD : 0e17a04 - Mon Aug 15 18:14:57 UTC 2016
Docker version 1.12.1-rc1, build 7889dc7
-
Have you tried some bootcodes like secure or superuser
http://distro.ibiblio.org/tinycorelinux/faq.html#bootcodes
-
There is no default password.
Set it and add the following to /opt/.filetool.lst. Then do a backup
etc/passwd
etc/shadow
-
Thank you.
". Boot2docker uses Tiny Core Linux, which runs from RAM", so it looks like Microsoft is also adapting Tiny Core linux :)
## .
## ## ## ==
## ## ## ## ## ===
/"""""""""""""""""\___/ ===
~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ / ===- ~~~
\______ o __/
\ \ __/
\____\_______/
docker is configured to use the default machine with IP 192.168.99.100
For help getting started, check out the docs at https://docs.docker.com
Start interactive shell
geev0@AMP-GV MINGW64 ~
$ docker run -ti --rm icymatter/slitaz40-minimal /bin/bash
bash-4.2#