Docker shows that my SNO container listens on IPV6... How to disable IPV6?

Node Operators troubleshooting
,
1

I’m running few SNO nodes via Docker on my Synology with DSM 7.2.

It appears, that every node is running with IPV6 enabled. I’m telling that because of ::: in the docker ps output:

PORTS 0.0.0.0:30101->14002/tcp, :::30101->14002/tcp, 0.0.0.0:30001->28967/tcp, 0.0.0.0:30001->28967/udp, :::30001->28967/tcp, :::30001->28967/udp

But I don’t have IPV6.

So far, it looks like there is nothing bad happens because of that.
But it seems wrong that SNO reports, that it listens on IPV6, when it is IPV4-only node.

So, is there a way to disable IPV6 for the node?

2

Yes, it’s possible. However, no need to fix what’s not broken.
If you’d like to have adventures, you may just limit port mapping to use only IPv4 of your network interface, i.e.

-p 192.168.0.2:30001:28967/tcp \
-p 192.168.0.2:30001:28967/udp \
-p 192.168.0.2:30101:14002 \

or to listen on any IPv4:

-p 0.0.0.0:30001:28967/tcp \
-p 0.0.0.0:30001:28967/udp \
-p 0.0.0.0:30101:14002 \

Or disable IPv6 globally on your Synology and/or router: https://community.synology.com/enu/forum/17/post/105676

By the way, SNO = Storage Node Operator, i.e. it’s you :slight_smile:
Please, do not convert yourself to a container!

1 Like
3

Thank you for that -p 0.0.0.0 idea.
Works, as expected.

IPV6 is already disabled on the router and Synology host. But docker still was listening on IPV6. Fixed with your advice. Thank you.

1 Like