The new instance cannot get an ipv4 address (docker)

wencan · January 19, 2023, 9:03pm

I am a new user of lxc.
I have created two instance.

+----------+---------+------+-------------------------------------------------+-----------------+-----------+------------+
|   NAME   |  STATE  | IPV4 |                      IPV6                       |      TYPE       | SNAPSHOTS |  LOCATION  |
+----------+---------+------+-------------------------------------------------+-----------------+-----------+------------+
| ubuntu01 | RUNNING |      | fd42:3a3f:3d85:d02d:216:3eff:fe5c:1b70 (eth0)   | CONTAINER       | 0         | fedora2022 |
+----------+---------+------+-------------------------------------------------+-----------------+-----------+------------+
| ubuntu02 | RUNNING |      | fd42:3a3f:3d85:d02d:216:3eff:fe85:4570 (enp5s0) | VIRTUAL-MACHINE | 0         | fedora2022 |
+----------+---------+------+-------------------------------------------------+-----------------+-----------+------------+

lxc info ubuntu01:

Name: ubuntu01
Status: RUNNING
Type: container
Architecture: x86_64
Location: fedora2022
PID: 27770
Created: 2023/01/20 04:40 CST
Last Used: 2023/01/20 04:47 CST

Resources:
  Processes: 67
  CPU usage:
    CPU usage (in seconds): 8
  Memory usage:
    Memory (current): 321.25MiB
    Swap (current): 4.00KiB
  Network usage:
    eth0:
      Type: broadcast
      State: UP
      Host interface: veth5b153284
      MAC address: 00:16:3e:5c:1b:70
      MTU: 1500
      Bytes received: 17.62kB
      Bytes sent: 15.62kB
      Packets received: 125
      Packets sent: 143
      IP addresses:
        inet6: fd42:3a3f:3d85:d02d:216:3eff:fe5c:1b70/64 (global)
        inet6: fe80::216:3eff:fe5c:1b70/64 (link)
    lo:
      Type: loopback
      State: UP
      MTU: 65536
      Bytes received: 18.04kB
      Bytes sent: 18.04kB
      Packets received: 238
      Packets sent: 238
      IP addresses:
        inet:  127.0.0.1/8 (local)
        inet6: ::1/128 (local)

lxc config show ubuntu01 --expanded:

architecture: x86_64
config:
  image.architecture: amd64
  image.description: ubuntu 22.04 LTS amd64 (release) (20230107)
  image.label: release
  image.os: ubuntu
  image.release: jammy
  image.serial: "20230107"
  image.type: squashfs
  image.version: "22.04"
  volatile.base_image: ed7509d7e83f29104ff6caa207140619a8b235f66b5997f1ed6c5e462617fb71
  volatile.cloud-init.instance-id: 17170660-9e29-497f-b7dc-ffe6656167e2
  volatile.eth0.host_name: veth5b153284
  volatile.eth0.hwaddr: 00:16:3e:5c:1b:70
  volatile.idmap.base: "0"
  volatile.idmap.current: '[{"Isuid":true,"Isgid":false,"Hostid":1000000,"Nsid":0,"Maprange":1000000000},{"Isuid":false,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]'
  volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":1000000,"Nsid":0,"Maprange":1000000000},{"Isuid":false,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]'
  volatile.last_state.idmap: '[]'
  volatile.last_state.power: RUNNING
  volatile.last_state.ready: "false"
  volatile.uuid: f9ceef4e-7c26-46a9-a61f-7b5c08a51700
devices:
  eth0:
    name: eth0
    network: lxdbr0
    type: nic
  root:
    path: /
    pool: default
    type: disk
ephemeral: false
profiles:
- default
stateful: false
description: ""

My host’s network interface:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 98:8f:e0:6a:71:45 brd ff:ff:ff:ff:ff:ff
3: wlp52s0f4u1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 50:2b:73:d4:5b:41 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.76/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp52s0f4u1
       valid_lft 35956sec preferred_lft 35956sec
    inet6 fe80::ff17:7004:6925:a3df/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
4: lxdbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:16:3e:cb:16:f5 brd ff:ff:ff:ff:ff:ff
    inet 10.137.187.1/24 scope global lxdbr0
       valid_lft forever preferred_lft forever
    inet6 fd42:3a3f:3d85:d02d::1/64 scope global 
       valid_lft forever preferred_lft forever
    inet6 fe80::216:3eff:fecb:16f5/64 scope link 
       valid_lft forever preferred_lft forever
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:dc:4b:56:bd brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:a8:4e:ff brd ff:ff:ff:ff:ff:ff
    inet 192.168.124.1/24 brd 192.168.124.255 scope global virbr0
       valid_lft forever preferred_lft forever
29: veth5b153284@if28: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master lxdbr0 state UP group default qlen 1000
    link/ether 62:51:6b:1b:34:3f brd ff:ff:ff:ff:ff:ff link-netnsid 0
30: tapf2cf581c: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master lxdbr0 state UP group default qlen 1000
    link/ether 76:71:d6:6d:c8:db brd ff:ff:ff:ff:ff:ff

lxc network list:

+-------------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
|    NAME     |   TYPE   | MANAGED |      IPV4       |           IPV6            | DESCRIPTION | USED BY |  STATE  |
+-------------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
| docker0     | bridge   | NO      |                 |                           |             | 0       |         |
+-------------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
| enp2s0      | physical | NO      |                 |                           |             | 0       |         |
+-------------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
| lxdbr0      | bridge   | YES     | 10.137.187.1/24 | fd42:3a3f:3d85:d02d::1/64 |             | 3       | CREATED |
+-------------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
| virbr0      | bridge   | NO      |                 |                           |             | 0       |         |
+-------------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
| wlp52s0f4u1 | physical | NO      |                 |                           |             | 0       |         |
+-------------+----------+---------+-----------------+---------------------------+-------------+---------+---------+

turtle0x1 · January 19, 2023, 9:21pm

Have you followed the docs with regards to docker?

https://linuxcontainers.org/lxd/docs/master/howto/network_bridge_firewalld/#prevent-issues-with-lxd-and-docker

wencan · January 20, 2023, 2:39am

@turtle0x1
sorry.
this doc didn’t solve my problem.
Maybe because I lack knowledge of iptables.
Can you help me to check the command below?

sudo iptables -I DOCKER-USER -i lxdbr0 -o wlp52s0f4u1 -j ACCEPT
sudo iptables -I DOCKER-USER -o lxdbr0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT