NegativeLookBehind

joined 1 year ago
MODERATOR OF
[–] [email protected] 53 points 1 day ago

Open(your fucking wallet)AI

[–] [email protected] 9 points 1 day ago

As a long time fan of his, this was not one of his greatest ideas for a joke.

[–] [email protected] 8 points 1 day ago

I long to fornicate with many a sea bound trollop, under the blazing fire of a worthy vessels’ cannons

[–] [email protected] 4 points 2 days ago

Like blowing dust off an old library book

[–] [email protected] 17 points 2 days ago* (last edited 2 days ago)

Let it be known that dear leader has backed down from a debate with…

gasps

A black woman

[–] [email protected] 3 points 2 days ago

Lol this is awesome

[–] [email protected] 12 points 2 days ago

One of JDs illegitimate children about to be born

[–] [email protected] 1 points 2 days ago* (last edited 2 days ago)

Doing more digging, I captured checksums of all files that get created by the i2p container, with

find i2p* -type f -exec md5 {} + > 1sum # After starting container

and

find i2p* -type f -exec md5 {} + > 2sum # After restarting container

Comparing the files with diff -y 1sum 2sum, I noticed this file was the only one whose checksum changed:

MD5 (i2phome/router.ping) = 95fd0fa14b084cf019f2dd9e0884aa1 | MD5 (i2phome/router.ping) = f4b060ae4f789f7d24f2851c06597c4

EDIT:

Preserving this file outside of the volume directory and copying it back in after the container restarts allows the web console to function as expected.

EDIT 2:

To take it a step further, I'm mounting it read only into the container at runtime like this:

- ./router.ping:/i2p/.i2p/:ro

which is sort of a hack, but I think I can live with it.

[–] [email protected] 1 points 2 days ago (1 children)

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'.
[–] [email protected] 58 points 2 days ago (5 children)

I get his campaign propaganda in my mailbox every single day. It’s always the same garbage message, super pinky-swearing that he’s not a fascist authoritarian dickhead.

[–] [email protected] 8 points 3 days ago

Those poor celebrities! What will we do without them?

[–] [email protected] 38 points 3 days ago* (last edited 3 days ago) (4 children)

She turned me into a newt!

view more: ‹ prev next ›