| 01:36:39 | | OrIdow6 (OrIdow6) joins |
| 02:21:43 | | justcool393 (justcool393) joins |
| 02:25:36 | <tech234a> | Just trying to understand how the Warrior works; I understand that it is Docker based, but I was told that it just uses one Docker container for all of the projects... why not have it pull and run individual Docker containers for each project? |
| 02:26:15 | <tech234a> | Wouldn’t that fix most of the compatibility problems? |
| 03:39:06 | <@chfoo> | it could, but it causes a bigger stovepipe organization because, for example, instances inside the container will now need coordination to ensure it doesn't exceed the maximum number of task to process in parallel |
| 03:41:47 | <@chfoo> | seesaw-kit, which manages the items and project in the warrior vm appliance, was never meant to be run within docker since it thinks it is physically rebooting a virtual machine |
| 03:43:36 | <@chfoo> | hmm, fusl isn't in this channel to help explain |
| 03:51:55 | <tech234a> | On a simpler level, could the VM be changed to be kind of a basic wrapper (project selection and container downloading/starting), leaving most of the coordination to occur within the Docker container? Or does task coordination need to occur outside of the Docker container? |
| 05:21:31 | | Craigle0 quits [Ping timeout: 244 seconds] |
| 06:01:14 | | Craigle (Craigle) joins |
| 13:41:03 | <@Kaz> | some work (tm) is happening in this space |
| 13:41:13 | <@Kaz> | there was a brief discussion about it the other day in another channel |
| 13:41:34 | <@Kaz> | the view is: the future is docker, we just need to work out how to make it 'easy' |
| 14:44:10 | | Craigle quits [Ping timeout: 244 seconds] |
| 15:18:05 | | Craigle (Craigle) joins |