| 22 Aug 2021 |
 andi- | Great. Systemd also doesn't bother not polluting /var/empty with its crap. | 19:33:24 |
 Finn Behrens (he/him) | toolbox looks interesting. trying it on my fedora 33 ARM64 vm | 19:39:32 |
| Finn Behrens (he/him) | well that does not work, guess because of architecture, but don't know enough podman to test it | 19:44:23 |
| Finn Behrens (he/him) | I have some questions: DEBU Entry point PID is a float64. Guess sleep is the best answer | 19:45:32 |
| andi- | Alright, pushed the latest verison of the v249 PR and triggered another hydra build. You should be able to switch your local systems to it in the morning (in ~9-12h) if you want to help with testing. | 20:53:03 |
| 23 Aug 2021 |
 gdamjan | perhaps slightly off-topic, but, does anyone have instructions to install nixos in a directory for systemd-nspawn | 13:07:39 |
| andi- | isn't that just nixos-install with a configuration that has boot.isContainer = true; set? | 13:14:49 |
| Finn Behrens (he/him) | In reply to @andi:kack.it
best case: systemd-nspawn -D $fedora32Directory --bind /dev/kvm $fedora32Directory/init Well, guess the manual written by Poettering was wrong:
execv(/persist/data/fedora-32/usr/lib/systemd/systemd) failed: No such file or directory
Container fedora-32 failed with error code 1.
| 14:42:52 |
| andi- | In reply to @kloenk:petabyte.dev
Well, guess the manual written by Poettering was wrong:
execv(/persist/data/fedora-32/usr/lib/systemd/systemd) failed: No such file or directory
Container fedora-32 failed with error code 1.
Try passing just /init instead of the full path. That path might be required within the environment | 14:46:45 |
| Finn Behrens (he/him) | good catch, thanks | 14:47:08 |
| Finn Behrens (he/him) | I now just have to get a password somehow | 14:47:17 |
| Finn Behrens (he/him) | oh, and how do I stop the container with a german (neo2) keyboard? xD | 14:47:58 |
| andi- | machinectl stop <tab> | 14:55:51 |
| Finn Behrens (he/him) | ah, i found systemctl poweroff -m fedora-32 | 14:56:07 |
| andi- | and you can also get a shell into the container via machinectl shell ... or machinectl login ... | 14:56:14 |
| Finn Behrens (he/him) | nice | 14:56:32 |
| Finn Behrens (he/him) | I guess I will now try to add a ssh server into the container, and then add socket activation for it | 14:57:03 |
| Finn Behrens (he/him) | Do you know if the finished auto poweroff for containers yet? | 14:57:22 |
| Finn Behrens (he/him) | andi-: should I use systemd.nspawn or systemd.services and use systemd-nspawn as ExecStart? Do you know what is best? | 15:16:53 |
| andi- | Depends on what for | 15:17:13 |
| andi- | You can also look at how the containers are usually defined | 15:17:27 |
| Finn Behrens (he/him) | where? | 15:17:35 |
| andi- | there is a containers.ini IIRC where you can define the entrypoint of a container. The default systemd-nspawn@.service can then be used to start those | 15:17:57 |
| Finn Behrens (he/him) | In the end I just want a containers that starts if i connect to it, that also has some lvm containers mounted inside | 15:17:57 |
| Finn Behrens (he/him) | * In the end I just want a containers that starts if i connect via ssh to it, that also has some lvm containers mounted inside | 15:18:31 |
| andi- | Then look into that | 15:19:12 |
| andi- | not sure how well those are accessible from nixos options | 15:19:22 |
| andi- | Perhaps worth looking there as well. | 15:19:27 |
| andi- | I never use nspawn outside of debugging systemd and then I use them manually. | 15:19:39 |
| Finn Behrens (he/him) | In reply to @andi:kack.it
Then look into that that means containers.ini? | 15:19:44 |
