Matthias Riße

@matrss
27 Followers
79 Following
314 Posts
Show threadMatthias Riße10h ago
@whitequark fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! WIP
Show threadMatthias RißeMay 28
@nobodyinperson actually, no. I didn't change anything with regard to that. I only know that Joey changed the push order to push the checked out branch first in https://git-annex.branchable.com/todo/Pushing_current_branch_before_synced__42___or_git-annex/, but I am sure you are aware of that given it was your issue 😄 But I have seen what you mean. I think it might just be a visual glitch.
Pushing current branch before synced* or git-annex

Show threadMatthias RißeApr 15

@mahlzahn @nobodyinperson filesystems already have some surprisingly restrictive limits (ext4 can only do 255 bytes long filenames), and apparently there is a sort-of hard limit on linux at 4096 bytes for paths. You can't `touch` an absolute path longer than 4096 bytes, but if you first cd into a part of that path and touch the same file with a relative path you can.

I guess git is applying those limits too?

Matthias RißeApr 15
ForgejoApr 15

The next major Forgejo release and LTS version (v15) is about to be released tomorrow, April 16.

Additionally, the Forgejo community invites all users to a release and upgrade party starting 16.00 UTC (18 CEST). It can be used to review the release cycle, exchange feedback and discuss future plans. Also, Admins are invited to perform upgrades of their instances during the meeting and get help from maintainers in case of any issues.

Audio + chat meeting on BigBlueButton: https://lecture.senfcall.de/ott-hqp-axg-yvm

Datenschutz

Matthias RißeApr 9
Do not do like me, do not wipe your root.
Matthias RißeApr 8
I am hacking on something stupid. Is it somehow possible with #podman / #crun to disregard the image's rootfs entirely and instead execute the entrypoint in the context of the host, without any isolation whatsoever? I am wrapping crun, so I can easily mess with the container bundle's config.json.
Show threadMatthias RißeApr 4
@Cs137 @ExtraFlauschig diesen Teil der Shownotes habe ich tatsächlich noch nie bewusst gelesen. Ich möchte den Podcast ja hören, nicht lesen. Die Themenauflistung im Untertitel reicht mir völlig, wenn ich überhaupt vorher schaue um was es geht. Ich glaube auch nicht, dass das KI generiert ist; dafür ist es zu knapp gefasst, für mich hat der Text einfach "Tim-Vibes". Die KI generierten Bilder gefallen mir dagegen gar nicht. Trotzdem finde ich den Podcast zu gut, um ihn deswegen zu deabonnieren.
Show threadMatthias RißeApr 2
@whitequark Instead I have hacked a bit on a crun wrapper that spawns an incus VM and executes inside of that (similar in concept to crun-vm and runcvm). I got it to launch a VM with podman run and run programs inside with podman exec. Next hurdle to get it to work for the Forgejo runner are mounts. I think I will explore that direction a bit more.
Show threadMatthias RißeApr 2

@whitequark I don't think I will spend more time with it, as I have no idea about containerd and firecracker and feel like I would just waste time with it.

To be fair, they explicitly say that the project is in a very early state.

Show threadMatthias RißeApr 2
@whitequark I tried it out but didn't get it to work. I followed both their "quickstart guide" and their "getting started guide" independently once. Building everything went fine, but for some reason the "devmapper snapshotter" setup produced an error on its first invocation (the second invocation didn't) and in the end trying to start a container with firecracker-ctr simply times out after a minute.