03:35:59<OrIdow6>So is this currently hung up on on luasocket inclusion?
03:37:11TheLovinator quits [Quit: Leaving]
03:41:23Jake (Jake) joins
07:35:15@arkiver quits [Excess Flood]
07:35:46arkiver (arkiver) joins
07:35:46@ChanServ sets mode: +o arkiver
09:05:47Henk53 joins
09:37:14<Henk53>Hey there! I have troubles getting the warrior to run in Docker on a Synology NAS. The problem is similar to https://github.com/ArchiveTeam/warrior-dockerfile/issues/38 and I've tried the workarounds there, but unfortunately it does not work. Permissions seems to be set correctly for the file and I tried running privileged mode, which did nothing.
09:37:15<Henk53>Furthermore I tried logging in to the container, removing the config file and readding it through the env_to_json.sh script, but that resulted in the same previous restart loop. Anyone got an idea what I could try next?
14:21:56<@arkiver>fix for the warrior is pretty easy probably, just need to test it
14:22:08<@arkiver>will try do get that done today
14:23:47Guest69 joins
14:27:26Arcorann quits [Read error: Connection reset by peer]
15:42:08Guest69 is now known as bithippo
16:05:40Henk53 quits [Ping timeout: 244 seconds]
17:47:07bithippo quits [Client Quit]
22:23:10Arcorann (Arcorann) joins