Your message dated Fri, 09 May 2014 22:04:13 +0000
with message-id <[email protected]>
and subject line Bug#739914: fixed in docker.io 0.11.1~dfsg1-1
has caused the Debian Bug report #739914,
regarding docker.io: daemon silently fails to start on i386 userspace
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
739914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739914
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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

--- End Message ---
--- Begin Message ---
Source: docker.io
Source-Version: 0.11.1~dfsg1-1

We believe that the bug you reported is fixed in the latest version of
docker.io, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tianon Gravi <[email protected]> (supplier of updated docker.io package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Fri, 09 May 2014 17:30:45 -0400
Source: docker.io
Binary: docker.io vim-syntax-docker
Architecture: source amd64 all
Version: 0.11.1~dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Paul Tagliamonte <[email protected]>
Changed-By: Tianon Gravi <[email protected]>
Description: 
 docker.io  - Linux container runtime
 vim-syntax-docker - Docker container engine - Vim highlighting syntax files
Closes: 739914 746774 747139 747140
Changes: 
 docker.io (0.11.1~dfsg1-1) unstable; urgency=medium
 .
   [ Paul Tagliamonte ]
   * Use EnvironmentFile with the systemd unit file. (Closes: #746774)
   * Patch out version checking code. (Closes: #747140)
   * Remove all host checking for non-amd64 host arches. Let docker build
     and run on all platforms now. (Closes: #747139, #739914)
 .
   [ Tianon Gravi ]
   * Updated to 0.11.1 upstream release.
   * Added backported upstream patch for removing RemoteAddr assumptions
     that cause events to not be delivered to more than one unix socket
     listener.
Checksums-Sha1: 
 713d2c147088e3406c985f92c7bac3e860553039 2476 docker.io_0.11.1~dfsg1-1.dsc
 a9923dddd53874ae0d629556d83178d0ee70c31e 2051846 
docker.io_0.11.1~dfsg1.orig.tar.gz
 0460ba2dc3a8a7b0b9ab295b03ac5cdb67efb7ec 15496 
docker.io_0.11.1~dfsg1-1.debian.tar.xz
 4c1c8641fd7dfa014fe950391751a240d3a84363 3988344 
docker.io_0.11.1~dfsg1-1_amd64.deb
 55af0bf4767e7829ea150456fbf6ad5bd5a8964f 24684 
vim-syntax-docker_0.11.1~dfsg1-1_all.deb
Checksums-Sha256: 
 3888c6cf0a262f58c443ae883900b92b9e58ceae7363a49d0309810547240285 2476 
docker.io_0.11.1~dfsg1-1.dsc
 662299ea2ec453583cbac31c83d8e151b69ed3d527660d8ce83720236ea9221f 2051846 
docker.io_0.11.1~dfsg1.orig.tar.gz
 80d672d7012565003aba473a44e56996de324337d779acb5e91da6b8686de684 15496 
docker.io_0.11.1~dfsg1-1.debian.tar.xz
 7c6e30317a46098db94c1704c6bfad20d4b81c6f6de5f9de875af756604b9a98 3988344 
docker.io_0.11.1~dfsg1-1_amd64.deb
 b499b205661fc52715100df10db6fc3a072b57b5f89b494203186a865cc5049e 24684 
vim-syntax-docker_0.11.1~dfsg1-1_all.deb
Files: 
 dd1cdac507a2d2acc1f40ecd425ff66a 3988344 admin optional 
docker.io_0.11.1~dfsg1-1_amd64.deb
 9645f9379f4f94ed27f149132617d604 24684 admin optional 
vim-syntax-docker_0.11.1~dfsg1-1_all.deb
 4559e287751056351d5cba79bd981e97 2476 admin optional 
docker.io_0.11.1~dfsg1-1.dsc
 9cd801741babcc5c015d18e2974dd3f9 2051846 admin optional 
docker.io_0.11.1~dfsg1.orig.tar.gz
 eb0556b85474543ca28770503cadb904 15496 admin optional 
docker.io_0.11.1~dfsg1-1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTbUq7AAoJEHtYWzCAfCqHzbcP/0KpVa7u5dnDiCQAIOSjGMRW
9hFh67i8eVyY46382hiSSuVswK6dsTSL0clcfRkNAXLtviq7w5fZ2gsDpQ9Vlw4i
4eBXxe9gbQsjZVQowO3P2LOjXeu1wX7S6DMw4m9ZbsggjZy5wVNX0dv5yervCfh0
0r9EuXyy5rsFLZHBu89M64mkM2f789dP6F9Gp+FpvBm25hQLNk7UaC5VElDmDut8
SfyOWaDHjFCljZrp+NTo6rRNcJXB9MFt15wtwbbaIavWQ31A7Y64lSqLnLgJQvss
k5fxUGhg7ca14GbhIVKC37PT9FQTp6BQ2CI0iYhCg6F5MBj6+IzHgQm9k+Se9Nd6
MbvAGrSO2P4792AtjjSYxwz29o8HaBTasBvkJuFjNkzLyPz61P4De1aqBWP27GXe
KWNPhuqBIxuLUU7y1fBgdZIe23KkeMA8vUWgTse/5w+Eyrx1SNB307soG32hLX+z
FgPlAjgca9HPTRA/iMLJNx1CVH26LqUIabXtzJp2Hbflfmjm+5VR7B8LyPmQRctG
DcKG3lvjNbgGS/qz4Ko+f9X4SYEdY9HStIurtpIarTQHusZolv10Pe2IWG1itOuU
7lTTA8YqINL96L9hFyhE8ZGRdIWBljvcePlY26pHciYDBJnISzB1/FKYd96vLxwA
cjaiMiuVHeymgzbsHshm
=EIno
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to