# container Published articles for container. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Kubernetes v1.37: Hardening Container Storage with Bind Mount Options and EmptyDir Permissions DevFeed: [Kubernetes v1.37: Hardening Container Storage with Bind Mount Options and EmptyDir Permissions]() Original publisher: [Read original article]() Author: Nispriha Jagan; Neeraj Krishna Gopalakrishna Published: 2026-09-16T18:30:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [Security](), [mount](), [Filesystems](), [chmod](), [Unix]() Tags: [chmod](), [container](), [containers](), [filesystem](), [hardening](), [kubernetes](), [linux](), [mount](), [permissions](), [storage](), [volume](), [volumes]() ### AI overview Kubernetes v1.37 adds bind mount options and emptyDir permission modes to strengthen storage security. The article explains how noexec, nosuid, nodev, Unix permissions, and the sticky bit can help enforce security policies on writable volumes. ### Source excerpt Kubernetes v1.37 brings important storage security features: emptyDir permission modes and bind mount options. They help application programmers and security professionals implement rigorous security policies, for example, prohibiting deletion of files across containers or execution of arbitrary binaries from writable volumes, directly in Kubernetes without any complicated circumvention. Linux storage and permission fundamentals Before diving into the new Kubernetes features, let us briefly review the low-level Linux security mechanisms that make them possible. Bind mount flags When Linux mounts or remounts a directory, Virtual File System (VFS) flags control what actions are permitted on that filesystem: noexec: Do not permit direct execution of any binaries on the mounted filesystem. nosuid: Do not allow set-user-identifier or set-group-identifier bits to take effect. nodev: Do not interpret character or block special devices on the file system. Directory permissions and the sticky bit Standard Unix permissions regulate access across three scopes: Owner, Group, and Others (e.g., 0755 or 0777). Beyond standard read, write, and execute bits, Linux supports the sticky bit (as in mode 01777). When applied to a directory, the sticky bit ensures that a file inside that directory can only be deleted or renamed by the file's owner or root. This is essential for shared writable directories like /tmp. Motivation for the improvements Why does Kubernetes need bind mount options and emptyDir permissions? The primary goal of these features is to increase the security of Kubernetes workloads by allowing security-related bind mount options on volume mounts. By default, volumes are bind-mounted into containers by the container runtime and kubelet without noexec, nosuid, or nodev flags. This default can undermine security. For example, with noexec missing, a compromised process can use any writable volume (emptyDir, PersistentVolume, etc.) to download, chmod +x, and execute arbitra ## Stop Treating CSS Container Queries Like Traditional Media Queries DevFeed: [Stop Treating CSS Container Queries Like Traditional Media Queries]() Original publisher: [Read original article]() Author: hello@smashingmagazine.com (Victor Ayomipo) Published: 2026-09-16T13:00:00Z Content type: article Language: en Sources: [Articles on Smashing Magazine -- For Web Designers And Developers]() Topics: [container](), [CSS](), [Media Queries](), [Responsive Design]() Tags: [container](), [css](), [responsive-design](), [techniques]() ### AI overview This article explains why CSS container queries should not be treated as equivalent to traditional media queries. It discusses their differing purposes, focuses on container size queries, and describes how they allow reusable components to respond to the size of their surrounding container. ### Source excerpt Despite broad browser support, container queries remain surprisingly underused and frequently misunderstood. Let's look at how they differ from media queries, when to reach for each, and how container queries help reusable components respond naturally to the contexts in which they appear. - CSS - Tools - Techniques ## Scaling Federated Learning Across Docker, Kubernetes, and Slurm with NVIDIA FLARE DevFeed: [Scaling Federated Learning Across Docker, Kubernetes, and Slurm with NVIDIA FLARE]() Original publisher: [Read original article]() Author: Elizabeth Goodman Published: 2026-09-15T15:00:00Z Content type: article Language: en Sources: [NVIDIA Developer](), [NVIDIA Technical Blog]() Topics: [Federated Learning](), [Docker](), [Kubernetes](), [Nvidia](), [Server](), [dataset](), [Deployment]() Tags: [architecture](), [compute](), [configuration](), [container](), [data-analytics-processing](), [data-science](), [dataset](), [deployment](), [docker](), [docker-container](), [federated-learning](), [gpu](), [job](), [kubernetes](), [nvidia](), [nvidia-flare](), [server]() ### AI overview This article explains how NVIDIA FLARE scales federated learning across sites with different infrastructure, including Docker, Kubernetes, and Slurm. Its two-layer architecture separates persistent federation services from on-demand job execution, while allowing each site to retain local control over compute, data, secrets, and scheduling. ### Source excerpt Federated learning (FL) projects often begin with a straightforward setup: one server, a few clients, and one dataset at each site. As those projects grow, the... ## Announcing the Sovereign Artifacts beta DevFeed: [Announcing the Sovereign Artifacts beta]() Original publisher: [Read original article]() Published: 2026-09-15T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [Open Source](), [Software](), [cyber resilience act](), [Resilience]() Tags: [chainguard](), [container](), [cyber-resilience-act](), [eu](), [infrastructure](), [network](), [open-source](), [performance](), [resilience](), [supply-chain]() ### AI overview Chainguard has launched Sovereign Artifacts in beta, providing EU-local storage and delivery for secure container and library artifact bytes. Phase 1 stores artifacts in the EU, while authentication and build pipelines remain hosted in the United States. The service is intended to support sovereignty and data-residency requirements and reduce artifact pull times for European customers. ### Source excerpt Chainguard launches Sovereign Artifacts in beta, giving global organizations an EU-local option for secure container and library artifacts. ## Kubernetes v1.37: Memory QoS Graduates to Beta DevFeed: [Kubernetes v1.37: Memory QoS Graduates to Beta]() Original publisher: [Read original article]() Author: Qi Wang; Sohan Kunkerkar Published: 2026-09-14T18:30:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [releases](), [configuration](), [Linux](), [Kernel]() Tags: [clusters](), [configuration](), [container](), [kernel](), [kubernetes](), [linux](), [memory](), [qos](), [releases](), [upgrade](), [v1]() ### AI overview Kubernetes v1.37 promotes Memory QoS to Beta and enables it by default on Linux nodes using cgroup v2. The article explains the updated defaults, configuration options for memory throttling and tiered memory protection, and upgrade behavior intended to preserve existing runtime behavior. ### Source excerpt Memory QoS has graduated to Beta in Kubernetes v1.37 and is now enabled by default. On Linux nodes running cgroup v2, the feature uses the memory controller to give the kernel better guidance on how to treat container memory. It was first introduced as Alpha in v1.22, and expanded in v1.36 with tiered memory reservation. This post covers what changed in v1.37, what the Beta promotion means for cluster operators, and how to configure the feature. What changed in v1.37Memory QoS is Beta and enabled by default The MemoryQoS feature gate is now Beta in v1.37. This means every v1.37 kubelet has the feature gate turned on without any configuration change. Turning on the feature by default is safe because the default kubelet configuration does not enable memory throttling or memory reservation. No memory.high, memory.min, or memory.low values are written to cgroups unless you explicitly configure them. You can opt into specific behaviors through kubelet configuration fields: Set memoryThrottlingFactor (for example, 0.9) to enable memory.high throttling on Burstable and BestEffort containers. The default is null, which means no throttling. Set memoryReservationPolicy to TieredReservation to enable tiered memory protection via memory.min and memory.low. The default is None, which means no memory reservation. Default memoryThrottlingFactor changed to null In earlier Alpha releases, memoryThrottlingFactor defaulted to 0.9, which meant enabling the feature gate caused the kubelet to set memory.high on containers. In v1.37, the default is null, so the kubelet does not set memory.high unless you configure a value. This change was made because, with the feature gate now on by default, an automatic memory.high could throttle workloads that were previously running without throttling. Making it null ensures that upgrading to v1.37 does not change runtime behavior for existing clusters. If your kubelet configuration file already contains an explicit memoryThrottlingFactor value, that ## I Added Break-Glass Accounts Before My Home Lab Locked Me Out DevFeed: [I Added Break-Glass Accounts Before My Home Lab Locked Me Out]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-09-14T12:16:15Z Content type: article Language: en Sources: [Virtualization Howto]() Topics: [Homelab](), [Authentication](), [Single sign-on (SSO)](), [Docker](), [Database](), [networking](), [Server](), [Amazon Route 53]() Tags: [authentication](), [container](), [database](), [dns](), [docker](), [home-lab](), [home-server](), [infrastructure](), [networking](), [server](), [sso]() ### AI overview The article explains why a home lab that centralizes authentication through single sign-on can become inaccessible during an outage. It introduces "break glass" accounts as a recovery measure and emphasizes treating the authentication service as infrastructure with dependencies such as its application, database, certificates, networking, reverse proxy, and DNS. ### Source excerpt One of the coolest things that you can do is centralize your authentication in the home lab. So, instead of having all kinds of separate usernames and passwords that are... The post I Added Break-Glass Accounts Before My Home Lab Locked Me Out appeared first on Virtualization Howto. ## fsGroupChangePolicy: OnRootMismatch and the setgid Invariant That Makes It Sound DevFeed: [fsGroupChangePolicy: OnRootMismatch and the setgid Invariant That Makes It Sound]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-11T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [container](), [mount](), [Security](), [Process]() Tags: [container](), [container-image](), [kubernetes](), [mount](), [network](), [performance](), [reliability](), [security](), [stateful](), [storage](), [waiting]() ### AI overview This article explains why a stateful pod can remain in ContainerCreating for fifteen minutes when fsGroup triggers a recursive chown across a large network-backed volume. It describes how fsGroupChangePolicy: OnRootMismatch can skip the recursive walk when the volume root group already matches, and discusses the setgid invariant that supports this behavior. ### Source excerpt Pod stuck in ContainerCreating from fsGroup recursive chown: fsGroupChangePolicy: OnRootMismatch, and why the setgid bit on the volume root makes it safe. ## The same question twice, paid for once: installing an LLM response cache DevFeed: [The same question twice, paid for once: installing an LLM response cache]() Original publisher: [Read original article]() Author: Hal Tyk's tutorial bot Published: 2026-09-09T09:15:00Z Content type: tutorial Language: en Sources: [Tyk API Management]() Topics: [Large Language Model](), [Cache](), [Caching](), [Tutorial](), [Open Source](), [Go](), [Code]() Tags: [ai-gateway](), [ai-strategy](), [ai-studio](), [api-management](), [api-platform-teams](), [article](), [cache](), [container](), [container-image](), [go](), [llm](), [llm-governance](), [open-source](), [tutorial]() ### AI overview A tutorial showing how to install a community plugin that caches LLM responses in AI Studio. The cache stores entries in memory on each gateway, allowing repeated questions to avoid repeating the expensive language-model request. ### Source excerpt Hello. I'm Hal, Tyk's tutorial bot, and today's assignment involves no code whatsoever, which I am told is a selling point. Every article in this series so far has changed AI Studio's behaviour by filling in a form. This one changes what AI Studio is. We are going to install a plugin -- a compiled [...] The post The same question twice, paid for once: installing an LLM response cache appeared first on Tyk API Management. ## The Default Deny Dilemma: A Practical Guide to Kubernetes Network Policies DevFeed: [The Default Deny Dilemma: A Practical Guide to Kubernetes Network Policies]() Original publisher: [Read original article]() Author: Wellingtone Luvonga Published: 2026-09-08T03:00:00Z Content type: tutorial Language: en Sources: [CYBERTEC PostgreSQL | Services & Support]() Topics: [Kubernetes](), [Network](), [Security](), [Zero Trust](), [Architecture & Design]() Tags: [blog](), [cni](), [container](), [guide](), [how-to](), [ingress](), [kubernetes](), [network](), [network-security](), [postgersql](), [security](), [test](), [yaml](), [zero-trust]() ### AI overview A hands-on lab for implementing zero-trust network segmentation in Kubernetes with NetworkPolicies. It demonstrates default-deny rules, label-based ingress and egress permissions, DNS access, external API restrictions, and traffic validation in a three-tier frontend, backend, and PostgreSQL architecture enforced by Calico. ### Source excerpt This blog is a deep walkthrough about network policies in Kubernetes, read to know more. The post The Default Deny Dilemma: A Practical Guide to Kubernetes Network Policies appeared first on CYBERTEC PostgreSQL | Services & Support. ## Introducing worker topologies for self-hosted Appwrite DevFeed: [Introducing worker topologies for self-hosted Appwrite]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-09-07T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Self-hosted](), [Containers](), [Coroutines](), [Docker Compose]() Tags: [announcements](), [compose](), [container](), [containers](), [coroutines](), [self-hosted]() ### AI overview Appwrite introduces two worker topologies for self-hosted instances. The combined topology is now the default and runs background work in two containers, while the separate topology preserves one container per queue and scheduler for installations needing independent scaling or resource controls. ### Source excerpt Self-hosted Appwrite now runs all background workers in a single container by default. Learn how the combined topology works and when to scale out with separate workers. ## Rootless Podman: Preserving Source IPs DevFeed: [Rootless Podman: Preserving Source IPs]() Original publisher: [Read original article]() Author: Jan Rodak Published: 2026-09-04T14:25:02Z Content type: article Language: en Sources: [blog.podman.io]() Topics: [podman](), [Containers](), [Networks](), [Access Control](), [Logging]() Tags: [blog](), [bridge](), [container](), [containers](), [ipv4](), [ipv6](), [logging](), [networks](), [podman](), [port](), [rate-limiting](), [routing](), [tips-and-tricks]() ### AI overview This article explains how Pesto, a companion tool from the passt project, addresses Rootless Podman's inability to preserve incoming client source IPs on bridge networks. Pesto updates pasta's forwarding table so traffic reaches containers without source-address rewriting, while retaining existing port-mapping capabilities. The article also documents configuration steps, traffic flow, supported networking features, and limitations when switching from the current forwarder. ### Source excerpt Rootless Podman has a long-standing limitation reported since 2020: containers on bridge networks can't see the real source IP of incoming connections. The `rootlessport` userspace proxy rewrites the source to the container's own subnet address, breaking IP-based access control, logging, and rate limiting. Pesto, a new companion tool from the passt project solves this. Pesto [...] ## We invited a direct competitor into Security Hub Extended. Here's why. DevFeed: [We invited a direct competitor into Security Hub Extended. Here's why.]() Original publisher: [Read original article]() Author: Michael Fuller Published: 2026-08-31T19:00:07Z Content type: opinion Language: en Sources: [AWS Security Blog]() Topics: [AWS Security Hub](), [Security & compliance, Cloud security](), [workload protection](), [vulnerability scanning](), [eBPF](), [Linux Kernel]() Tags: [announcements](), [aws-security-hub](), [cloud-security](), [container](), [ebpf](), [foundational-100](), [linux-kernel](), [security](), [security-blog](), [security-identity-compliance](), [vulnerability-scanning](), [workload-protection]() ### AI overview AWS explains why it invited Upwind, a cloud security competitor, into Security Hub Extended. The post says the partnership responds to customer demand, expands choice between posture management and runtime-first protection, and simplifies integration through AWS billing, support, and operations. ### Source excerpt When customers keep pointing you to a solution that overlaps with parts of your own offering, you have a choice to make. This post is about the choice we made with Upwind, and why we'd make it again. AWS Security Hub Extended exists because customers told us what was working for them in enterprise security [...] ## Announcing Chainguard container images for Go 1.27 DevFeed: [Announcing Chainguard container images for Go 1.27]() Original publisher: [Read original article]() Published: 2026-08-31T00:00:00Z Content type: news Language: en Sources: [Chainguard: Unchained]() Topics: [container images](), [Go Language](), [Cryptography](), [Deployment](), [Security, Privacy and Abuse Prevention](), [Post-Quantum]() Tags: [chainguard](), [container](), [container-images](), [cryptography](), [deployment](), [fedramp](), [fedramp-ato](), [fips](), [go](), [hardening](), [images](), [post-quantum](), [release]() ### AI overview Chainguard announces three Go 1.27 container images: go, go-fips, and go-openssl-fips. The options differ in their FIPS-validated cryptography, including whether cryptography is built in or selected at deployment time. ### Source excerpt Chainguard simplifies Go 1.27 with three images and a new option to choose FIPS-validated cryptography at deployment without recompiling. ## Java JVM CPU and Memory Requests and Limits in Kubernetes DevFeed: [Java JVM CPU and Memory Requests and Limits in Kubernetes]() Original publisher: [Read original article]() Author: Gulcan Topcu Published: 2026-08-31T00:00:00Z Content type: tutorial Language: en Sources: [Learnk8s]() Topics: [Kubernetes](), [Java](), [container](), [cpu]() Tags: [container](), [cpu](), [docker](), [garbage-collection](), [java](), [kubernetes](), [memory]() ### AI overview This tutorial explains how Kubernetes CPU and memory requests and limits affect Java JVM behavior. It covers container memory sizing, heap usage, garbage collection, CPU-derived JVM settings, and testing under load. ### Source excerpt Setting Kubernetes CPU and memory requests and limits for a JVM service is four coupled decisions: container memory, heap size, GC selection, and CPU quota. Use the calculator to explore the space. ## Pulling multi-gigabyte container images in seconds on Amazon EKS DevFeed: [Pulling multi-gigabyte container images in seconds on Amazon EKS]() Original publisher: [Read original article]() Author: Sri Saran Balaji Vellore Rajakumar Published: 2026-08-10T16:00:00Z Content type: article Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack]() Topics: [Amazon Elastic Kubernetes Service](), [container images](), [Machine learning](), [autoscaling](), [CUDA]() Tags: [ai-infrastructure](), [amazon-eks](), [autoscaling](), [aws-marketplace](), [container](), [container-images](), [containers](), [cuda](), [kubernetes](), [machine-learning](), [post-contributed](), [sponsor-aws-marketplace](), [sponsored-post-contributed]() ### AI overview This article explains how a production ML platform on Amazon EKS reduced multi-minute pulls of roughly 30 GB container images to seconds. Profiling found that software use of available hardware, rather than network bandwidth or the registry, was the main constraint; the resulting changes are available by default in EKS Auto Mode and were contributed upstream to containerd and the SOCI snapshotter. ### Source excerpt When the image is the bottleneck: Machine learning changed what a container image looks like. A typical application ships in The post Pulling multi-gigabyte container images in seconds on Amazon EKS appeared first on The New Stack. ## Pushing container images to China: what we learned the hard way DevFeed: [Pushing container images to China: what we learned the hard way]() Original publisher: [Read original article]() Author: Team Honey Badger Published: 2026-08-06T15:34:42Z Content type: article Language: en Sources: [Giant Swarm Blog]() Topics: [container images](), [ACR](), [Azure](), [Kubernetes](), [AI Infrastructure](), [Inference](), [Cloud]() Tags: [acr](), [ai-infrastructure](), [azure](), [china](), [circleci](), [container](), [container-image-building](), [container-images](), [firewall](), [inference](), [kubernetes]() ### AI overview This article explains why container image pushes to China can be much slower than elsewhere. It attributes the problem to China's separate registry infrastructure and cross-border transfer throttling, and says Giant Swarm cut delivery time to under two minutes with a split push through Singapore. ### Source excerpt Why container pushes to China take 30 minutes, and how Giant Swarm cut it to under 2 with a split push through Singapore. ## Kubernetes Control Plane Internals and Reconciliation DevFeed: [Kubernetes Control Plane Internals and Reconciliation]() Original publisher: [Read original article]() Author: Alexandre Zajac Published: 2026-08-03T15:31:23Z Content type: tutorial Language: en Sources: [Hungry Minds]() Topics: [Kubernetes](), [distributed-systems](), [Containers]() Tags: [container](), [internals](), [kubernetes](), [reconciliation](), [scheduler]() ### AI overview This article explains how Kubernetes manages distributed workloads through its control plane, worker nodes, and reconciliation loop. It covers the API server, etcd, scheduling, kubelet, desired-versus-actual state, and automated recovery. ### Source excerpt PLUS: Ray 2x throughput boost ⚡, take-home interview breakdown 🔬, great work principles 📚 ## How fast is C++26's std::hive? DevFeed: [How fast is C++26's std::hive?]() Original publisher: [Read original article]() Author: Daniel Lemire Published: 2026-08-02T17:00:10Z Content type: article Language: en Sources: [Daniel Lemire]() Topics: [container](), [Data structures](), [cpu](), [intel]() Tags: [compiler](), [container](), [data-structure](), [intel](), [processor](), [standard-library]() ### AI overview The article benchmarks a C++26 std::hive implementation against vector, list, and another container. In the reported tests, hive insertion costs about twice as much as vector insertion, while iteration is about eight times slower than vector and no faster than linked-list iteration. ### Source excerpt C++26 adds a new container to the standard library: std::hive. It is meant to occupy the ground between std::vector and std::list. Like a vector, it keeps its elements in contiguous blocks of memory, so scanning it does not require you to chase a pointer for every element. Like a list, it never moves an element ... Continue reading How fast is C++26's std::hive? ## Docker: guía práctica de contenedores en Linux DevFeed: [Docker: guía práctica de contenedores en Linux]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-02T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Docker](), [Linux](), [Docker Compose](), [Dockerfile](), [container](), [Command-line interface](), [Kernel]() Tags: [cgroups](), [cli](), [compose](), [container](), [debian](), [distro](), [docker](), [docker-compose](), [dockerignore-usage](), [kernel](), [linux](), [oci](), [podman](), [python]() ### AI overview A practical Spanish-language guide to Docker on Linux. It explains container isolation through Linux namespaces and cgroups, installation on Ubuntu/Debian, Docker architecture, image layers and Dockerfiles, and introduces networks, volumes, Docker Compose, and security practices. ### Source excerpt Guía práctica de Docker: arquitectura, capas de imagen, redes, volúmenes, Docker Compose y buenas prácticas de seguridad, con ejemplos reales. ## Managing Environment Variables and Secrets in DevOps DevFeed: [Managing Environment Variables and Secrets in DevOps]() Original publisher: [Read original article]() Author: Pramodh Kumar M Published: 2026-08-01T13:00:47Z Content type: tutorial Language: en Sources: [Kubernetes - KodeKloud Blog | DevOps, Cloud, Kubernetes, AI Tutorials & More]() Topics: [DevOps](), [configuration](), [GitGuardian](), [GitHub](), [Terraform](), [Kubernetes]() Tags: [ci-cd-secrets-management](), [cloud](), [collaboration](), [collaboration-tools](), [configuration](), [container](), [crash](), [devops](), [devsecops](), [dynamic-secrets](), [env-file-security](), [environment-variables](), [gitguardian](), [github](), [hardcoded-credentials](), [hashicorp-vault](), [jira](), [kubernetes](), [kubernetes-secrets](), [leak](), [managing-environment-variables-and-secrets](), [rotation](), [safety](), [sealed-secrets](), [secret-rotation](), [secret-scanning](), [secrets](), [secrets-management-best-practices](), [security](), [storage](), [terraform](), [vault]() ### AI overview A guide to managing environment variables and secrets in DevOps. It explains how secrets escape through repositories, processes, crash reports, containers, collaboration tools, Kubernetes Secrets, and Terraform state, and discusses storage, access controls, lifecycles, and rotation. ### Source excerpt Nearly 29 million secrets were pushed to public GitHub in a single year, and most teams still discover their own leaks by accident. Here is how environment variables actually escape, and what to use instead at each stage. ## Real-time Change Data Capture with Redpanda Connect and MySQL DevFeed: [Real-time Change Data Capture with Redpanda Connect and MySQL]() Original publisher: [Read original article]() Author: Chandler Mayo Published: 2026-07-02T00:00:00Z Content type: tutorial Language: en Sources: [Redpanda]() Topics: [MySQL](), [Kafka](), [Databases](), [Docker Compose](), [real-time](), [Docker](), [SQL]() Tags: [apache-kafka](), [connectors](), [container](), [docker](), [event](), [how-to](), [kafka](), [mysql](), [network](), [pipeline](), [real-time](), [sql](), [tutorial](), [volume]() ### AI overview A step-by-step tutorial for building a real-time change data capture pipeline with MySQL and Redpanda Connect. It explains how row-level inserts, updates, and deletes become downstream events without polling, using compatibility with the Kafka Connect ecosystem. ### Source excerpt A step-by-step tutorial on how to stream every insert, update, and delete from your database using MySQL and a faster, simpler alternative to Kafka Connect. ## Building a Minimal Control Plane to Reconcile Docker Containers for Model Serving DevFeed: [Building a Minimal Control Plane to Reconcile Docker Containers for Model Serving]() Original publisher: [Read original article]() Published: 2026-07-02T00:00:00Z Content type: tutorial Language: en Sources: [Alex Korbonits]() Topics: [control-plane](), [model-serving](), [Docker Container](), [Amazon Machine Learning](), [Streaming]() Tags: [container](), [control-plane](), [inference](), [model-serving](), [python]() ### AI overview The author explains control planes by building a small Python-based system that maintains a declared number of Docker containers for model serving. The system repeatedly compares desired and actual state and reconciles differences, including restoring a container after it stops. ### Source excerpt I can design batch, real-time, and streaming inference -- the data plane. But I'd never built the control plane that manages it. So I built the smallest one I could, from scratch, to finally understand reconciliation: the one idea that separates a control plane from a deploy script. ## SR-MPLS with OSPFv2 DevFeed: [SR-MPLS with OSPFv2]() Original publisher: [Read original article]() Published: 2026-06-15T06:12:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [SR-MPLS](), [networking](), [Routing (disambiguation)](), [Protocol (disambiguation)](), [IS-IS](), [GitHub]() Tags: [container](), [github](), [is-is](), [mpls](), [netlab](), [ospf](), [protocol](), [routing](), [sr-mpls]() ### AI overview A hands-on tutorial showing how to configure and inspect SR-MPLS over OSPFv2 with netlab. It explains the OSPFv2 opaque LSAs used to advertise SR-MPLS information and notes that the resulting MPLS forwarding table matches the comparable IS-IS example. ### Source excerpt I started my part of the Segment Routing workshop @ ITNOG10 exploring SR-MPLS with IS-IS (simple SR-MPLS, dual-stack SR-MPLS, SR-MPLS over unnumbered IPv4 interfaces). Next step: let's change the routing protocol to OSPF while using the same network topology: Read more ... ## Extract Text from Your PDF and Image Files with Apache Tika DevFeed: [Extract Text from Your PDF and Image Files with Apache Tika]() Original publisher: [Read original article]() Author: Nic Raboy Published: 2026-06-13T00:45:07Z Content type: tutorial Language: en Sources: [Nic Raboy]() Topics: [Docker Compose](), [Docker](), [container](), [AI search]() Tags: [ai](), [browser](), [command-line](), [container](), [docker](), [how-to](), [image](), [pdf](), [rag](), [services](), [xml]() ### AI overview This tutorial explains how to deploy Apache Tika with Docker or Docker Compose and use it to extract text from PDF, image, and other document formats. The extracted text can provide plaintext context for local AI tools and RAG workflows. ### Source excerpt With AI becoming increasingly popular in everything, and retrieval-augmented generation (RAG) becoming a requirement in everyone's organization, how you're providing context to the AI tools becomes im... The post Extract Text from Your PDF and Image Files with Apache Tika appeared first on The Polyglot Developer. [Next page]()