I have finally resolved this issue.
The NIC was being configured by systemd-networkd, which was obtaining an
IP address using its version of dhclient. Removing dhclient did not
prevent this from happening. NetworkManager was configuring the static
IP.
Stopping NetworkManager and configurin
When I factor out the bonded network configuration, your LXD profiles
and containers look just like mine. There is an existing non-LXD
bridge, a profile which describes it as "bridged", and containers which
use that profile.
On my system, the NIC gets two IP addresses: one configured by the
On 2/11/20 4:57 PM, Joshua Schaeffer wrote:
Not sure this will help but I provided my configuration for LXD below. I
use Ubuntu so you'd have to translate the configuration network
configuration portions over to RedHat/CentOS. My containers' configure
their own interfaces (static, dhcp, or what
Not sure this will help but I provided my configuration for LXD below. I use
Ubuntu so you'd have to translate the configuration network configuration
portions over to RedHat/CentOS. My containers' configure their own interfaces
(static, dhcp, or whatever), LXD simply defines the interface. Thes
On 2/11/20 11:00 AM, Mike Wright wrote:
On 2/11/20 10:01 AM, Michael Eager wrote:
There's still a lot of confusion. :-/
Yes, here too. I'm experimenting with the nic types but a lot of the
problems I'm running into have to do with me misunderstanding the LXD
command syntax. The docs are r
On 2/11/20 10:01 AM, Michael Eager wrote:
On 2/8/20 1:32 PM, Mike Wright wrote:
On 2/6/20 8:29 AM, Michael Eager wrote:
Thanks. I had tried this, but it didn't appear to work. I just tried
it again and got it to work.
I assume that I can move the eth0 definition back to the profile,
without
On 2/8/20 1:32 PM, Mike Wright wrote:
On 2/6/20 8:29 AM, Michael Eager wrote:
Thanks. I had tried this, but it didn't appear to work. I just tried
it again and got it to work.
I assume that I can move the eth0 definition back to the profile,
without the ipv4.address specification.
https://lx
On 2/6/20 8:29 AM, Michael Eager wrote:
Thanks. I had tried this, but it didn't appear to work. I just tried
it again and got it to work.
I assume that I can move the eth0 definition back to the profile,
without the ipv4.address specification.
https://lxd.readthedocs.io/en/latest/instances/#t
On 2/8/20 6:13 AM, Andrey Repin wrote:
Greetings, Michael Eager!
Thanks. I had tried this, but it didn't appear to work. I just tried
it again and got it to work.
I assume that I can move the eth0 definition back to the profile,
without the ipv4.address specification.
I don't know about
Greetings, Michael Eager!
> Thanks. I had tried this, but it didn't appear to work. I just tried
> it again and got it to work.
> I assume that I can move the eth0 definition back to the profile,
> without the ipv4.address specification.
I don't know about LXD specifics, but for bare LXC, ther
Thanks. I had tried this, but it didn't appear to work. I just tried
it again and got it to work.
I assume that I can move the eth0 definition back to the profile,
without the ipv4.address specification.
On 2/5/20 2:21 PM, Oliver Rath wrote:
Hi Michael,
you can use the standard fedora way cr
Hi Michael,
you can use the standard fedora way creating a static IP inside the vm.
Hth
Oliver
Am 05.02.20 um 23:15 schrieb Michael Eager:
> I'm running LXD on a Centos 8 host. The container is Fedora 31.
> I'm using a bridge (br0), not managed by LXD.
>
> When I start the container, it recei
I'm running LXD on a Centos 8 host. The container is Fedora 31.
I'm using a bridge (br0), not managed by LXD.
When I start the container, it receives an IP address from the DHCP
server on the LAN. I want to assign the container a static IP.
I removed the eth0 device from the profile and added
13 matches
Mail list logo
