Package: docker.io
Version: 0.8.0+dfsg1-2
Severity: important

Dear Maintainer,

I have a 64bit machine running a 64bit kernel and 32bit userspace.

After installing the package I tried to run the first command in the tutorial
and the error message was less than helpful:
        $ docker.io run debian echo hello world
        2014/02/23 17:59:07 dial unix /var/run/docker.sock: no such file or
directory

After a few searches about what that probably meant I ran accross someone
suggesting I set the DOCKER_HOST environment variable to tcp://. It still did
not work but the message was more helpful and exactly what I suspected was
happening:

        $ DOCKER_HOST=tcp:// docker.io run debuan echo hello world
        2014/02/23 18:02:46 Can't connect to docker daemon. Is 'docker -d'
running on this host?

Which was confusing because the daemon reported to have started successfully
after installation:

        [...]
        Setting up libapparmor1:i386 (2.8.0-5+b1) ...
        Setting up lxc (0.9.0~alpha3-2+deb8u1) ...
        Setting up docker.io (0.8.0+dfsg1-2) ...
        Adding group `docker' (GID 121) ...
        Done.
        [ ok ] Starting Docker: docker.io.
        Processing triggers for libc-bin (2.17-97) ...
        Press Return to continue.

I tried to start the daemon myself:

        # /etc/init.d/docker.io status
        [FAIL] docker is not running ... failed!

Unfortunately, there were no logs whatsoever about what could have gone wrong:

        # grep -ri docker /var/log/*
        /var/log/apt/history.log:Install: lxc:i386 (0.9.0~alpha3-2+deb8u1,
automatic), libapparmor1:i386 (2.8.0-5+b1, automatic), docker.io:i386
(0.8.0+dfsg1-2)
        /var/log/apt/term.log:Selecting previously unselected package
docker.io.
        /var/log/apt/term.log:Preparing to unpack
..../docker.io_0.8.0+dfsg1-2_i386.deb ...
        /var/log/apt/term.log:Unpacking docker.io (0.8.0+dfsg1-2) ...
        /var/log/apt/term.log:Setting up docker.io (0.8.0+dfsg1-2) ...
        /var/log/apt/term.log:Adding group `docker' (GID 121) ...
        [ ok log/apt/term.log:[....] Starting Docker: docker.io.
        /var/log/aptitude:[INSTALL] docker.io:i386
        /var/log/auth.log:Feb 23 17:58:07 waterworld groupadd[17978]: group
added to /etc/group: name=docker, GID=121
        /var/log/auth.log:Feb 23 17:58:07 waterworld groupadd[17978]: group
added to /etc/gshadow: name=docker
        /var/log/auth.log:Feb 23 17:58:07 waterworld groupadd[17978]: new
group: name=docker, GID=121
        /var/log/dpkg.log:2014-02-23 17:58:04 install docker.io:i386 <none>
0.8.0+dfsg1-2
        /var/log/dpkg.log:2014-02-23 17:58:04 status half-installed
docker.io:i386 0.8.0+dfsg1-2
        /var/log/dpkg.log:2014-02-23 17:58:04 status unpacked docker.io:i386
0.8.0+dfsg1-2
        /var/log/dpkg.log:2014-02-23 17:58:05 status unpacked docker.io:i386
0.8.0+dfsg1-2
        /var/log/dpkg.log:2014-02-23 17:58:06 configure docker.io:i386
0.8.0+dfsg1-2 <none>
        /var/log/dpkg.log:2014-02-23 17:58:06 status unpacked docker.io:i386
0.8.0+dfsg1-2
        /var/log/dpkg.log:2014-02-23 17:58:07 status unpacked docker.io:i386
0.8.0+dfsg1-2
        /var/log/dpkg.log:2014-02-23 17:58:07 status unpacked docker.io:i386
0.8.0+dfsg1-2
        /var/log/dpkg.log:2014-02-23 17:58:07 status unpacked docker.io:i386
0.8.0+dfsg1-2
        /var/log/dpkg.log:2014-02-23 17:58:07 status half-configured
docker.io:i386 0.8.0+dfsg1-2
        /var/log/dpkg.log:2014-02-23 17:58:07 status installed docker.io:i386
0.8.0+dfsg1-2

After reading through /etc/init.d/docker.io I ran the following and got a
useful message out:

# start-stop-daemon --start --exec /usr/bin/docker.io --pidfile
/var/run/docker.io.pid -- -d -p /var/run/docker.io.pid
2014/02/23 18:07:11 The docker runtime currently only supports amd64 (not 386).
This will change in the future. Aborting.

I do understand that non-amd64 hosts are not supported (as mentioned in the
description of the package). Then again I think it would be best to have the
failure be more prominent about what is not working instead of silently
failing.

Another alternative (that I prefer, but I trust your decision and time) would
be to change docker.io's code to actually start the daemon in a "unsupported"
platforms. It appears to be a 2-line change in server.go [1]

[1] http://mwhiteley.com/linux-containers/2013/08/31/docker-on-i386.html

Best regards,
Toote



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: i386 (x86_64)

Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages docker.io depends on:
ii  adduser              3.113+nmu3
ii  init-system-helpers  1.14
ii  iptables             1.4.21-1
ii  lxc                  0.9.0~alpha3-2+deb8u1
ii  perl                 5.18.2-2

Versions of packages docker.io recommends:
pn  aufs-tools       <none>
ii  ca-certificates  20130906
ii  xz-utils         5.1.1alpha+20120614-2

docker.io suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to