docker @ v-server strato.de–next steps

So after thinking about it I have work around most things so I end up with:

#> apt-get install golang
#> apt-get install lxc curl xz-utils git mercurial
#> apt-get install uml-utilities
#> tunctl
#> ifconfig tap1 10.4.0.0 netmask 255.255.255.0 up
#> ./docker -d -D -G local -b tap1

and the result is quite promising:

2014/07/01 09:13:02 WARNING: You are running linux kernel version 2.6.32-042stab090.3, which might be unstable running docker. Please upgrade your kernel to 3.8.0.
2014/07/01 09:13:02 docker daemon: 1.0.1 990021a; execdriver: native; graphdriver:
[debug] daemon.go:784 Using graph driver vfs
[debug] daemon.go:797 Creating images graph
[debug] graph.go:66 Restored 5 elements
[debug] daemon.go:809 Creating volumes graph
[debug] graph.go:66 Restored 0 elements
[debug] daemon.go:814 Creating repository list
[477fbb4f] +job init_networkdriver()
[debug] /sbin/iptables, [-C POSTROUTING -t nat -s 10.4.0.0/24 ! -d 10.4.0.0/24 -j MASQUERADE]
[debug] /sbin/iptables, [-D FORWARD -i tap1 -o tap1 -j DROP]
[debug] /sbin/iptables, [-C FORWARD -i tap1 -o tap1 -j ACCEPT]
[debug] /sbin/iptables, [-C FORWARD -i tap1 ! -o tap1 -j ACCEPT]
[debug] /sbin/iptables, [-C FORWARD -o tap1 -m conntrack –ctstate RELATED,ESTABLISHED -j ACCEPT]
[debug] /sbin/iptables, [-t nat -D PREROUTING -m addrtype –dst-type LOCAL -j DOCKER]
[debug] /sbin/iptables, [-t nat -D OUTPUT -m addrtype –dst-type LOCAL ! –dst 127.0.0.0/8 -j DOCKER]
[debug] /sbin/iptables, [-t nat -D OUTPUT -m addrtype –dst-type LOCAL -j DOCKER]
[debug] /sbin/iptables, [-t nat -D PREROUTING -j DOCKER]
[debug] /sbin/iptables, [-t nat -D OUTPUT -j DOCKER]
[debug] /sbin/iptables, [-t nat -F DOCKER]
[debug] /sbin/iptables, [-t nat -X DOCKER]
[debug] /sbin/iptables, [-t nat -N DOCKER]
[debug] /sbin/iptables, [-t nat -A PREROUTING -m addrtype –dst-type LOCAL -j DOCKER]
[debug] /sbin/iptables, [-t nat -A OUTPUT -m addrtype –dst-type LOCAL ! –dst 127.0.0.0/8 -j DOCKER]
[477fbb4f] -job init_networkdriver() = OK (0)
2014/07/01 09:13:02 WARNING: mountpoint not found
[debug] daemon.go:344 Loaded container fa5709a2bed13b6f99010dc239cbbb9dbf609fd68f94cbb3cf51b5367c658c7d
[477fbb4f.initserver()] Creating pidfile
[477fbb4f.initserver()] Setting up signal traps
[477fbb4f] -job initserver() = OK (0)
[477fbb4f] +job acceptconnections()
[477fbb4f] -job acceptconnections() = OK (0)

ok so the server is running, but as we see already with a quite valid kernel version warning.

On the client side I see:

user@host#> ./docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
user@host#> ./docker run -t -i busybox /bin/bash
Unable to find image ‘busybox’ locally
Pulling repository busybox
a9eb17255234: Download complete
511136ea3c5a: Download complete
42eed7f1bf2a: Download complete
120e218dd395: Download complete
2014/07/01 09:16:08 Error response from daemon: Cannot start container e67e871b6f9cba47210ed16be2b9e8ec377a1e478b8a24110397a5938e9c4459: fork/exec /var/lib/docker/init/dockerinit-1.0.1: operation not permitted
user@host#> ./docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
busybox             latest              a9eb17255234        3 weeks ago         2.433 MB
user@host#> ./docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS                      PORTS               NAMES
e67e871b6f9c        busybox:latest      /bin/bash           8 seconds ago       Exited (-1) 7 seconds ago                       hungry_mcclintock  
user@host#>

Basically I am already quite happy, it looks quite well except the point that the container can not start. So still not there.

Advertisements
This entry was posted in Docker and tagged , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s