12:27 a.m.
Hi Louise,
Excellent news! It's actually not totally trivial to propagate an error
message from the OCI runtime underneath containerd up the user using
docker. I logged an issue to see if we can do this so we can provide
direct feedback of what went wrong:
https://github.com/01org/cc-oci-runtime/issues/364
I find that a usual source of failure is the path to qemu-lite which has
to been known at build time. If the configure script doesn't find
qemu-lite in the path, we default to /usr/bin/qemu-system-x86_64 and the
runtime will fail to start if this binary isn't there or doesn't support
the pc-lite machine type.
HTH,
--
Damien
On Wed, Nov 09, 2016 at 04:11:04PM +0000, louise.krug(a)bt.com wrote:
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
Thanks for your prompt responses
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