cap total connections, and document the P2P port 8444

The daemon has always listened on 8444 and nothing published it, so every node built from this image was outbound-only. Publishing it is now a documented choice rather than an omission -- including the two things that are not obvious from the config: peers are told the port from `port` in keys.dat rather than the one you mapped it to (so only 8444:8444 works), and the node's own address is never configured at all, because every peer replaces the hardcoded 127.0.0.1 in the version message with the IP it sees on the socket. An open port needs a brake, hence BITMESSAGE_MAXTOTALCONNECTIONS. It defaults to the PyBitmessage stock 200, so nothing changes for existing users of the image. The key is inserted when the stock config lacks it instead of trusting the substitution: the PyBitmessage clone is unpinned, and a silent no-op would ship a node that looks capped and is not. The API port in the example compose moves to loopback, which is what the README already prescribed.
2026-08-02 14:48:01 +00:00
parent 335ee52c0d
commit 2701c57200
5 changed files with 96 additions and 7 deletions
@@ -45,7 +45,11 @@ RUN f=/usr/local/lib/python2.7/dist-packages/pybitmessage/helper_sql.py \

 FROM ubuntu:bionic

+# 8442 is the XML-RPC API (keep it on loopback), 8444 the Bitmessage P2P port.
+# The daemon listens on both regardless; publishing 8444 is what makes the node
+# reachable for inbound peers.
 EXPOSE 8442/tcp
+EXPOSE 8444/tcp

 ENV USER_UID=2000
 ENV USER_GID=2000