| 14 Feb 2022 |
 @mic92:nixos.dev | zimbatm: might know this. | 08:34:02 |
 lewo | Mic92: yep, that would actually be possible | 08:34:09 |
| @mic92:nixos.dev | But maybe do some research. I think there are tons of example easily available. | 08:34:32 |
| @mic92:nixos.dev | It's a quite common use case | 08:34:42 |
| @mic92:nixos.dev | I recently also added podman as an unprivileged services in one ci system. | 08:36:10 |
| @mic92:nixos.dev | I needed it for docker-compose | 08:36:17 |
| @mic92:nixos.dev | There are also nix-shell envs available for this | 08:36:27 |
| @mic92:nixos.dev | This would be nice for local testing as well | 08:36:34 |
| @mic92:nixos.dev | * I recently also added podman as an unprivileged service in one ci system. | 08:36:56 |
| @mic92:nixos.dev | https://gist.github.com/adisbladis/187204cb772800489ee3dac4acdd9947 | 08:37:31 |
| lewo | wow, cool! | 08:39:30 |
 @zimbatm:numtide.com | lewo: each "job" in Github Actions spawns an ephemeral VM, with a ton of stuff pre-installed on it. Part of that already includes docker and docker-compose. Each "step" in a job is just a command that's running in this machine. So you can have one step building all your containers, and then a step that docker load -i and runs docker-compose or whatever afterwards. | 09:21:07 |
| lewo | zimbatm: thx for the explanation!
This should then be quite easy to run all example containers ;) | 09:27:33 |
|  @test:boba.best changed their display name from Tseb to Tseb (Old). | 12:52:32 |
| 18 Feb 2022 |
| @test:boba.best removed their profile picture. | 11:29:13 |
| @test:boba.best removed their display name Tseb (Old). | 11:55:30 |
| @test:boba.best left the room. | 13:08:16 |
| 23 Feb 2022 |
| lewo | FYI, a small PR to fix the OpenStack image: https://github.com/NixOS/nixpkgs/pull/161388 | 13:25:58 |
 Arian | https://twitter.com/ProgrammerDude/status/1496203404368044034 | 13:32:11 |
| 2 Mar 2022 |
|  phaer set a profile picture. | 13:09:04 |
| phaer changed their display name from phaer to Paul Haerle. | 13:09:34 |
