this post was submitted on 12 Jun 2023
3 points (100.0% liked)

The Invisible Internet Project

1452 readers
1 users here now

I2P Community Edition

This isn't the official I2P channel, if you want go there then you can find it in the links below.

Rules

"Don't be a dick" - Wil Wheaton

General

Media:

File Hosting and Pastebins

Torrents

Social Networks and Microblogging

Exploring I2P

I2P Name Registries

Search engines

IRC

Irc2P comes pre-configured with I2P. To connect with other networks, please follow this tutorial.

Syndie

An open source system for operating distributed forums in anonymous networks

Inproxies

You can use inproxies to surf the I2P network without having to have an I2P router.

Follow us on Twitter

founded 1 year ago
MODERATORS
CAVOK
[email protected]
3
I2P Docker Container Question (monero.house)
submitted 1 year ago by [email protected] to c/i2p
6 comments fedilink hide all child comments
 

Hi so I'm following the docker compose section on Installing I2P in Docker, the docker image pulls and deploys fine but how do I make it so the router is accessible outside its own network as can't get to http://127.0.0.1:7657/ as the container is running inside a virtual machine. Is there any way to change the config so I can access the router via the LAN IP address instead of the loopback IP?

top 6 comments
sorted by: hot top controversial new old
[–] [email protected] 4 points 1 year ago (1 children)

for it to listen on all interfaces for that specific port. Notice that you need to remove the "network_mode: host" to be able to mapp ports. you will need to mapp all the ports that the service is using.

version: "3.5"
services:
    i2p:
        image: geti2p/i2p
        network_mode: host
        volumes:
            - ./i2pconfig:/i2p/.i2p
            - ./i2ptorrents:/i2psnark
    ports:
      - 7657:7657
[–] [email protected] 1 points 1 year ago

Thanks for this, I figured it out this exact way as well. Not really documented to do it this way so probably worth updating the documentation and the i2p compose script.

[–] 0v0 3 points 1 year ago (1 children)

Also not a docker user, but I notice the tutorial states:

That means that the services in the list above which are bound to 127.0.0.1 (which include the router console) will need to be accessed via other methods like ssh tunneling or be manually configured to bind to a different interface.

What is your host OS? On linux you can use iptables/nftables to setup a forward.

[–] [email protected] 2 points 1 year ago

I've got it running in an alpine VM. I'm going to try bind it to the local lan interface but it's basically only to access the getting started portion, the rest will be bound to other docker containers as the network for those containers.

[–] CAVOK 1 points 1 year ago (1 children)

I'm not exactly sure what you're asking as I'm not a Docker user myself, but there's some config you can change in http://127.0.0.1:7657/configi2cp for allowing access from "the outside".

[–] [email protected] 2 points 1 year ago

Thanks I'll tinker around with this.