Thanks a lot for your explanations and workaround examples.
I expanded our ansible update playbooks to check if
/etc/netplan/10-lxc.yaml is installed, then to remove that file, runs
"netplan apply" and then remove the package "netplan.io". It seems to
work in our environment, without loosing the
Thank you so much for your very detailed answer! I understand my mistake
and fixed our set-up.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1863873
Title:
Systemd fails
> lxc.net.0.ipv4.gateway = 192.168.252.1
> lxc.net.0.ipv4.address = 192.168.252.171/32
> 3. inside the container, deactivate dhcp (dhcp4: false )in
`/etc/netplan/10-lxc.yaml`,
ok, this is your problem; you're misconfiguring the instance.
Unfortunately, you were just 'lucky' that it worked
I have the same problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1863873
Title:
Systemd fails to configure bridged network in LXC container
Status in systemd
** Description changed:
- In all our LXC containers running Bionic Beaver, installing systemd
- 237-3ubuntu10.39 results in losing network configuration.
+ In all our LXC containers running Bionic Beaver, Eoan Ermine or Focal
+ Fossa, installing the latest systemd package results in losing
Possible workaround:
switch back to ifupdown and don't use netplan
sudo apt-get update
sudo apt-get install ifupdown
cat << EOF > /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet manual
EOF
systemctl stop systemd-networkd.socket systemd-networkd \
I can confirm this behavior after update to systemd 237-3ubuntu10.39 on
privileged and unprivileged containers. We classify this bug as critical
because in the next monthly update cycle via ansible orchestration we
would expect failing all Bionic LXC containers. The only workaround
seems to
** Description changed:
In all our LXC containers running Bionic Beaver, installing systemd
237-3ubuntu10.39 results in losing network configuration.
It is still possible to configure the network "by hand" with
/usr/sbin/ip, but of course, the configuration is lost at reboot.
An
** Description changed:
In all our LXC containers running Bionic Beaver, installing systemd
237-3ubuntu10.39 results in losing network configuration.
It is still possible to configure the network "by hand" with
/usr/sbin/ip, but of course, the configuration is lost at reboot.
An
** Description changed:
In all our LXC containers running Bionic Beaver, installing systemd
237-3ubuntu10.39 results in losing network configuration.
It is still possible to configure the network "by hand" with
/usr/sbin/ip, but of course, the configuration is lost at reboot.
-
** Description changed:
- In all our unprivileged LXC containers running Bionic Beaver, installing
- systemd 237-3ubuntu10.39 results in losing network configuration.
+ In all our LXC containers running Bionic Beaver, installing systemd
+ 237-3ubuntu10.39 results in losing network configuration.
** Description changed:
In all our unprivileged LXC containers running Bionic Beaver, installing
systemd 237-3ubuntu10.39 results in losing network configuration.
It is still possible to configure the network "by hand" with
/usr/sbin/ip, but of course, the configuration is lost at
** Description changed:
In all our unprivileged LXC containers running Bionic Beaver, installing
systemd 237-3ubuntu10.39 results in losing network configuration.
It is still possible to configure the network "by hand" with
/usr/sbin/ip, but of course, the configuration is lost at
same behavior here!
systemd 237-3ubuntu10.38 -> IPV4 Adress after start of lxc-Container,
everything OK
systemd 237-3ubuntu10.39 -> NO IPV4 Adress in Container after lxc-start
Host: Ubuntu 16.04 lxc 2.0.8-0ubuntu1~16.04.2
Container: Ubuntu 18.04
--
You received this bug notification because
** Description changed:
In all our unprivileged LXC containers running Bionic Beaver, installing
systemd 237-3ubuntu10.39 results in losing network configuration.
It is still possible to configure the network "by hand" with
/usr/sbin/ip, but of course, the configuration is lost at
Here is a full procedure to reproduce the issue.
Set-up
==
1. Install an amd64 Debian Buster (default network install),
2. install lxc and create a bionic amd64 container,
```bash
apt install lxc
lxc-create -t download -n bionic
lxc-start -n bionic
```
3. inside the container, deactivate
Just in case, I also removed any arptables or iptables on the host. The problem
is still present.
Here is an even simpler LXC configuration file to reproduce (privileged LXC
container on Debian Buster, 5.4.13 kernel):
# Distribution configuration
lxc.include = /usr/share/lxc/config/common.conf
The problem is also present in eoan and focal, but not disco
(unprivileged LXC containers, 5.4.13 kernel).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1863873
Title:
The problem is also present in privileged LXC containers. Example with
full LXC configuration below, on a host with a custom 5.4.13 kernel.
# Distribution configuration
lxc.include = /usr/share/lxc/config/common.conf
# For Ubuntu 14.04
lxc.mount.entry = /sys/kernel/debug sys/kernel/debug none
Did you do your test in an unprivileged LXC container?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1863873
Title:
Systemd fails to configure bridged network in LXC
I can't reproduce your error:
ubuntu@lp1863873-b:~$ dpkg -l systemd|grep ii
ii systemd237-3ubuntu10.38 amd64system and service manager
ubuntu@lp1863873-b:~$ ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd
** Description changed:
In all our unprivileged LXC containers running Bionic Beaver, installing
systemd 237-3ubuntu10.39 results in losing network configuration.
+
+ It is still possible to configure the network "by hand" with
+ /usr/sbin/ip, but of course, the configuration is lost at
** Description changed:
In all our unprivileged LXC containers running Bionic Beaver, installing
systemd 237-3ubuntu10.39 results in losing network configuration.
- Host:
+ Hosts:
debian buster
- custom 5.3.9 or 5.4.8 kernel
+ custom 5.3.9 or 5.4.8 kernel
Example container
** Description changed:
In all our unprivileged LXC containers running Bionic Beaver, installing
systemd 237-3ubuntu10.39 results in losing network configuration.
Host:
debian buster
- custom 5.3.9 kernel
+ custom 5.3.9 or 5.4.8 kernel
Example container network configuration:
24 matches
Mail list logo
