this post was submitted on 13 Sep 2024
8 points (100.0% liked)

Docker

1300 readers
2 users here now

founded 2 years ago
MODERATORS
 

I'm experimenting with i2p and a librewolf container setup in Docker compose. However, the i2p web console front end (127.0.0.1:7657) becomes inaccessible if the container itself is restarted. This can be remedied by removing the directories that get created by the volume mappings in the compose file, but this obviously not ideal. Anyone have experience with this problem? I've seen hints from people online suggesting that the data in those directories getting somehow corrupted. I have not yet investigated that further.

version: "3.5"
services:
  i2p_router:
    image:
      geti2p/i2p:latest
    environment:
    - JVM_XMX=256m
    volumes:
    - ./i2phome:/i2p/.i2p
    - ./i2ptorrents:/i2psnark
    ports:
    - 4444:4444
    - 6668:6668
    - 7657:7657
    - 9001:12345
    - 9002:12345/udp

  libre_wolf:
    image:
      linuxserver/librewolf
    ports:
    - 9300:3000
    - 9301:3001

volumes:
  i2phome:
  i2ptorrents:
networks:
  frontend:
    driver: bridge
you are viewing a single comment's thread
view the rest of the comments
[โ€“] onlinepersona@programming.dev 0 points 9 months ago* (last edited 9 months ago) (1 children)

You should probably look at the logs. It helps narrow down the issue and provide us also with more information.

Logs are either in the i2p home folder or in the docker logs.

Anti Commercial-AI license