00:05:49monoxane quits [Quit: estoy fuera]
04:57:08monoxane (monoxane) joins
04:57:10monoxane quits [Remote host closed the connection]
04:58:08monoxane (monoxane) joins
05:14:35systwi quits [Ping timeout: 272 seconds]
06:10:25systwi (systwi) joins
07:23:39sec^nd quits [Ping timeout: 255 seconds]
07:24:10sec^nd (second) joins
08:24:51sec^nd quits [Ping timeout: 255 seconds]
08:29:16sec^nd (second) joins
09:00:04Bleo182600 quits [Client Quit]
09:01:26Bleo182600 joins
09:18:51sec^nd quits [Ping timeout: 255 seconds]
09:19:34sec^nd (second) joins
09:27:17tbc18871 (tbc1887) joins
09:28:34tbc1887 quits [Ping timeout: 255 seconds]
09:28:34tbc18871 is now known as tbc1887
10:03:16zhongfu quits [Quit: cya losers]
13:37:37magmaus3 (magmaus3) joins
14:55:54KiviStone joins
15:00:30<KiviStone>Does anyone have experience setting warrior docker on synology nas? I can connect to network but it wont start projects. What should I set to path volume ? logs: https://pastebin.com/raw/Zt0vwbJs
15:03:13<imer>KiviStone: looks to be an issue with the blogger project?
15:03:13<imer>arkiver: ^ "/home/warrior/projects/blogger/warrior-install.sh: line 4: sudo: command not found"
15:04:32<imer>the blogger project is pretty much empty anyways, so not much to contribute there
15:04:44<imer>at the moment*
15:04:58<KiviStone>I have tried other projects too but none seem to work for me
15:05:09<imer>do you get the same error with a different one?
15:05:24<imer>deviantart for example
15:05:59<KiviStone>here: https://pastebin.com/raw/ysjFx9pc
15:10:09zhongfu (zhongfu) joins
15:11:40<imer>KiviStone: any chance your docker image is old? (should only happen if you've used it in the past on that host and it didnt fetch a new version) otherwise I have no idea
15:11:50<imer>the warrior docker image*
15:12:13<KiviStone>i have this https://registry.hub.docker.com/r/archiveteam/warrior-dockerfile/
15:12:48<imer>the plot thickens :)
15:12:48<imer>you want to use atdr.meo.ws/archiveteam/warrior-dockerfile
15:12:56<imer>not the docker hub one
15:13:12<KiviStone>Ok, lets try that!
15:14:19<imer>JAA: can you archive (not to say delete) the docker hub one? looks like you might have access looking at the last push
15:17:17<KiviStone>Is it normal that the dockerfile says "nope" ?
15:23:54<KiviStone>I cant add it
15:31:12<imer>KiviStone: not sure how this would work in the synology ui, but for the docker command line you'd just specify that whole link when starting a container instead of a short name (which will go to docker hub by default)
15:31:21<imer>and yeah, there's no web interface
15:31:34<imer>just a docker container registry on atdr.meo.ws
16:02:07JaffaCakes118 quits [Remote host closed the connection]
16:02:27JaffaCakes118 (JaffaCakes118) joins
18:10:55<@JAA>imer: Yeah, I've been meaning to, but I haven't figured out how to archive the older images yet. Build logs are gone, and I don't know whether the image IDs are available anywhere else. Docker Hub (intentionally?) makes that painful.
18:31:50JaffaCakes118 quits [Remote host closed the connection]
18:32:13JaffaCakes118 (JaffaCakes118) joins
18:34:28<imer>or replace it with a container that prints “get the real one” i guess
18:35:36<@JAA>Yeah
18:36:25<@JAA>The readme already references the atdr.meo.ws image, but nobody reads that.
18:37:06<@JAA>On the other hand, it also talks about running things on RPi, and nobody *should* read that.
19:20:51thalia quits [Quit: Connection closed for inactivity]
19:37:49zhongfu quits [Ping timeout: 272 seconds]
21:10:53JaffaCakes118 quits [Remote host closed the connection]
21:11:14JaffaCakes118 (JaffaCakes118) joins
22:32:33BearFortress quits [Client Quit]
23:42:51KiviStone quits [Client Quit]
23:46:55JaffaCakes118 quits [Remote host closed the connection]
23:47:14JaffaCakes118 (JaffaCakes118) joins