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
Yeah, I looked at the logs originally, and would’ve posted them had they been relevant. The problem is, the logs do not differ between a working and non-working container. They’re literally this, before and after a restart:
Starting I2P [startapp] Running in container [startapp] Running in docker network [startapp] setting reachable IP to container IP 172.26.0.2 Starting I2P 2.5.2-0 OpenJDK 64-Bit Server VM warning: You have loaded library /tmp/i2p-JtRKWUcL.tmp/libjbigi.so which might have disabled stack guard. The VM will try to fix the stack guard now. It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.docker compose exec i2p_router tail -F .i2p/wrapper.logFor 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.Anti Commercial-AI license