Le 13/04/2016 19:22, Anders Andersson a écrit : >> Can you show the process listing in the broken containers? > Sure, there is not much to show: > > root@deb8:~# ps auxf > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > root 10 0.0 0.0 21868 3812 ? S 16:22 0:00 /bin/bash > root 11 0.0 0.0 19068 2464 ? R+ 16:22 0:00 \_ ps auxf > root 1 0.0 0.0 27080 2052 ? S 16:14 0:00 /sbin/init > > deb9 looks the same.
It seems that systemd is not started. Because the interface is raised through it, I think that this is the source of your network problem. In my Debian containers, I purge systemd and I replace it by sysvinit. You should do the same in order to get a working container. With your interface up, run these commands in the container to replace systemd by sysvinit: # apt-get update # apt-get install sysvinit sysvinit-core sysvinit-utils --purge -y # apt-get autoremove --purge systemd -y Xavier _______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
