LXD 3.21 on RHEL 7 w/ Firewall Enabled . No IP Address

1

This is first time I am executing LXD with Firewall enabled on host machine. Unfortunately, I am not able to get IP Assigned to container.

LXD (3.21) was installed via SNAP.

I was able to successfully complete

lxd init

lxdbr0 seems to be up. Validated DNSMASQ running.

config:
ipv4.address: 10.193.144.1/24
ipv4.nat: “true”
ipv6.address: none
description: “”
name: lxdbr0
type: bridge
used_by:

  • /1.0/instances/chrome
    managed: true
    status: Created
    locations:
  • none

default profile

config: {}
description: Default LXD profile
devices:
  eth0:
    name: eth0
    nictype: bridged
    parent: lxdbr0
    type: nic
  root:
    path: /
    pool: default
    type: disk
name: default
used_by:
- /1.0/instances/chrome

Lxc Container Info:

Name: chrome
Location: none
Remote: unix://
Architecture: x86_64
Created: 2020/02/19 18:25 UTC
Status: Running
Type: container
Profiles: default
Pid: 1333
Ips:
  eth0:	inet6	fe80::216:3eff:feb2:cc0b	vethe0dc5607
  lo:	inet	127.0.0.1
  lo:	inet6	::1
Resources:
  Processes: 1
  Disk usage:
    root: 747.36MB
  CPU usage:
    CPU usage (in seconds): 0
  Memory usage:
    Memory (current): 38.77MB
  Network usage:
    eth0:
      Bytes received: 9.25kB
      Bytes sent: 656B
      Packets received: 54
      Packets sent: 8
    lo:
      Bytes received: 0B
      Bytes sent: 0B
      Packets received: 0
      Packets sent: 0

lxc list

image

Any thoughts what setting I am missing and if I need to update firewall?

I added following ports to firewall.

  • 10443(TCP),
  • 53(TCP)
  • 53(UDP)
  • 67(UDP)
2

you are missing an important information, what kind of container is this ‘chrome’ ?
For you information, images are pulled on a regular basis from current distro versions and last time I looked the automated tests were not checking that the container get an IP, so your particular image may be actually broken.

3

Standard Ubuntu 18.04 (Bionic) image is used for this container. This image works on other machines (downloaded during creation process).

4

ubuntu 18.04 ? how is it managing to only eat 39 Mb of memory ? If i do the same it’s taking 200 Mb…

Anyway, In this case I have this snippet in my files that has helped me in the past for a similar problem

SYSTEMD_LOG_LEVEL=debug strace /usr/lib/systemd/systemd-networkd &>mylog

after stopping the systemd-networkd service (it may be necessary to actually disable it, systemd is so sticky) and running it, maybe some useful info could be obtained from the trace.

5

Will try it out. Thanks