| 00:13:37 | | @Sanqui quits [Quit: .] |
| 00:21:58 | | Sanqui joins |
| 00:22:00 | | Sanqui is now authenticated as Sanqui |
| 00:22:00 | | Sanqui quits [Changing host] |
| 00:22:00 | | Sanqui (Sanqui) joins |
| 00:22:00 | | @ChanServ sets mode: +o Sanqui |
| 01:34:21 | | mut4ntm0nkey quits [Ping timeout: 255 seconds] |
| 01:36:30 | | Meli quits [Ping timeout: 265 seconds] |
| 01:38:44 | | Meli (Meli) joins |
| 01:41:03 | | mut4ntm0nkey (mutantmonkey) joins |
| 03:46:19 | | kurusii joins |
| 03:49:01 | <kurusii> | hey everyone; i've never been here on IRC before, but i've been running a warrior instance for years on an ESXi box i use for homelab-type things. that's mostly my question: i installed the appliance years ago and just never touched it, and it just occurred to me, is there any updating i need to do on my end? |
| 03:49:11 | <kurusii> | i don't even see a version in the about section of the web UI |
| 03:49:35 | <kurusii> | i just want to make sure i've actually been, you know, helping out the project all this time... |
| 03:50:16 | <kurusii> | if the answer is in the FAQ and i missed it, i apologize in advance. |
| 03:55:23 | | kurusii is now authenticated as kurusii |
| 05:10:18 | | Craigle quits [Quit: The Lounge - https://thelounge.chat] |
| 05:12:03 | | Craigle (Craigle) joins |
| 05:51:13 | | qwertyasdfuiopghjkl quits [Ping timeout: 265 seconds] |
| 06:27:39 | <theblazehen|m> | Yeah it does auto-update |
| 06:33:45 | <@JAA> | Depends on what 'years' means. There was a new appliance version early last year (March 2021). The auto-updating only applies to project stuff, not the appliance as a whole. |
| 06:34:21 | <theblazehen|m> | Does it not run watchtowerr in the appliance? |
| 06:34:29 | <@JAA> | You might want to update to the appliance 3.2, although I'm not sure whether that's necessary or not. I think we were already using Docker containers in the VM before that, and the containers would be updating. |
| 06:36:49 | <@JAA> | theblazehen|m: Only since version 3.2 it seems. It was added in February 2021: https://github.com/ArchiveTeam/Ubuntu-Warrior/commit/fdd5ce8b2ed7adfc7b31499ab36fe2cd425ffad1 |
| 06:37:05 | <theblazehen|m> | Ah, thanks |
| 06:39:07 | <@JAA> | There was probably some insane hack before that with a similar but subtly broken effect. |
| 06:53:24 | <tech234a|m> | 3.0 (released in 2017) and later should automatically update to the latest internal Docker image (I believe I tested this), but earlier versions definitely will not. It shouldn’t matter for now, but 3.0/3.1 use an older version of Alpine Linux/Docker for the “outermost layer”, which is not automatically updated. |
| 06:57:11 | <tech234a|m> | The update was distributed using a script that is automatically pulled from GitHub each time the virtual machine is started. The script checks if the change has been made within the VM, and if not, automatically reconfigures the environment to use the updated version. I believe I have been told that the VM automatically restarts weekly so it should be applied to all running instances of 3.0 and later by now. |
| 07:03:56 | <tech234a|m> | Besides Alpine Linux and Docker updates, there are some other improvements specific to 3.2 like faster startup and ability to view Warrior container logs on TTY2 and Watchtower Logs on TTY3 |
| 07:35:10 | | Meli quits [Client Quit] |
| 07:38:54 | | Meli (Meli) joins |
| 09:03:25 | | knecht420 quits [Quit: The Lounge - https://thelounge.chat] |
| 09:04:21 | | knecht420 (knecht420) joins |
| 10:12:09 | | Sluggs quits [Ping timeout: 268 seconds] |
| 10:12:31 | | Minkafighter7 quits [Quit: The Lounge - https://thelounge.chat] |
| 10:14:32 | | Minkafighter7 joins |
| 10:51:07 | | qwertyasdfuiopghjkl joins |
| 11:19:20 | | qwertyasdfuiopghjkl_ joins |
| 11:22:47 | | qwertyasdfuiopghjkl quits [Ping timeout: 265 seconds] |
| 11:25:31 | | qwertyasdfuiopghjkl_ is now known as qwertyasdfuiopghjkl |
| 11:37:15 | | Meli quits [Ping timeout: 268 seconds] |
| 11:43:37 | | Meli (Meli) joins |
| 13:38:33 | | Meli quits [Ping timeout: 276 seconds] |
| 13:41:28 | | Meli (Meli) joins |
| 14:31:00 | | Meli quits [Ping timeout: 245 seconds] |
| 14:31:00 | | qwertyasdfuiopghjkl quits [Remote host closed the connection] |
| 14:31:10 | | Meli (Meli) joins |
| 15:05:21 | | qwertyasdfuiopghjkl_ joins |
| 15:06:27 | | qwertyasdfuiopghjkl_ is now known as qwertyasdfuiopghjkl |
| 16:32:55 | | mrfooooo0 joins |
| 16:36:39 | | Meli quits [Ping timeout: 276 seconds] |
| 16:44:43 | | Meli (Meli) joins |
| 16:45:45 | | mrfooooo0 quits [Ping timeout: 276 seconds] |
| 16:48:28 | | mrfooooo0 joins |
| 16:54:28 | | mrfooooo0 quits [Remote host closed the connection] |
| 17:01:58 | | mrfooooo0 joins |
| 19:28:15 | | yawkat quits [Ping timeout: 276 seconds] |
| 19:35:47 | | Meli quits [Ping timeout: 268 seconds] |
| 19:41:27 | | Meli (Meli) joins |
| 20:11:09 | | Meli quits [Client Quit] |
| 20:11:22 | | Meli (Meli) joins |
| 20:34:33 | | fuzzy8021 quits [Ping timeout: 276 seconds] |
| 20:37:31 | | fuzzy8021 (fuzzy8021) joins |
| 20:39:45 | | Meli quits [Ping timeout: 276 seconds] |
| 20:41:46 | | Meli (Meli) joins |
| 21:01:42 | | qwertyasdfuiopghjkl_ joins |
| 21:04:43 | | qwertyasdfuiopghjkl quits [Ping timeout: 265 seconds] |
| 21:14:08 | | qwertyasdfuiopghjkl_ is now known as qwertyasdfuiopghjkl |
| 21:17:50 | | mrfooooo0 quits [Remote host closed the connection] |
| 21:56:57 | | fuzzy8021 quits [Remote host closed the connection] |
| 21:56:57 | | qwertyasdfuiopghjkl quits [Remote host closed the connection] |
| 22:00:34 | | fuzzy8021 (fuzzy8021) joins |
| 22:34:48 | | Meli quits [Ping timeout: 276 seconds] |
| 22:40:34 | | Meli (Meli) joins |
| 23:36:39 | | qwertyasdfuiopghjkl_ joins |
| 23:58:47 | | @AlsoJAA quits [Remote host closed the connection] |