00:01:41Meli quits [Ping timeout: 260 seconds]
00:11:04nyakase quits [Remote host closed the connection]
00:12:49nyakase (nyakase) joins
00:47:45FiTheArchiver quits [Read error: Connection reset by peer]
01:09:33Bleo18260072271962345 quits [Quit: Ping timeout (120 seconds)]
01:09:50Bleo18260072271962345 joins
01:20:33BornOn420 quits [Remote host closed the connection]
01:21:09BornOn420 (BornOn420) joins
01:30:50Ryz quits [Read error: Connection reset by peer]
01:31:46Ryz (Ryz) joins
01:40:51@Fusl quits [Ping timeout: 260 seconds]
01:53:31Fusl (Fusl) joins
01:53:31@ChanServ sets mode: +o Fusl
04:04:21razul27 quits [Ping timeout: 260 seconds]
04:12:03razul27 joins
06:53:45Meli (Meli) joins
10:11:39FiTheArchiver joins
10:59:56thenes quits [Remote host closed the connection]
11:00:04Bleo18260072271962345 quits [Quit: The Lounge - https://thelounge.chat]
11:00:13thenes (thenes) joins
11:02:57Bleo18260072271962345 joins
11:03:31BornOn420 quits [Ping timeout: 276 seconds]
11:13:40BornOn420 (BornOn420) joins
11:16:36@imer quits [Ping timeout: 260 seconds]
11:36:01imer (imer) joins
11:36:01@ChanServ sets mode: +o imer
16:56:14kansei quits [Quit: ZNC 1.9.1 - https://znc.in]
17:08:41kansei (kansei) joins
18:07:23ATWF_notcarl joins
18:08:16<ATWF_notcarl>Hello happy archive team not support people! It is I, random internet person who barges into your channel. I have a query pertaining to running using podman on ipv6.
18:08:51<ATWF_notcarl>(i.e. "I'm probably the first person to do this, and of COURSE I chose that as my first attempt")
18:10:35<ATWF_notcarl>and you can probably imagine my 2 questions (:
18:11:36<ATWF_notcarl>(if not: "podman documentation suggests using 'podman generate systemd blah blah' but that's now deprecated, and doesn't produce any usable output."
18:12:05<ATWF_notcarl>"anyone have the output of what the command produced BEFORE?"
18:12:36<ATWF_notcarl>and then of course "am I going to have a lot of difficulty running this on a ipv6 only host"
18:13:20<ATWF_notcarl>- and yes, I'll probably go fiddle with it more instead of waiting around for an answer, so I'll just check in randomly over the next 24 hours.
18:14:07<ATWF_notcarl>- oh and I obviously mean running the archiveteam-warrior container under podman, not... general "how to podman"
18:49:57FiTheArchiver quits [Quit: Leaving]
19:02:57<ATWF_notcarl>It seems my config for non-root use was off, as when running as root, it's giving me the web interface. Likely it was something akin to 'not able to access a resource via cgroups'
19:18:01nyakase quits [Remote host closed the connection]
19:20:33nyakase (nyakase) joins
19:42:00Jake quits [Quit: Leaving for a bit!]
19:44:12<ATWF_notcarl>ok, a few more things:
19:44:43<ATWF_notcarl>first, if using podman on ipv6, you need to be sure you have it workign for ipv6; i.e. like so:
19:44:46<ATWF_notcarl>https://developers.redhat.com/articles/2022/08/10/how-conifgure-podman-40-ipv6#package_installation_and_configuration
19:45:05<ATWF_notcarl>(basically: enable ipv6, and use the netavark network backend)
19:45:14Webuser161207 quits [Quit: Ooops, wrong browser tab.]
19:45:56sec^nd quits [Remote host closed the connection]
19:46:01<ATWF_notcarl>if folks suspect difficulty, they can always use python and requests.request to test the archiveteam url... if it fails to connect, so will the archiveteam program.
19:46:10sec^nd (second) joins
19:51:23Webuser603791 joins
20:23:03nyakase quits [Remote host closed the connection]
20:27:15nyakase (nyakase) joins
20:27:34nyakase quits [Remote host closed the connection]
20:30:34nyakase (nyakase) joins
21:25:36Meli quits [Ping timeout: 260 seconds]
21:43:13<Webuser603791>Is there any way to abort the automatic restart countdown associated with the "The container has stopped responding" message?
22:06:26tek_dmn quits [Ping timeout: 260 seconds]
22:16:31tek_dmn (tek_dmn) joins
23:45:07daftaupe2 joins
23:46:46daftaupe quits [Ping timeout: 260 seconds]
23:46:46daftaupe2 is now known as daftaupe