El 12/04/22 a las 22:40, Paul Gevers escribió: > Hi, > > On 12-04-2022 22:20, Santiago Ruano Rincón wrote: > > > > > > 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 > > > > This is the same mac address than the unmatched's lxcbr0. Try changing > > it. > > root@unmatched:~# grep hwaddr > /var/lib/lxc/autopkgtest-unstable-riscv64/config > lxc.net.0.hwaddr = 00:16:3e:00:00:01 > > root@unmatched:~# lxc-start -n autopkgtest-unstable-riscv64 > root@unmatched:~# lxc-ls -f > NAME STATE AUTOSTART GROUPS IPV4 IPV6 > UNPRIVILEGED > autopkgtest-unstable-riscv64 RUNNING 0 - 10.0.3.17 - false > root@unmatched:~# lxc-attach -n autopkgtest-unstable-riscv64 > root@autopkgtest-unstable-riscv64:~# apt update > Ign:1 https://deb.debian.org/debian-ports unstable InRelease > Ign:1 https://deb.debian.org/debian-ports unstable InRelease > Ign:1 https://deb.debian.org/debian-ports unstable InRelease > > It seems it's getting better, but it still doesn't want to find the > archive.... Good. But it would be nice to know why it got that not-so-random MAC address. Regular lxc containers populate their initial config from /etc/lxc/default.conf. No idea if autopkgtest-build-lxc does something extra. * verify packets can be routed (NATed) and it's a DNS resolution problem with a ping 128.31.0.62 (or any other public IP) * verify NAT rules with nft list ruleset. There should be a couple of lxc-related tables. If nft is not available, I think it should be on iptables -L -t nat. Cheers, -- S
Attachment:
signature.asc
Description: PGP signature