docker-compose with a specified IP address - works with 1.5, doesn't work with 1.7

Thanks for the great software. I am using docker-compose to run I2P and need to specify the IP address for my I2P container. Using the following example docker-compose.yml (modified from https://geti2p.net/en/download/docker):

version: "3.5"

services:
    i2p_test_cont:
        container_name: i2p_test_cont
        image: geti2p/i2p:i2p-i2p-1.5.0
        networks:
          12p_test_net:
            ipv4_address: 172.28.1.1
        volumes:
            - i2pconfig:/i2p/.i2p
            - i2ptorrents:/i2psnark

volumes:
  i2pconfig:
  i2ptorrents:

networks:
    12p_test_net:
        ipam:
            driver: default
            config:
                - subnet: 172.28.0.0/16

When started with docker-compose up --build, I am able to connect to http://172.28.1.1:7657 and reach the console UI.

However, if I use the image tag i2p-i2p-1.7.0 or latest, instead of i2p-i2p-1.5.0, I am not able to access the console UI at http://172.28.1.1:7657.

Strangely, if I first build and bring up with i2p-i2p-1.5.0, then bring down, change the tag to i2p-i2p-1.7.0, then build and bring up, I am able to access the console UI at http://172.28.1.1:7657 and it does state 1.7.x is the version running.

Can anyone explain what is causing this issue and help me understand how to use a specific IP address with i2p-i2p-1.7.0 and not have to go through this convoluted process to get it running?

Thanks, BC

changed the description

assigned to @idk

added docker label

this thread may have the answer: http://zzz.i2p/topics/3305

Yes this is exactly the same issue. You need to configure the console and the tunnels to listen on the host/IP address that you will actually be accessing it from, or to listen on all possible addresses(0.0.0.0). Otherwise you get this issue, which is actually by design. Changing it to 0.0.0.0 turns it into a bit of a footgun, it's much easier to misconfigure if we do that.

Instead, what might be an improvement to the behavior of the docker container is if the IP address inside the docker network could be detected and inserted into router.config, clients.config, and i2ptunnel.config automatically at runtime if:

1. 127.0.0.1 is still present on the config(we could also insert a different "placeholder" value for the initial configuration to avoid interference after the first run if the config is persisted in a volume)
2. We know that the container is using a docker network and not sharing a network with the host directly.

I think that seems like a good idea.

closed with commit a70c988a