BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.all-systems-go.io//BBTJSF
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-all-systems-go-2025-BBTJSF@cfp.all-systems-go.io
DTSTART;TZID=CET:20250930T164500
DTEND;TZID=CET:20250930T171000
DESCRIPTION:At Meta\, we've been looking to revamp our internal container r
 untime (Twine). Instead of maintaining all the low level container runtime
  code ourselves\, we'd much prefer having more of this managed by systemd.
  This talk will go over what we did to make systemd transient units a suit
 able environment for running system containers (pid namespace support\, cg
 roup namespace support\, namespace delegation\, ...)\, and why we went thi
 s route instead of reusing systemd-nspawn.
DTSTAMP:20261013T215119Z
LOCATION:Loft
SUMMARY:A new systemd container runtime?! - Daan De Meyer
URL:https://cfp.all-systems-go.io/all-systems-go-2025/talk/BBTJSF/
END:VEVENT
END:VCALENDAR