Re: "Invalid Release file" when setup autopkgtest env with autopkgtest-build-lxc
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
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"
# Honor system's dnsmasq configuration
#LXC_DHCP_CONFILE=/etc/dnsmasq.conf
```
* 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
* check the status of lxc services, including lxc-net:
`sudo systemctl status "lxc*"`
root@unmatched:~# sudo systemctl status "lxc*"
sudo: unable to resolve host unmatched: No address associated with hostname
Here, the complaint will display if without sudo.
Thanks all:-)
BR,
Bo
● lxc-net.service - LXC network bridge setup
Loaded: loaded (/lib/systemd/system/lxc-net.service; enabled;
vendor preset: enabled)
Active: active (exited) since Thu 2022-03-17 12:26:50 UTC; 11h ago
Docs: man:lxc
Process: 297 ExecStart=/usr/libexec/lxc/lxc-net start
(code=exited, status=0/SUCCESS)
Main PID: 297 (code=exited, status=0/SUCCESS)
Tasks: 1 (limit: 19113)
Memory: 4.1M
CPU: 167ms
CGroup: /system.slice/lxc-net.service
└─381 dnsmasq --conf-file=/dev/null -u dnsmasq
--strict-order --bind-interfaces>
mrt 17 12:26:50 unmatched dnsmasq[381]: reading /etc/resolv.conf
mrt 17 12:26:50 unmatched dnsmasq[381]: using nameserver 192.168.31.1#53
mrt 17 12:26:50 unmatched dnsmasq[381]: read /etc/hosts - 4 addresses
mrt 17 12:26:50 unmatched systemd[1]: Finished LXC network bridge setup.
mrt 17 12:26:55 unmatched dnsmasq[381]: reading /etc/resolv.conf
mrt 17 12:26:55 unmatched dnsmasq[381]: using nameserver 192.168.31.1#53
mrt 17 17:47:29 unmatched dnsmasq[381]: reading /etc/resolv.conf
mrt 17 17:47:29 unmatched dnsmasq[381]: using nameserver 192.168.31.1#53
mrt 17 23:17:11 unmatched dnsmasq[381]: reading /etc/resolv.conf
mrt 17 23:17:11 unmatched dnsmasq[381]: using nameserver 192.168.31.1#53
● lxc.service - LXC Container Initialization and Autoboot Code
Loaded: loaded (/lib/systemd/system/lxc.service; enabled; vendor
preset: enabled)
Active: active (exited) since Thu 2022-03-17 12:26:56 UTC; 11h ago
Docs: man:lxc-autostart
man:lxc
Process: 402 ExecStartPre=/usr/libexec/lxc/lxc-apparmor-load
(code=exited, status=0/SUCC>
Process: 430 ExecStart=/usr/libexec/lxc/lxc-containers start
(code=exited, status=0/SUCC>
Main PID: 430 (code=exited, status=0/SUCCESS)
CPU: 253ms
mrt 17 12:26:56 unmatched systemd[1]: Starting LXC Container
Initialization and Autoboot Cod>
mrt 17 12:26:56 unmatched systemd[1]: Finished LXC Container
Initialization and Autoboot Cod>
Paul
Reply to: