9:18 a.m.
-----Original Message-----
From: cc-devel [mailto:cc-devel-bounces@lists.01.org] On Behalf Of
louise.krug(a)bt.com
Sent: Wednesday, November 9, 2016 4:11 PM
To: Castelino, Manohar R <manohar.r.castelino(a)intel.com>; Hunt, James O
<james.o.hunt(a)intel.com>
Cc: cc-devel(a)lists.01.org
Subject: Re: [cc-devel] beginner help required
Well I prodded everything suggested with no success (yes standard docker
bridge, yes runc worked etc etc). Last resort was to rebuild the system from
scratch and its now working....No idea what I could have had on it that was
causing problems however
That is ... odd :-) I don't think we've seen that before. If you ever figure it
out, do let us know
Thanks for your prompt responses
And thanks for reaching out and also letting us
know it is up and running!
Graham
Louise
-----Original Message-----
From: Castelino, Manohar R [mailto:manohar.r.castelino@intel.com]
Sent: 04 November 2016 17:18
To: Krug,AL,Louise,TUB8 R <louise.krug(a)bt.com>; Hunt, James O
<james.o.hunt(a)intel.com>
Cc: cc-devel(a)lists.01.org
Subject: RE: [cc-devel] beginner help required
Hi Louise,
> > the permission bits on the lower branch Nov 2 12:14:16 nfv-mobile
> > systemd-udevd[19236]: Could not generate persistent MAC address for
> > vethd53b6fb: No such file or directory Nov 2 12:14:16 nfv-mobile
> > NetworkManager[827]: <warn> [1478088856.9211] device (vethd53b6fb):
> > failed to find device 27 'vethd53b6fb' with udev Nov 2 12:14:16
> > nfv-mobile NetworkManager[827]: <info> [1478088856.9251]
> > manager: (vethd53b6fb): new Veth device
> > (/org/freedesktop/NetworkManager/Devices/30)
> > Nov 2 12:14:16 nfv-mobile NetworkManager[827]: <warn>
> > [1478088856.9264] device (veth80531c9): failed to find device 28
> > 'veth80531c9' with udev Nov 2 12:14:16 nfv-mobile
The errors seen above do not seem typical
Are you using the standard docker bridge network when you launch the
container? Are you using an alternate network plugin?
Could you provide the output of "docker network inspect bridge" if you are
running with the standard docker bridge. Or the output of inspect in the case of
an alternate plugin.
Have you been able to launch a runc docker container on the same system, once
you installed the clear container runtime
sudo docker run -itd --runtime=runc alpine /bin/sh
Also could you look at your dmesg output to see if there are any relevant errors.
-manohar
_______________________________________________
cc-devel mailing list
cc-devel(a)lists.01.org
https://lists.01.org/mailman/listinfo/cc-devel
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.