maidsafe / temp_safe_network

The Safe Network. A libp2p backed data and transfer network
106 stars 41 forks source link

My IPv4 rootless podman container (Ubuntu 22.04) comnet has "timed out" issues #1126

Closed Folaht closed 2 years ago

Folaht commented 2 years ago

Host

Container

https://safenetforum.org/t/need-help-my-ipv4-rootless-podman-container-ubuntu-22-04-comnet-has-timed-out-issues/36926

All errors are yet again from the non-root nodes.

 INFO 2022-04-17T00:07:45.035001Z [sn/src/node/api/mod.rs:L209]:
     ➤ 8f02f4.. Bootstrapping a new node.
 ERROR 2022-04-17T00:08:21.468893Z [/cargo/registry/src/github.com-1ecc6299db9ec823/qp2p-0.28.5/src/endpoint.rs:L278]:
     ➤ bootstrap
     ➤ Failed to bootstrap to the network, last error: timed out
 DEBUG 2022-04-17T00:08:21.469938Z [sn/src/node/core/comm/mod.rs:L548]:
     ➤ count_msgs
     ➤ Entered msg counting listener loop.

Command run for node #2 out of 16:

sn_node -vvvv 
--idle-timeout-msec 5500 
--keep-alive-interval-msec 40000 
--skip-auto-port-forwarding 
--local-addr 10.88.0.2 
--public-addr my.ip.v.4 
--log-dir /home/admin/.safe/node_dir_1 
--root-dir /home/admin/.safe/node_dir_1 
--hard-coded-contacts [10.88.0.2:12000]

ip addr inside container

admin@e7c8edc6d8da:~/.safe/node$ ip addr
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: eth0@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 92:8c:93:6d:59:6c brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 10.88.0.2/16 brd 10.88.255.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::908c:93ff:fe6d:596c/64 scope link
       valid_lft forever preferred_lft forever

podman run command

podman run 
--name root_node 
--network podman 
--publish 192.168.178.26:12000-65535:12000-65535/udp 
--env CON_IP=10.88.0.2 
--env CON_PORT=12000 
--env PUB_IP=my.ip.v.4 
--env PUB_PORT=12000 
--env VERBOSE=-vvvv 
--userns=keep-id --ip 10.88.0.2 
-v root_node_vol:/home/admin/.safe/cli 
-d ghcr.io/safenetwork-community/rootnode-ipv4:ubuntu
joshuef commented 2 years ago

Closing as we don't directly use or support podman, so can't offer any advice here. Such third party issues are better to duscuss on the forum, where hopefully somone can help (safenetforum.org/). Good luck!