BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.gulas.ch//gpn24//talk//8SDDSH
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-gpn24-8SDDSH@cfp.gulas.ch
DTSTART;TZID=CET:20260607T134500
DTEND;TZID=CET:20260607T140500
DESCRIPTION:Developing an OCI image pull through cache for Forgejo had some
  interesting rabbit holes and it was surprisingly hard to get in depth inf
 ormation on a supposedly well known system. So I got to deep dive and do b
 its of research and reverse engineering to make the parts communicate prop
 erly.\n\nIn this talk I'll share my insights into the process of pulling O
 CI images according to the distribution spec (and its slight deviations) a
 nd try to answer questions like:\n	- Which requests are sent by Podman or 
 the Docker daemon when doing `docker pull image`?\n		- Whats that with the
  /v2 endpoint and discovery?\n		- How about authentication?\n	- What does 
 the pull sequence look like?\n       	- Help\, I got an index manifest\, w
 hat should I do?\n	- How should Forgejo communicate with the daemon for a 
 successful pull?\n\nIf there is time\, I'll also share small pieces of kno
 wledge of where the implementation sits in the Forgejo codebase and how it
  interacts with the existing package registry.
DTSTAMP:20260516T172640Z
LOCATION:ZKM Medientheater
SUMMARY:Popping podman/dockers bonnet: Unraveling the image pull process wh
 ile developing for Forgejo - Erik
URL:https://cfp.gulas.ch/gpn24/talk/8SDDSH/
END:VEVENT
END:VCALENDAR