kave/kavetoolbox repository overview

See http://github.com/KaveIO/KaveToolbox⁠ For head releases/automated builds see http://hub.docker.com/r/kave/kavetoolbox-head⁠

⁠Quickstart

Choose an appropriate tag (e.g. 3.0-Beta.c7.workstation), then start a container with the correct port forwarding you want (e.g. for an ipython notebook).

docker run -it --name kavetoolbox -p 8899:8888 kave/kavetoolbox:3.0-Beta.c7.workstation /bin/bash

⁠IPython notebooks

To run an ipython notebook server, first start the docker, then add a user

docker start  kavetoolbox
docker exec kavetoolbox useradd kaveuser
docker exec kavetoolbox mkdir /home/kaveuser
docker exec kavetoolbox chown kaveuser:kaveuser /home/kaveuser

Now start the ipython notebook under that user

docker exec -it kavetoolbox su kaveuser /bin/bash -l -c 'cd ; pwd; env; nohup ipython notebook --ip=0.0.0.0 &'

Then if you can connect to http://localhost:8899⁠ (in this example)

To make the root user also have the kave environment (not recommended since it replaces system python) do:

docker exec kavetoolbox touch /root/.kaveEnv

⁠Centos7 services / vnc desktop

Dockers do not run the init scripts for centos. To enable things like service sshd start, you would need to run the docker with special privilages

docker run --security-opt seccomp=unconfined --cap-add=SYS_ADMIN --privileged  -ti -e "container=docker"  -v /sys/fs/cgroup:/sys/fs/cgroup:ro --name kavetoolboxwrk -p 5966:5966 kave/kavetoolbox:3.0-Beta.c7.workstation /usr/sbin/init

will start a docker in a privileged mode and run the init scripts. This run command will never return control to the user, and so to communicate with or kill the docker that would need to be done in a separate terminal. Then service xxx start commands should work normally, and so should getting a vnc connection working

docker exec kavetoolboxwrk service firewalld stop
docker exec kavetoolboxwrk -it /bin/bash
$ vncserver :66

Then on the host machine:

vncviewer localhost:66

⁠Tag Format

Image tags use the following format:

kaveversion.osversion.flavor

e.g.:

3.0-Beta.c7.node, is the KaveToolbox version 3.0-Beta, built on a centos7 image in --node flavor.

⁠OS versions

We support:

• u14 = ubuntu14,
• u16 = ubuntu16
• c7 = centos7 for these docker containers:

⁠Flavors

KaveToolbox has two main installation flavors:

• Node: only libraries and applications needed for remote or non-interactive use, no gui components
• Workstation: all required libraries for a complete workstation including VNC, IDE, Gui, browser, etc.

⁠Dockerfiles:

https://github.com/KaveIO/KaveToolbox/tree/master/docker⁠

see:

• c7.node: https://github.com/KaveIO/KaveToolbox/tree/master/docker/c7.node⁠
• c7.workstation: https://github.com/KaveIO/KaveToolbox/tree/master/docker/c7.workstation⁠
• u14.node: https://github.com/KaveIO/KaveToolbox/tree/master/docker/u14.node⁠
• u14.workstation: https://github.com/KaveIO/KaveToolbox/tree/master/docker/u14.workstation⁠
• u16.node: https://github.com/KaveIO/KaveToolbox/tree/master/docker/u16.node⁠
• u16.workstation: https://github.com/KaveIO/KaveToolbox/tree/master/docker/u16.workstation⁠