From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: bug#34333: Docker daemon failing to start on boot Date: Tue, 12 Feb 2019 18:45:17 +0100 Message-ID: <20190212184517.77edfb58@scratchpost.org> References: <26bbaae65fb9ab18036684e9f676ac1e@adair.io> <87pns2vtaz.fsf@gnu.org> <20190211114651.2b32e555@scratchpost.org> <20190211183155.30861768@scratchpost.org> <8a67633984fd5547e69b09fff29223ba@adair.io> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_//DbUxcoCdMNkA+27=KVke59"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:53441) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gtc8I-0002HG-Ld for bug-guix@gnu.org; Tue, 12 Feb 2019 12:46:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gtc8G-0001ri-J7 for bug-guix@gnu.org; Tue, 12 Feb 2019 12:46:10 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:45846) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gtc89-0001kk-Op for bug-guix@gnu.org; Tue, 12 Feb 2019 12:46:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gtc89-0000Sd-KJ for bug-guix@gnu.org; Tue, 12 Feb 2019 12:46:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <8a67633984fd5547e69b09fff29223ba@adair.io> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Allan Adair Cc: 34333@debbugs.gnu.org --Sig_//DbUxcoCdMNkA+27=KVke59 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Allan, On Tue, 12 Feb 2019 09:05:10 +0000 Allan Adair wrote: > On 2019-02-11 17:31, Danny Milosavljevic wrote: > > Hi Allan, > >=20 > > I've added some more requirements--let's see. > >=20 > > Can you guix pull and guix reconfigure and then try again once more? =20 >=20 > Still no luck. Do you face the same issue? I don't know since my machine has not finished updating after the recent staging to master merge. --Sig_//DbUxcoCdMNkA+27=KVke59 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAlxjBi0ACgkQ5xo1VCww uqW76Af/Rl/OL3c1yJfNbVQZ6kyHDVkUjreiep5B83ulK/ce0Gm07OMz3tzgabyi Let8YcLNpj8By5uRnk7MjCHvxMvVFhqio2yVTKQvlqpboyxOzz3aSioinNaCg/mw K+MsX62itLRcy1Plj3sPxgwyQPlHEduTbKwTiTzeNQgMUeCIZm91M63ufGMV1nMu ab/OjpCzoAK80gQT1SUDwtPdgh4lrOCWMhH+BQOXfUFu/tsELoigEjl15HBxcXod VRHM0sbwInIz/YKRRYpFsJ4arf6CPlsWqAb+7gh8SW+qyYpH2N89HYQY+5aUfDX2 i5UetYKafjT/DE6D3uhZ4QhPV0qscA== =o7At -----END PGP SIGNATURE----- --Sig_//DbUxcoCdMNkA+27=KVke59--