NegativeLookBehind

joined 1 year ago
MODERATOR OF
[–] NegativeLookBehind@lemmy.world 6 points 1 hour ago (6 children)

Your credit must be completely fucked

[–] NegativeLookBehind@lemmy.world 1 points 10 hours ago

Soon your triangles will be completely unmanageable. What will you do then?

[–] NegativeLookBehind@lemmy.world 4 points 11 hours ago

I was hoping for more of a Terminator style Jesus, you know?

[–] NegativeLookBehind@lemmy.world 7 points 21 hours ago (3 children)

How did you find this one?

Also, approximately how many knives do you own?

[–] NegativeLookBehind@lemmy.world 6 points 22 hours ago (2 children)

Dude, I’ve been there. It’s creepy as shit and super amazing. You should go.

[–] NegativeLookBehind@lemmy.world 3 points 1 day ago (2 children)

Liar! Sinner! You should be raptured immediately!

Can confirm, am dead.

I totally honestly believed that. I’m just so naive, how do I get by in life? Thank goodness you’re here to set me straight. What would I do without you? How did you get so good at computers? You must be some kind of wizard.

My question was mostly a light jab at OP

 

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
 
 
 
 
view more: next ›