Uploaded April 2024 | Updated September 2026, 2 weeks ago
- Many Docker users are integrating AI within containers, despite initial designs around CPU-centric architectures.
- Challenges include adapting Docker for GPU support and making AI accessible to newcomers without a data science background.
- Docker has introduced tools like the "gen AI stack" to help users learn and experiment with AI in Docker environments.
- Continuous efforts to improve documentation and provide ready-to-use AI templates on Docker Hub.
- Docker is working on standardizing access to various GPUs, overcoming limitations due to hardware shortages and high costs.
- Innovations like WebGPU to facilitate browser-GPU interactions and Web Assembly for secure, high-performance browser applications.
- Introduction of hybrid tools allowing cloud-based operations while maintaining local-like experiences, enhancing developer flexibility.
Watch a 360˚ view of this conversation youtu.be/r4KFx_fxJkQ
Other videos that go with this one: youtube.com/playlist?list=PLIzb4b2ejfFgIFpyqpfOLEblevhgXByA-
00:00 Docker & AI
02:31 Container Device Interface
05:43 Docker Build Cloud
09:21 Web Assembly & WASM
14:21 KubeCon Community
- Many Docker users are integrating AI within containers, despite initial designs around CPU-centric architectures.
- Challenges include adapting Docker for GPU support and making AI accessible to newcomers without a data science background.
- Docker has introduced tools like the "gen AI stack" to help users learn and experiment with AI in Docker environments.
- Continuous efforts to improve documentation and provide ready-to-use AI templates on Docker Hub.
- Docker is working on standardizing access to various GPUs, overcoming limitations due to hardware shortages and high costs.
- Innovations like WebGPU to facilitate browser-GPU interactions and Web Assembly for secure, high-performance browser applications.
- Introduction of hybrid tools allowing cloud-based operations while maintaining local-like experiences, enhancing developer flexibility.
Watch a 360˚ view of this conversation youtu.be/r4KFx_fxJkQ
Other videos that go with this one: youtube.com/playlist?list=PLIzb4b2ejfFgIFpyqpfOLEblevhgXByA-
00:00 Docker & AI
02:31 Container Device Interface
05:43 Docker Build Cloud
09:21 Web Assembly & WASM
14:21 KubeCon Community

![CDN PURGE with Elixir
https://makeitwork.tv 👈 full version shipping any week now
We implement the following one-liner bash script the Elixir Way™:
dig cdn-2025-02-25.internal AAAA +short | while read ipv6; do curl -so /dev/null -w %{http_code} %{method} %{url_effective}n -X PURGE http://[$ipv6]:9000/; done
Find the code and the conversation in this pull request 🐙 https://github.com/thechangelog/changelog.com/pull/549
🤔 THE PROBLEM: CDN is serving stale content, with some entries expired for over 4 minutes. We need a way to explicitly purge cache across all CDN instances rather than waiting for user requests to trigger refreshes.
🙇♂️ THE SOLUTION: DNS lookups to discover all instances and coordinate purges across them.
🧑🔧 THE DNS THING (02:26): Using Fly.ios internal DNS system, we implement IPv6 lookups to discover all CDN instances. Claude Code helps. It works the first time 🎉
🐞 BUGS & PREDATORS (3:00): Undefined function errors, mock testing issues, and the classic double-slash URL bug. No Claude Code, just experience.
🧐 DID IT WORK? (6:56): Lets force push straight into production and see what happens 😱
This session isnt just a tutorial - its an authentic look at collaborative coding, where DNS magic meets Elixir elegance to conquer distributed caching.
If youre into DevOps, CDNs, or just love seeing bugs squashed in real time, this gives you the tools to understand (and maybe implement) your own purge system.
00:00 The Problem
00:46 The Solution
02:26 The DNS thing
03:00 Bugs & Predators
04:43 Lets fire this up
06:56 Lets force push it
07:25 Is it working?
08:53 No no no CDN PURGE with Elixir](https://i.ytimg.com/vi/fhQd9XaZTr8/mqdefault.jpg)








