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 must log in or register to comment.
deleted by creator
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.
deleted by creator
- How long did you wait for the router to be back up?
- Have you looked at the logs within the container?
docker compose exec i2p_router tail -F .i2p/wrapper.log
For me, it comes back up after a few seconds.
WARN: There may be another router already running. Waiting a while to be sure... WARN: Old router was not shut down gracefully, deleting /i2p/.i2p/router.ping INFO: No, there wasn't another router already running. Proceeding with startup.
