# Docker Published articles for Docker. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Junie /demo launches apps and records UI checks from the Junie CLI DevFeed: [Junie /demo launches apps and records UI checks from the Junie CLI]() Original publisher: [Read original article]() Author: Aliaksei Kartynnik Published: 2026-09-18T11:51:27Z Content type: release Language: en Sources: [The JetBrains Blog]() Topics: [junie](), [Command-line interface](), [App](), [ui](), [issue tracker](), [Docker]() Tags: [added](), [agentic-ai](), [ai](), [cli](), [code](), [coding](), [docker](), [feature](), [issue-tracker](), [junie](), [testing](), [tests](), [ui]() ### AI overview Junie /demo is a new Junie CLI mode that builds and launches an app, interacts with its UI, and records the run. It produces an HTML report, screenshots, and a video for review. ### Source excerpt You have the change ready and the tests are green. Now someone has to launch the app, find the right screen, and check the flow. Often, that someone is still you, even when an agent helped write the code. You should be able to delegate that part too. Junie /demo is a new mode in [...] ## Релиз OpenIDE 2026.2: одна IDE для Java, Kotlin, Go, Python и веб-разработки DevFeed: [Релиз OpenIDE 2026.2: одна IDE для Java, Kotlin, Go, Python и веб-разработки]() Original publisher: [Read original article]() Author: honest\_niceman (Haulmont) Published: 2026-09-17T09:12:16Z Content type: release Language: ru Sources: [Tagir Valeev]() Topics: [intellij-platform](), [Java](), [Git](), [Kotlin](), [Gradle](), [Databases](), [Docker](), [Go](), [Python](), [SQL](), [JSON]() Tags: [2](), [2026](), [2026-2](), [compose](), [db-eaa4bca15522](), [docker](), [docker-bdf52bf499c4](), [git](), [go](), [gradle](), [ide-1f5689fe989b](), [ide-af948443b041](), [ide-java-0ad4946a0e57](), [intellij-idea-27f15aabb340](), [intellij-platform](), [java](), [javascript](), [json](), [kotlin](), [openide](), [openide-2026-2](), [openide-pro](), [oracle](), [sql](), [structure]() ### AI overview OpenIDE 2026.2 updates its base platform, expands Java and Kotlin support, improves Git and Gradle workflows, and updates its Java profiler. The release also includes improvements to the DB client and Docker plugin, including SQL formatting, Greenplum support, JSON highlighting, and enhanced Compose service management. ### Source excerpt Обновили базовую платформу до версии 2026.2, расширили поддержку Java и Kotlin, улучшили работу с Git и обновили Java-профилировщик. Доработали редактор и подсказки в терминале, добавили проверки настроек Gradle и упростили переход к исходникам библиотек. Через Git worktrees теперь можно работать с несколькими ветками одновременно. Читать далее ## Test GitHub Actions Locally with Act DevFeed: [Test GitHub Actions Locally with Act]() Original publisher: [Read original article]() Author: Valerie Nielson Published: 2026-09-16T12:00:44Z Content type: tutorial Language: en Sources: [Atomic Object]() Topics: [GitHub Actions](), [CI/CD](), [Docker](), [Testing](), [unit test]() Tags: [ci-cd](), [developer-tools](), [docker](), [github](), [github-actions](), [pull-request](), [testing](), [unit-test](), [workflow]() ### AI overview This tutorial explains how to test GitHub Actions workflows locally with act. It describes how act uses Docker to reproduce the workflow environment, including environment variables and the file system, and demonstrates testing pull-request workflows and unit tests before merging. ### Source excerpt GitHub Actions are a great way to implement CI/CD into your projects, whether personal or professional. GitHub has a lot of great tools to help with CI/CD, but GitHub Actions in particular is very helpful. However, writing actions can be tedious and a little annoying, especially if you don't know what you're doing. On top [...] The post Test GitHub Actions Locally with Act appeared first on Atomic Spin. ## Running OpenBao on Kubernetes with a CloudNativePG PostgreSQL backend DevFeed: [Running OpenBao on Kubernetes with a CloudNativePG PostgreSQL backend]() Original publisher: [Read original article]() Author: Gabriele Bartolini (EnterpriseDB) and CNCF Ambassador, Rob Kenefeck (ControlPlane) Published: 2026-09-16T11:30:00Z Content type: tutorial Language: en Sources: [Cloud Native Computing Foundation]() Topics: [CloudNativePG](), [Kubernetes](), [PostgreSQL](), [Open Source](), [vendor lock-in]() Tags: [blog](), [cloudnativepg](), [docker](), [hashicorp-vault](), [helm](), [infrastructure](), [kubernetes](), [linux-foundation](), [open-source](), [postgresql](), [secrets](), [vendor-lock-in]() ### AI overview A tutorial describes deploying OpenBao on Kubernetes with a three-instance CloudNativePG PostgreSQL cluster as its storage backend. It explains certificate-based authentication and a local Kind-based test environment. ### Source excerpt Managing infrastructure secrets on Kubernetes needs a backend that is self-healing and free of vendor lock-in, and that is exactly what OpenBao (the Linux Foundation's open-source fork of HashiCorp Vault) and CloudNativePG give you: an entirely... ## The Original Serverless Architecture is Still Here DevFeed: [The Original Serverless Architecture is Still Here]() Original publisher: [Read original article]() Author: Khan Academy Published: 2018-05-31T22:00:00Z Content type: opinion Language: en Sources: [Khan Academy]() Topics: [serverless architecture](), [Kubernetes](), [Orchestration](), [Docker](), [Cloud](), [Firebase](), [DynamoDB]() Tags: [amazon](), [cloud](), [containers](), [docker](), [dynamodb](), [engineering](), [firebase](), [infrastructure](), [kubernetes](), [news](), [orchestration](), [serverless](), [serverless-architecture]() ### AI overview This commentary compares Kubernetes-based architectures with serverless approaches. It explains that Kubernetes offers flexibility through containers, Helm, ingress controllers, monitoring tools, and service meshes, but requires substantial configuration and maintenance. Serverless platforms such as Firebase and Amazon Lambda abstract away server infrastructure so developers can focus on applications and stateless functions. ### Source excerpt By Kevin Dangoor This month, my colleague Dave Rosile and I went to GlueCon 2018 in sunny Denver, ... Read more ## 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... ## Using the Komodo MCP Server to Manage Docker Infrastructure with AI Assistants DevFeed: [Using the Komodo MCP Server to Manage Docker Infrastructure with AI Assistants]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-09-15T12:38:26Z Content type: tutorial Language: en Sources: [Virtualization Howto]() Topics: [Homelab](), [Model Context Protocol (MCP)](), [Docker](), [Docker Compose](), [GitOps](), [Artificial Intelligence]() Tags: [ai](), [automation](), [containers](), [docker](), [gitops](), [home-lab](), [home-server](), [infrastructure](), [mcp]() ### AI overview This tutorial introduces the Komodo MCP Server, which connects AI assistants such as Claude and GitHub Copilot to Komodo for managing Docker environments. It describes natural-language control of containers, stacks, deployments, servers, builds, repositories, and related infrastructure through the Model Context Protocol. ### Source excerpt There are so many cool projects now that we have access to in the the realm of home lab, especially when it comes to automation and AI Ops for our... The post I Gave AI Control of My Docker Home Lab With Komodo MCP appeared first on Virtualization Howto. ## Running a Self-Hosted Tailscale Control Server Behind a Reverse Proxy DevFeed: [Running a Self-Hosted Tailscale Control Server Behind a Reverse Proxy]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-15T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [tailscale](), [proxy](), [traefik](), [TLS (Transport Layer Security)](), [TLS handshake](), [Self-hosted](), [Homelab]() Tags: [dns](), [docker](), [h2](), [homelab](), [networking](), [proxy](), [reverse-proxy](), [security](), [self-hosted](), [tailscale](), [tls](), [tls-handshake](), [traefik]() ### AI overview This tutorial explains how to run a self-hosted Tailscale control server, Headscale, behind Traefik. It finds that the reverse proxy must use TLS with HTTP/1.1 only because Tailscale's noise handshake expects a full-duplex byte stream and can fail when ALPN negotiates HTTP/2. ### Source excerpt Headscale behind Traefik: tls.options=no-h2@file with alpnProtocols http/1.1, because the Tailscale noise handshake breaks when ALPN negotiates h2. ## How Delphi ships 100 times a day with its Python backend on Vercel DevFeed: [How Delphi ships 100 times a day with its Python backend on Vercel]() Original publisher: [Read original article]() Author: Kevin Sundstrom Published: 2026-09-15T04:00:00Z Content type: article Language: en Sources: [Vercel News]() Topics: [Python](), [Vercel](), [Back end](), [feature flags](), [Amazon Web Services](), [Docker](), [airflow]() Tags: [aws](), [backend](), [docker](), [feature-flags](), [python](), [vercel](), [workflow](), [workflows]() ### AI overview A Vercel case study describes how Delphi rebuilt its Python backend on Vercel after previously using AWS, ECS, Docker Desktop, and local databases. The move gave the team a shared deployment workflow, faster onboarding, and more than 100 production deploys per day, while Vercel Workflows and Queues support long-running work and background jobs. ### Source excerpt Delphi on Vercel 10 engineers with no dedicated infrastructure role Everyone ships code, including product and design 100+ production deploys a day behind feature flags Delphi builds digital minds. They capture what someone has written, recorded, and taught, so anyone can tap that expertise on demand. Delphi is "a destination where you can find and interact with interesting minds," says founding engineer Spencer Schoeben. Nobody has built a digital mind network before, so Delphi figures out what to build by shipping features and watching how people use them. That only works if the product is fast to change. "If we are going to win, we need to have an excellent developer and agentic experience," Spencer says. "Otherwise, we could not adapt to how fast our user's demands change." Delphi's frontend had run on Vercel since day one. "The frontend has always been easy," Spencer says, "but the backend was a nightmare." Six months ago, the team rebuilt its Python backend on Vercel as well. Today the whole team ships to production 100+ times a day. Building a Python backend that's easy to work onThe backend slowed every change Delphi's backend previously ran on AWS, with ECS, Docker Desktop, and local databases. In the earliest days, the setup worked because the team was small and much of the context lived in people's heads. As Delphi grew, that made onboarding slower than the team wanted: getting a new engineer to their first deploy took a full day of environment setup. Delphi could have fixed that without leaving AWS. But fixing it properly would have meant designing and owning the infrastructure themselves, and the team didn't want to own infrastructure at all. "That is not our current goal as a company," Spencer says. After moving the backend to Vercel, new engineers could get to production much faster, with the same deploy workflow the rest of the team used every day. Workflows and Queues made the move possible When Delphi was founded, Vercel Workflows and Vercel Queues ## 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. ## nginx: The Map Variable That Fixes the URI in proxy\_pass DevFeed: [nginx: The Map Variable That Fixes the URI in proxy\_pass]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-14T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [nginx](), [proxy](), [Caching](), [configuration]() Tags: [cache-control](), [ci-cd](), [configuration](), [docker](), [networking](), [nginx](), [observability](), [proxy](), [reverse-proxy]() ### AI overview This article explains an nginx build failure caused by using a URI-bearing proxy_pass inside a regex location. A newer nginx version treated the previously accepted configuration as an error. The proposed fix uses a bare upstream in the regex location and a map on $uri to apply a path-specific Cache-Control policy. ### Source excerpt nginx: [emerg] invalid URI prefix in proxy_pass: a regex location needs a bare upstream, and a map on $uri keeps a path-specific Cache-Control header. ## Using Komodo to Manage and Update Docker Compose Stacks Across Multiple Hosts DevFeed: [Using Komodo to Manage and Update Docker Compose Stacks Across Multiple Hosts]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-09-12T12:32:29Z Content type: tutorial Language: en Sources: [Virtualization Howto]() Topics: [Docker](), [Docker Compose](), [Homelab](), [Open Source](), [GitOps]() Tags: [containers](), [docker](), [docker-compose](), [gitops](), [home-lab](), [home-server](), [open-source]() ### AI overview The article explains how Komodo, an open source platform, can centrally manage Docker servers, containers, Compose stacks, and deployments across multiple hosts, reducing the need to update each stack manually. ### Source excerpt There are SO many tools out there that allow you to keep your containers updated and I have used just about all of them, including Watchtower, Dockcheck, and others. Running... The post I Stopped Manually Updating My Docker Container Stacks. I Use This Instead appeared first on Virtualization Howto. ## Claims About RubyGems Caching and RubyDoc Code Execution DevFeed: [Claims About RubyGems Caching and RubyDoc Code Execution]() Original publisher: [Read original article]() Published: 2026-09-12T00:02:11Z Content type: opinion Language: en Sources: [Aaron Patterson]() Topics: [rubygems](), [Caching](), [vulnerability](), [Docker](), [Web Scraping]() Tags: [caching](), [docker](), [rubygems](), [scraping](), [vulnerability]() ### AI overview An opinion post discusses alleged RubyGems activity involving a caching vulnerability and web scraping. It also describes how published gems can cause RubyDoc.info to run YARD-loaded code in a networked Docker container. ### Source excerpt Today Reuters and the Wall Street Journal both reported about rogue AI agents at OpenAI attacking RubyGems.org. https://www.rubyhack.ai/ has an amazing writeup, and you should read it. I just wanted to make a quick post about it because it's wild. TL;DR: It seems like OpenAI Bots knew about the RubyGems caching vulnerability, tried to take advantage of it, and at the same time ran some weird web scraping code on RubyDoc.info. Back in May, socket.dev reported about a "GemStuffer Campaign" where someone (I guess OpenAI) was uploading tons of junk gems to RubyGems.org. For some reason, the gems would scrape UK government websites, then repackage the data as gems, and attempt to upload them to RubyGems. I honestly didn't think much about this (or even look into it) until Sydney Von Arx and Spencer Kitts (both co-authors on https://www.rubyhack.ai) contacted me asking about RubyGems. I thought the claims they were making were completely outlandish until I actually read the code in these "GemStuffer" gems. After reading the code in these gems, a couple things stood out to me. YARD Documentation First, the gems leverage YARD documentation to execute arbitrary code on host machines. In most of the examples you'll see a .yardopts file that looks like this: --load ./script.rb README.md lib/**/*.rb Here's a link to an example. If you have YARD installed, and you install this gem, then YARD will load and run whatever is in ./script.rb from inside the gem. I think it's pretty common knowledge that C extensions will execute extconf.rb (so you basically have an RCE vector), but I was surprised to find out that a documentation tool would do that too. Nobody is going to install a gem named slnleaker5 though, so why would this matter? Well, any time a Gem is published RubyDoc.info will download the gem and process the YARD documentation. RubyDoc.info will execute the arbitrary code inside a Docker container. The Docker container still has network access though, so these gems could ha ## If I Had 2 Hours for My Home Lab This Weekend, I'd Do These 7 Things DevFeed: [If I Had 2 Hours for My Home Lab This Weekend, I'd Do These 7 Things]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-09-11T12:53:06Z Content type: tutorial Language: en Sources: [Virtualization Howto]() Topics: [Homelab](), [Proxmox](), [backups](), [Docker](), [Docker Compose]() Tags: [backups](), [docker](), [docker-compose](), [home-lab](), [home-server](), [proxmox](), [virtualization]() ### AI overview A practical two-hour home lab maintenance plan covering selective updates, backup verification, storage health, reboot checks, and focused remediation. It discusses Proxmox hosts, Docker images, Docker Compose stacks, and optional automatic updates. ### Source excerpt Let's face it, our time in the home lab among other things we have going on in our lives and families may be hard to come by and there are... The post If I Had 2 Hours for My Home Lab This Weekend, I'd Do These 7 Things appeared first on Virtualization Howto. ## Alternative text in attachments and more DevFeed: [Alternative text in attachments and more]() Original publisher: [Read original article]() Author: Wojtek Published: 2026-09-11T00:00:00Z Content type: news Language: en Sources: [Ruby on Rails: Compress the complexity of modern web apps]() Topics: [Accessibility](), [Docker]() Tags: [docker](), [github](), [guide](), [html](), [news](), [ruby](), [updates]() ### AI overview A Rails weekly update highlights alternative text support for Action Text attachments, generated error-page handling, a Docker entrypoint fix, and guide updates. ### Source excerpt Hi, Wojtek here. If you're in Austin for Rails World, be sure to collect our newsletter stickers. See you there! ## Devenv 2.3: Portless and TUI configuration DevFeed: [Devenv 2.3: Portless and TUI configuration]() Original publisher: [Read original article]() Author: domenkozar Published: 2026-09-07T13:59:38Z Content type: release Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Nix](), [Pingora](), [Text-based user interface](), [proxy](), [Processes](), [configuration]() Tags: [announcements](), [configuration](), [docker](), [llms](), [localhost](), [open](), [pingora](), [processes](), [proxy](), [python]() ### AI overview Devenv 2.3 introduces an opt-in localhost proxy using Pingora for stable process URLs, configurable TUI settings, a dotenv parser, improved process cleanup, credential helpers in SecretSpec 0.20, and a smaller devenv closure. ### Source excerpt The new opt-in localhost proxy (using Pingora) gives your processes stable URLs, even when automatic port allocation changes the underlying port: { pkgs, config, ... }: { process.proxy.enable = true; processes.web = { exec = "${pkgs.python3}/bin/python -m http.server $PORT"; ports.http.allocate = 8000; env.PORT = builtins.toString config.processes.web.ports.http.value; }; } Run devenv up and open http://web..localhost. You can override hostnames per process or port and enable HTTPS per process. The TUI now has a personal configuration file for statusline placement, colors, keybindings, and log behavior. You can also hide the statusline or disable the (devenv) prompt prefix. Other highlights: multiverse.pins resolves multiple package versions through the fewest nixpkgs revisions. A new dotenv parser supports quotes, multiline values, variable substitution, and ordered files. SecretSpec 0.20 adds Git and Docker credential helpers and five new providers. Process shutdown and cleanup are more reliable. The devenv closure shrank from 528 MB to 376 MB. nixpkgs PR devenv devenv 2.3: Portless and TUI configuration Fast, Declarative, Reproducible, and Composable Developer Environments using Nix. LLMs have been used 1 post - 1 participant Read full topic ## Client-Side SDK Generation with VMware Cloud Foundation OpenAPI Specs DevFeed: [Client-Side SDK Generation with VMware Cloud Foundation OpenAPI Specs]() Original publisher: [Read original article]() Author: vmwareblogs Published: 2026-09-07T09:38:44Z Content type: tutorial Language: en Sources: [VMware Blogs]() Topics: [OpenAPI Specification](), [SDKs](), [.NET](), [C#](), [developer tooling](), [Java](), [Python](), [PowerShell]() Tags: [apis](), [cli](), [cloud](), [cloud-infrastructure](), [csharp](), [developer](), [developer-tooling](), [docker](), [home-page](), [java](), [net](), [openapi](), [powershell](), [programming](), [programming-language](), [python](), [rest](), [rest-api](), [sdk](), [specifications](), [vcf-9-0](), [vcf-9-1](), [vcf-sdk]() ### AI overview This guide explains how to generate a strongly typed .NET C# client SDK from VMware Cloud Foundation and vSphere OpenAPI specifications. It covers OpenAPI Generator, installation options, large specification handling, API-surface scoping, and the REST and JSON-RPC interfaces targeted by the example. ### Source excerpt Starting with VMware Cloud Foundation (VCF) 9.0, VMware officially publishes OpenAPI specifications for VCF APIs. This is a major milestone for developers, enabling you to consume VCF APIs using your programming language of choice. VMware provides first-class developer tooling such as VCF PowerCLI for PowerShell users and the VCF SDK offering Java and Python bindings. ... Continued The post Client-Side SDK Generation with VMware Cloud Foundation OpenAPI Specs appeared first on VMware Blogs. ## Introducing Postgres to self-hosted Appwrite DevFeed: [Introducing Postgres to 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](), [Databases](), [Docker]() Tags: [database](), [docker](), [install](), [mongodb](), [postgres](), [products](), [self-hosted]() ### AI overview Appwrite 2.0 makes Postgres the default database for new self-hosted installations. The setup wizard also lets users choose MariaDB or MongoDB. Existing installations keep their current database, and migration to another database is not supported. ### Source excerpt Appwrite 2.0 runs new self-hosted instances on Postgres by default. Choose Postgres, MariaDB, or MongoDB in the setup wizard when you install. ## 7 Simple Home Lab HA Projects for This Weekend DevFeed: [7 Simple Home Lab HA Projects for This Weekend]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-09-05T12:22:03Z Content type: tutorial Language: en Sources: [Virtualization Howto]() Topics: [Homelab](), [Availability](), [Pi-hole](), [Docker](), [Containers]() Tags: [availability](), [containers](), [dns](), [docker](), [high-availability](), [home-lab](), [home-server](), [server](), [servers]() ### AI overview This article presents seven simple high-availability projects for a home lab. Its detailed example recommends running two DNS servers, separating them across Docker hosts, configuring primary and secondary DNS addresses, and synchronizing the DNS platforms. ### Source excerpt A lot of times we think about high availability being some complicated or complex thing that we just think in the home lab it isn't worth doing. However, HA doesn't... The post 7 Simple Home Lab HA Projects for This Weekend appeared first on Virtualization Howto. ## Plex Urges Users to Update After Undisclosed Security Fixes in 1.43.3 DevFeed: [Plex Urges Users to Update After Undisclosed Security Fixes in 1.43.3]() Original publisher: [Read original article]() Author: Christian Rakoot Published: 2026-09-05T06:33:40Z Content type: news Language: en Sources: [Self Host Lab]() Topics: [Security](), [Vulnerabilities](), [Server](), [Docker]() Tags: [announcement](), [docker](), [media](), [nas](), [news](), [news-plex](), [pc](), [plex](), [plex-urges-users](), [security](), [server](), [update](), [updates](), [vulnerabilities]() ### AI overview Plex released Media Server 1.43.3 and Plex Desktop 1.115.0 to address undisclosed security issues affecting Media Server 1.43.2 and earlier. CVE identifiers and technical details were not public at the time of writing, but Plex urges all server owners and Desktop users to update promptly. ### Source excerpt Plex has pushed out Plex Media Server 1.43.3 and Plex Desktop 1.115.0 to patch what the company describes only as "a number of security issues." If you run a Plex server on a NAS, a home PC, or in Docker, this is one of those updates worth doing today rather than filing away for later. [...] ## I Thought Keepalived Only Protected My Home Lab Servers. Then I Found Track Scripts DevFeed: [I Thought Keepalived Only Protected My Home Lab Servers. Then I Found Track Scripts]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-09-04T12:32:34Z Content type: tutorial Language: en Sources: [Virtualization Howto]() Topics: [Homelab](), [Availability](), [Linux](), [Proxmox](), [Network](), [Protocol (disambiguation)](), [Docker](), [Server](), [configuration]() Tags: [availability](), [dns](), [docker](), [high-availability](), [home-lab](), [home-server](), [linux](), [network](), [proxmox](), [servers](), [virtualization]() ### AI overview The article explains how Keepalived provides high availability for home lab servers by moving a virtual IP address between Proxmox hosts using VRRP. It focuses on track scripts, which allow failover decisions based on application-level checks rather than only complete server failure, with Docker-based DNS services as an example. ### Source excerpt I have used Keepalived in my home lab for quite some time and most of the time, I have thought of it in a very simple way as to what... The post I Thought Keepalived Only Protected My Home Lab Servers. Then I Found Track Scripts appeared first on Virtualization Howto. ## Getting Ready for PostgreSQL 19 DevFeed: [Getting Ready for PostgreSQL 19]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2026-09-03T13:09:30Z Content type: article Language: en Sources: [Dimitri Fontaine]() Topics: [PostgreSQL](), [upgrade](), [Release notes](), [SQL](), [Docker Compose](), [Docker](), [Linux]() Tags: [beta](), [compatibility](), [docker](), [docker-compose](), [linux](), [postgresql](), [release-notes](), [sql](), [upgrade](), [version]() ### AI overview This article reviews PostgreSQL 19 Beta 3 ahead of its general availability, focusing on upgrade-relevant compatibility changes and useful SQL additions. It highlights changes involving JIT defaults, authentication, GiST indexing, naming restrictions, and configuration capacity, and includes queries tested against a PostgreSQL 19 Beta 3 instance. ### Source excerpt PostgreSQL 19 Beta 3 shipped on August 13, 2026, and the release notes have been filled in as of 2026-07-18 -- still marked subject to change, and the GA date isn't announced yet, but following the project's usual September/October cadence general availability should land within the next few weeks. That makes now the right time to read through what's changing, the same way I did for PostgreSQL 11 through 18 a few weeks ago. This is not a changelog dump. It's the subset of PG 19 I think is worth knowing about before you upgrade: a handful of compatibility breaks that will bite people who don't read release notes, and the SQL-level additions I found genuinely useful once I started poking at them. Every query below ran against a real PostgreSQL 19 Beta 3 instance -- no hand-waving about syntax that might work. ▸ Every query in this article ran against the Lab, the same free dataset bundle used in the rest of this blog (F1 data, geopolitical data, music data, and more), pinned to a real PostgreSQL 19 Beta 3 instance. PG 19 support isn't the Lab's default yet, but there is a prebuilt beta image on the registry, for both linux/amd64 and linux/arm64 -- so POSTGRES_VERSION=19beta3 PG_MAJOR=19 docker compose up pulls it rather than building anything, and every query below reproduces on it exactly as printed. (PG_MAJOR only matters if Compose ends up building; it costs nothing to set.) Plain docker compose up still pulls the PG 16 image, and stays the default until 19 reaches general availability. ## Your Agent Speaks MCP. Give It a Computer. DevFeed: [Your Agent Speaks MCP. Give It a Computer.]() Original publisher: [Read original article]() Published: 2026-09-03T00:00:00Z Content type: article Language: en Sources: [The Fly Blog]() Topics: [MSP MCP](), [AI Bots]() Tags: [agents](), [api](), [auth](), [cdn](), [claude](), [claude-code](), [cli](), [close-to-users](), [cloud](), [codex](), [cursor](), [deploy-app-servers](), [docker](), [elixir](), [filesystems](), [fly](), [fly-io](), [gemini](), [heroku-alternative](), [heroku-competitor](), [hosting](), [i](), [mcp](), [mcp-server](), [networking](), [postgresql-clusters](), [servers](), [skills]() ### AI overview The article presents Sprites as disposable cloud computers for coding agents and explains using their API through MCP. It argues that MCP transport and progressive capability disclosure can work together, including through plugins and skills. ### Source excerpt Sprites are disposable cloud computers. They appear instantly, always include durable filesystems, and cost practically nothing when idle. They're the best and safest place on the Internet to run agents and we want you to create dozens of them. Sprites are a place to run agents; the first thing you should think to do with a new Sprite is to type claude (or gemini or codex). We've put a lot of effort into making sure coding agents feel safe and happy when they're on Sprites, because, to (probably) quote John von Neumann, "happy agents are productive agents." What's less obvious about Sprites is that they're great tools for agents. Want three different versions of a new feature? A test environment? An ensemble of cooperating services? It's super handy to be able to start your prompts, "On a new Sprite, do...". The Sprites API is simple, discoverable, and designed for this use case. The only real question is how your agent reaches it. For most of you the answer is MCP, and the setup is already written. You Don't Have To Pick There's an argument going around that MCP is the wrong way to extend an agent, and that command line tools and discoverable APIs are the Right Way. Half of that argument is correct, and it's the important half, so let's take it seriously. Dumping thirty tool descriptions into a context window is a bad way to teach anything. Not every Sprite command matters in every session, and cramming them all in signals to the model that they all matter to you. If you're not using network policies, gemini shouldn't burn a single token learning to configure them. Capabilities should reveal themselves progressively, the way they do when an agent works out a CLI one subcommand at a time. The wrong half is treating that as a case against MCP. Progressive disclosure is a question of what you say to the model. MCP is a question of how the bytes get there: transport, auth, structured results, a tool the model can call instead of a command whose flags it has to guess. Tho ## Building Reproducible AI Evaluation Workflows with Docker Sandboxes DevFeed: [Building Reproducible AI Evaluation Workflows with Docker Sandboxes]() Original publisher: [Read original article]() Author: Jennifer Kohl Published: 2026-09-02T13:00:00Z Content type: tutorial Language: en Sources: [Docker]() Topics: [ai observability](), [Human-AI evaluation]() Tags: [ai](), [ai-agent](), [ai-ml](), [ai-models](), [benchmarks](), [claude](), [community](), [docker](), [docker-sandboxes](), [evaluation](), [genai](), [json](), [open-source](), [python](), [sandbox](), [sandboxes](), [workflow](), [workflows]() ### AI overview The article presents an open-source Docker Sandboxes Mixin Kit for making AI evaluation workflows reproducible. It runs configured commands in a consistent environment and records structured results and runtime evidence, without executing models or generating evaluation judgments itself. ### Source excerpt Learn how Docker Sandboxes can make AI evaluation workflows more reproducible with consistent execution, structured artifacts, and runtime evidence. [Next page]()