| 19 Mar 2025 |
 magic_rb | I dont think it would need any actual programming, if we were to bolt runc on the bottom | 10:21:49 |
| magic_rb | Just a healthy amount of nix and maybe some bash | 10:21:56 |
| magic_rb | Ill try to retarget my ucontainer thing i use to run NixNG containers on top of runc first tho | 10:22:30 |
 ElvishJerricco | do other container systems integrate as nicely with systemd as nspawn does? e.g. nspawn will use sd_notify to signal when the container is ready, so that you can order units after container@foo.service and have that mean the right thing | 10:24:37 |
| ElvishJerricco | or systemctl status container@foo.service shows you the unit hierarchy of the container | 10:24:51 |
 @lotte:chir.rs | In reply to @elvishjerricco:matrix.org
do other container systems integrate as nicely with systemd as nspawn does? e.g. nspawn will use sd_notify to signal when the container is ready, so that you can order units after container@foo.service and have that mean the right thing OH | 10:25:14 |
| @lotte:chir.rs | i was confused on that front | 10:25:29 |
| @lotte:chir.rs | i was wondering how to depend on container@postgres.service and actually have another service/container start when postgres is ready? | 10:25:57 |
| magic_rb | In reply to @elvishjerricco:matrix.org
do other container systems integrate as nicely with systemd as nspawn does? e.g. nspawn will use sd_notify to signal when the container is ready, so that you can order units after container@foo.service and have that mean the right thing Not really i guess, but its not impossible to get working. You can use SDNOTIFY the socket from within the container to signal ready when you reach multi-user.target manually | 10:26:13 |
