El 12/04/22 a las 07:49, Bo YU escribió: > Hi, > On Mon, Apr 11, 2022 at 10:40:53PM +0200, Paul Gevers wrote: > > Hi Santiago, > > > > On 11-04-2022 10:46, Santiago Ruano Rincón wrote: > > > (And sorry if I jumping in into the conversation and introducing just > > > noise) > > > > No, your contribution is much appreciated. :-) > > > > > Could you run rather `lxc-ls -f` (to include IP addresses information) > > > > root@unmatched:~# lxc-ls -f > > NAME STATE AUTOSTART GROUPS IPV4 IPV6 > > UNPRIVILEGED > > autopkgtest-unstable-riscv64 STOPPED 0 - - - false The container wasn't running. > > > > > Some questions/commands that could help debugging the issue: > > > > > > * Have you modified the contents of /etc/default/lxc-net? > > > > I didn't (not sure if Bo did). > No, I did not modify the /etc/default/lxc-net: > ```bash > root@unmatched:~# cat /etc/default/lxc-net > USE_LXC_BRIDGE="true" ... > > > > > * Could you share the configuration of your lxc container? I suppose you > > > can find it in /var/lib/lxc/autopkgtest-unstable-riscv64/config > > > Regarding networking, this could be enough: > > > `grep net /var/lib/lxc/autopkgtest-unstable-riscv64/config` > > > > root@unmatched:~# grep net /var/lib/lxc/autopkgtest-unstable-riscv64/config > > lxc.net.0.type = veth > > lxc.net.0.link = lxcbr0 > > lxc.net.0.flags = up > > lxc.net.0.hwaddr = 00:16:3e:00:00:00 > > * Just to be sure, could you verify the lxc bridge in the host machine is called lxcbr0? In the container: * What are the contents of /etc/network/interfaces * is ifupdown installed? HTH, -- S
Attachment:
signature.asc
Description: PGP signature