I’m glad we could collaborate on this effort and teach people some shit 🤝
I’m glad we could collaborate on this effort and teach people some shit 🤝
Fuck yeah dude
Do VPSs typical give you LOM? Honest question. Maybe LUKs isn’t good if you can’t console in.
JDV is like a toddler trying to trick you by hiding behind the curtains, but you can still see his Scooby Doo Velcro shoes and he’s back there giggling.
LUKS
VPN
Encrypt sensitive files
Cursing is an art, and adds color to otherwise bland sentences and communication. Curse words emphasize tone, inflection, emotion.
If you’re not very good at cursing, maybe you should fuckin’ practice more.
NAS
I long to fornicate with many a sea bound trollop, under the blazing fire of a worthy vessels’ cannons
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.
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'.
Those poor celebrities! What will we do without them?
That’s enough blue food coloring to give you instant butt cancer.
Um, hell yeah
France isn’t real!
You’re welcome. I would do anything for you.
Those god damned democrats are coming for my ducks
Is this a cry for help?
WW3, great for profits!