BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.devconf.info//devconf-cz-2025//speaker//CK7KTA
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-devconf-cz-2025-RKW3WM@pretalx.devconf.info
DTSTART;TZID=CET:20250613T131500
DTEND;TZID=CET:20250613T135000
DESCRIPTION:At the last Devconf.cz\, I demoed how one can "replace/reinstal
 l" a cloud instance with a bootc (bootable) container image. However\, thi
 s is just one option in the wider environment.\n\nIn this talk we'll first
  take a deeper technical dive for background into that perennial question 
 "How do I boot a container?". But more specifically we'll look at the broa
 der options for deploying a bootc container to a physical/virtual system (
 Anaconda\, bootc-image-builder\, bootc install to-existing-root\, or a fac
 tory reset).\n\nWe'll cover interesting details like static IP addressing 
 on bare metal\, best practices for secrets (outside of the container)\, an
 d also touch on the interesting topic of the larger question of system con
 figuration frontends (kickstart vs cloud-init vs blueprints vs Ignition) t
 hat all intersect with bootc still.
DTSTAMP:20260816T013346Z
LOCATION:E112 (capacity 156)
SUMMARY:System provisioning and bootc\, now and the future - Colin Walters
URL:https://pretalx.devconf.info/devconf-cz-2025/talk/RKW3WM/
END:VEVENT
END:VCALENDAR