this post was submitted on 06 May 2024
14 points (93.8% liked)

The Invisible Internet Project

1455 readers
22 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
 

I'm looking to try out i2p but I'm having trouble getting it going.

I have a docker-compose container going with this docker-compose.yml:

version: "3.5"
services:
    i2p:
        image: geti2p/i2p
        ports:
            - 4444:4444
            - 127.0.0.1:6668:6668
            - 7657:7657
            - 54321:12345
            - 54321:12345/udp
        volumes:
            - ./i2pconfig:/i2p/.i2p
            - ./i2ptorrents:/i2psnark
        restart: always
        environment:
            - IP_ADDR=0.0.0.0
            - JVM_XMX=1024m

The container starts up and the log outputs:

$ docker logs i2p-i2p-1 
Starting I2P
[startapp] Running in container
[startapp] setting reachable IP to container IP 0.0.0.0
Starting I2P 2.4.0-0

But when I try to access the console, I'm seeing:

$ curl localhost:7657
curl: (56) Recv failure: Connection reset by peer

Is there anything else that I need to do here?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 6 months ago