00:07:29Guest58 quits [Ping timeout: 260 seconds]
01:01:16sec^nd quits [Remote host closed the connection]
01:01:32sec^nd (second) joins
01:27:26Guest58 joins
01:28:02fuzzy8021 quits [Ping timeout: 276 seconds]
01:51:25Guest58 quits [Read error: Connection reset by peer]
01:51:28Guest58_ joins
02:00:08BornOn420 quits [Remote host closed the connection]
02:02:50BornOn420 (BornOn420) joins
02:09:38Guest58_ quits [Client Quit]
02:29:11Guest58 joins
03:03:00Guest58 quits [Client Quit]
03:03:39GNU_world joins
03:04:14razul27 quits [Ping timeout: 260 seconds]
03:06:22Guest58 joins
03:12:30razul27 joins
03:31:18Guest58 quits [Client Quit]
03:33:25Guest58 joins
03:35:08Guest58 quits [Client Quit]
03:35:55Guest58 joins
03:53:38Guest58 quits [Client Quit]
04:48:37Guest58 joins
04:53:19Guest58 quits [Ping timeout: 260 seconds]
05:10:48Guest58 joins
05:22:29Guest58 quits [Client Quit]
05:25:42Guest58 joins
06:09:09Guest58 quits [Client Quit]
06:29:21Guest58 joins
07:21:59Hans5958 (Hans5958) joins
07:23:19<Hans5958>Yes, there are problems on the tracker and the Docker image repository (incl. pulling Warriors and per-project images). Expect issues on your Warriors at the moment. Stay tuned for updates.
07:25:17daftaupe quits [Quit: The Lounge - https://thelounge.chat]
07:29:20daftaupe joins
07:47:52Guest58 quits [Client Quit]
07:50:47Webuser285599 joins
07:51:13Webuser285599 quits [Client Quit]
07:51:16HardlineMouse16 joins
07:53:37Guest58 joins
08:02:44Webuser2856646 joins
08:03:20Webuser2856646 quits [Client Quit]
08:19:39<HardlineMouse16>Hello, I am trying to run warrior 4.1 in VirtualBox, it gets most of the way there but when it tries to download the docker image it fails at 66% and exits with code 1. It's a Client.Timeout exceeded while awaiting headers error. I tried pinging atdr.meo.ws and that works, and cURL -ing https://atdr.meo.ws/v2/ as well as
08:19:39<HardlineMouse16>https://atdr.meo.ws/archiveteam/warrior-dockerfile:latest and those seem to connect as well, but never download anything when using curl or my web browser
08:21:14<anonymoususer852>Known, https://irclogs.archivete.am/warrior/2025-07-05#laad9ea16
08:24:17<HardlineMouse16>Oh, sorry, didnt realise
08:24:55<anonymoususer852>All good, just stay tuned for more news. It's just been hours like this.
08:26:18<HardlineMouse16>Will do
08:40:08<anonymoususer852>May as well start adjusting the warrior 4.1 to your liking, while waiting. Not sure if it's only me but by default it uses the wrong emulated video adapter which causes flickering when switching to another TTY
08:43:26<anonymoususer852>I'm kinda half-tempted to mess with it, but at the same time it's kinda running projects, with limited degree of success, so that stops me from doing so. Like the video memory amount doesn't need to be that high as well
09:03:28<HardlineMouse16>What options are there? I did change the driver to VMSVGA but thats it
09:08:03<anonymoususer852>Yeah that's what I have it also set to; VMSVGA. I believe I did lower the video memory from like 16MB down to 8MB without issues, and am planning to go much less, just to see how low I can push it. Pretty sure a "headless" setup doesn't really need that much, as I am mostly SSHing into the machine, instead of having a window open for it. Other stuff are like changing RAM/CPU amounts, depending
09:08:09<anonymoususer852>on how many you want to run (concurrency), or for some larger projects like URLs
09:10:35<anonymoususer852>512MB of virtual system RAM from memory wasn't enough, it'll be quick to reap OOM killer and in my case, I decided to give it a generous 3GB instead. Amount of core/CPU count was raised from 1 (default) to 4 which kinda makes processing a bit faster, like some websites has PDF and those needs links to be extracted, which can bog down the single core if you do run it at a scale
09:28:57BearFortress quits []
09:53:20BornOn420 quits [Quit: Textual IRC Client: www.textualapp.com]
09:55:31BornOn420 (BornOn420) joins
10:14:38BearFortress joins
10:23:50UwU_93bydbco451y joins
10:31:04tzt quits [Ping timeout: 260 seconds]
10:33:32Webuser612859 joins
10:34:30<UwU_93bydbco451y>hi, couldn't help but noticing the back bones of warrior (`archiveteam/warrior-code2` and `ArchiveTeam/seesaw-kit` - I think?) haven't been updated for a while. Was more recent developments not published?
10:35:58<UwU_93bydbco451y>Also, my pc couldn't resolved atdr.meo.ws
10:36:54<UwU_93bydbco451y>going to meo.ws works though so I don't think it's the DNS
10:38:00<anonymoususer852>The atdr.meo.ws issue is likely a known issue, https://irclogs.archivete.am/warrior/2025-07-05#laad9ea16
10:39:41<UwU_93bydbco451y>ah
10:41:19<UwU_93bydbco451y>can I stuff seesaw-kit into an alpine image and call it a day?
10:43:17tzt (tzt) joins
10:44:39<anonymoususer852>warrior 4.1 is an alpine image. I don't know about the seesaw-kit part much, but it does look like there hasn't been much (release) activity since like 6 years ago.
10:50:54<UwU_93bydbco451y>wait really? I thought it was using some debian-esque image since `warrior-dockerfile/blob/master/Dockerfile` uses `apt-get`
10:52:01Webuser612859 quits [Client Quit]
10:57:04<anonymoususer852>That might have been warrior-preseed (ArchiveTeam/warrior-preseed). warrior 4.1 is using alpine as I am using that to run AT projects
11:00:04Bleo182600722719623455222 quits [Quit: The Lounge - https://thelounge.chat]
11:00:51<anonymoususer852>https://github.com/ArchiveTeam/warrior4-vm/?tab=readme-ov-file#using-the-disk-images - here it says to 'select either Alpine Linux 64-bit variant if available, or else "Other Linux (64-bit)"'
11:02:53Bleo182600722719623455222 joins
11:04:21<UwU_93bydbco451y>That is for the OS. I don't think it reveals much (if at all) about what the docker image which is running on top of it.
11:07:01<anonymoususer852>Also the tracker is back online, if you didn't catch the news
11:07:14<UwU_93bydbco451y>yeah I saw it
11:07:29<UwU_93bydbco451y>it 403'd for me tho...
11:07:59<UwU_93bydbco451y>maybe it's bc I'm using public wifi?
11:08:49<anonymoususer852>I am pretty certain warrior 4.1 is running alpine, I can see there's "warrior-dockerfile" via "docker ps" command
11:11:27<anonymoususer852>System updates are all using apk which is very alpine specific. The automated workflow on github for warrior4-vm uses ubuntu, but beyond that I believe it's alpine unless you have specific commands you want me to try and prove somehow that it isn't
11:19:18<UwU_93bydbco451y>well, if you have access to the VM's command line you can try to check if apk is installed or not by `docker exec <the container name from docker ps> apk -h`
11:20:19<UwU_93bydbco451y>I could have *sworn* I saw a way to check if a system is using musl-libc or gnu-libc sometime ago...
11:22:04<anonymoususer852>'warrior' appears to be accepting "dpkg" commands, so I suppose alpine is just the host
11:23:23<anonymoususer852>https://transfer.archivete.am/inline/3ar2x/docker.log
11:25:08<UwU_93bydbco451y>yeah the container most likely not using alpine as a base image
11:25:34<UwU_93bydbco451y>it doesn't know what apk is
11:26:12<UwU_93bydbco451y>I do see something about an experimental "apk.sh" though
11:35:25<anonymoususer852>docker image appears to be running debian 12, via 'docker exec warrior cat /usr/lib/os-release'
12:12:26Guest58 quits [Quit: My Mac has gone to sleep. ZZZzzz…]
12:13:58Guest58 joins
12:51:08Meli (Meli) joins
12:51:20<Hans5958>ICYMI: The issue has been resolved.
13:03:06ryman1 joins
13:05:45ryman1 quits [Client Quit]
14:27:19UwU_93bydbco451y quits [Ping timeout: 260 seconds]
14:54:37Senk0 joins
15:00:26<Senk0>Hey, I'm not 100% sure if this is the right channel for this, but I'm running warrior in my K8s cluster and its barely using any resources. I read through the networking requirements and I meet them, but they specifically mention to not run on shared networks, which is what clustering effectively does. Any idea if just setting replicas to 3 or so
15:00:27<Senk0>would be bad if set to auto? I would assume that selecting a manual project per replica would be fine, but I'm not positive that leaving on auto and scaling up is correct.
15:00:27<Senk0>Thank you for the reply in advance.
15:44:22Guest58 quits [Quit: My Mac has gone to sleep. ZZZzzz…]
15:44:47Guest58 joins
15:47:11Guest58 quits [Client Quit]
16:19:23Exorcism quits [Quit: Bye!]
16:25:35Exorcism8 (exorcism) joins
16:27:19Senk0 quits [Client Quit]
16:28:02Exorcism8 is now known as Exorcism0666
17:19:34fuzzy80211 (fuzzy80211) joins
17:20:00Webuser406114 joins
17:20:21Webuser406114 quits [Client Quit]
18:00:12HardlineMouse16 leaves [Ooops, wrong browser tab.]
18:26:02archiveDrill quits [Quit: The Lounge - https://thelounge.chat]
19:01:24BornOn420 quits [Remote host closed the connection]
19:01:59BornOn420 (BornOn420) joins