# Docker & Containers Published articles for Docker & Containers. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Forgejo 16.0.4 and 15.0.8 Fix Critical Repository Template RCE DevFeed: [Forgejo 16.0.4 and 15.0.8 Fix Critical Repository Template RCE]() Original publisher: [Read original article]() Author: Christian Rakoot Published: 2026-09-12T06:40:18Z Content type: article Language: en Sources: [Self Host Lab]() Topics: [vulnerability](), [releases](), [Security](), [Template](), [Authorization](), [API](), [Git]() Tags: [api](), [docker-containers](), [docker-containers-news](), [forgejo](), [git](), [news](), [release](), [security](), [self-hosted](), [update](), [vulnerability]() ### AI overview Forgejo 16.0.4 and 15.0.8 fix a critical remote code execution vulnerability in repository-template creation, along with an API authorization bypass. The article explains how malicious template variables could restore a .git directory with executable hooks and urges affected self-hosted instances to update. ### Source excerpt Forgejo 16.0.4 and 15.0.8 patch a critical remote code execution vulnerability in repository templates, tracked as CVE-2026-89094 with a CVSS score of 9.9, plus a narrower API permission bypass. Any instance on 16.0.3 or earlier, or 15.0.7 or earlier on the LTS branch, is vulnerable. Here's what happened, why it matters, and how to update. ## Bring your Dockerfile to Vercel Functions DevFeed: [Bring your Dockerfile to Vercel Functions]() Original publisher: [Read original article]() Author: Joe Haddad Published: 2026-06-30T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Dockerfile](), [Containers](), [Docker]() Tags: [autoscaling](), [container-images](), [container-registry](), [containers](), [docker](), [docker-containers](), [oci](), [routing](), [vercel]() ### AI overview Vercel Functions now support deploying HTTP servers from Dockerfile or Containerfile projects using OCI-compatible container images on Fluid compute. Images are built, pushed to Vercel Container Registry, and deployed on each commit, while retaining Vercel preview deployments, logs, routing, and autoscaling benefits. ### Source excerpt Vercel Functions now support deploying HTTP servers from a Dockerfile or Containerfile, using Open Container Initiative (OCI) compatible images on Fluid compute. This makes it easier to bring existing applications written in any language to Vercel while keeping the preview deployments, logs, routing, and autoscaling benefits of using Vercel Functions and Fluid compute. To use container images with your functions, create a project with a Dockerfile.vercel (or Containerfile.vercel) file that starts an HTTP server listening on $PORT: This image will be built, pushed, and deployed on every commit to Vercel Container Registry. Learn more about using container images in the docs and see seven ways you can use Docker containers on Vercel. Read more ## Docker Hodgepodge Images DevFeed: [Docker Hodgepodge Images]() Original publisher: [Read original article]() Published: 2026-04-15T00:00:00Z Content type: opinion Language: en Sources: [Chainguard: Unchained]() Topics: [Docker Hardened Images](), [supply-chain-security](), [vulnerability](), [Docker]() Tags: [chainguard-vs-docker](), [dhi](), [docker](), [docker-containers](), [docker-hardened-images](), [docker-images](), [free-container-images](), [security](), [supply-chain-security](), [vulnerability](), [vulnerability-scanner]() ### AI overview The article argues that Docker Hardened Images are Debian Trixie derivatives rather than ordinary Debian images. It contends that Docker's custom repository, rebuilt packages, and operating-system identification can cause vulnerability scanners and related tools to produce inaccurate results, creating supply chain security concerns. ### Source excerpt Docker ships their own Linux distro, they just pretend not to. Learn how misidentification and VEX usage can mislead scanners and impact supply chain security. ## Going deep: Upstream distros and hidden CVEs DevFeed: [Going deep: Upstream distros and hidden CVEs]() Original publisher: [Read original article]() Published: 2026-02-25T00:00:00Z Content type: opinion Language: en Sources: [Chainguard: Unchained]() Topics: [Docker Hardened Images](), [supply-chain-security](), [container images](), [Vulnerabilities](), [Debian](), [Docker]() Tags: [chainguard-containers](), [debian](), [debian-containers](), [dhi](), [docker](), [docker-containers](), [docker-hardened-images](), [security](), [supply-chain](), [supply-chain-security](), [vex](), [vulnerabilities](), [zero-cves]() ### AI overview The article argues that container vendors relying on upstream distributions such as Debian or Alpine can inherit vulnerabilities because fixes may lag between upstream availability and downstream image releases. It examines Docker Hardened Images and claims that some CVEs are suppressed through no-DSA classifications and VEX documents even when fixes exist upstream but have not been incorporated into the images. ### Source excerpt Are all zero-CVE images truly secure? A deep dive into Debian no-DSA, VEX suppression, and why transparency matters in container supply chain security. ## Corrosion DevFeed: [Corrosion]() Original publisher: [Read original article]() Published: 2025-10-22T00:00:00Z Content type: article Language: en Sources: [The Fly Blog]() Topics: [distributed-systems](), [Concurrent Programming](), [Deadlock](), [Rust](), [Network](), [Orchestration](), [fly](), [fly.io]() Tags: [cdn](), [close-to-users](), [deadlock](), [deploy-app-servers](), [distributed-system](), [docker](), [docker-containers](), [elixir](), [fly](), [fly-io](), [heroku-alternative](), [heroku-competitor](), [hosting](), [i](), [networking](), [outage](), [pipelines](), [postgresql-clusters](), [routing](), [rust](), [servers](), [synchronization]() ### AI overview This article introduces Corrosion, Fly.io's open-source distributed state synchronization and service discovery system. It explains how Fly.io propagates workload and routing state across globally distributed servers and edge proxies, and recounts a severe outage caused by a Rust concurrency bug that triggered a contagious deadlock. The article also describes Fly.io's decentralized orchestration model, in which individual servers are authoritative for their workloads instead of relying on a centralized database. ### Source excerpt Fly.io transmogrifies Docker containers into Fly Machines: micro-VMs running on our own hardware all over the world. The hardest part of running this platform isn't managing the servers, and it isn't operating the network; it's gluing those two things together. Several times a second, as customer CI/CD pipelines tear up or bring down Fly Machines, our state synchronization system blasts updates across our internal mesh, so that edge proxies from Tokyo to Amsterdam can keep the accurate routing table that allows them to route requests for applications to the nearest customer instances. On September 1, 2024, at 3:30PM EST, a new Fly Machine came up with a new "virtual service" configuration option a developer had just shipped. Within a few seconds every proxy in our fleet had locked up hard. It was the worst outage we've experienced: a period during which no end-user requests could reach our customer apps at all. Distributed systems are blast amplifiers. By propagating data across a network, they also propagate bugs in the systems that depend on that data. In the case of Corrosion, our state distribution system, those bugs propagate quickly. The proxy code that handled that Corrosion update had succumbed to a notorious Rust concurrency footgun: an if let expression over an RWLock assumed (reasonably, but incorrectly) in its else branch that the lock had been released. Instant and virulently contagious deadlock. A lesson we've learned the hard way: never trust a distributed system without an interesting failure story. If a distributed system hasn't ruined a weekend or kept you up overnight, you don't understand it yet. Which is why that's how we're introducing Corrosion, an unconventional service discovery system we built for our platform and open sourced. Our Face-Seeking Rake State synchronization is the hardest problem in running a platform like ours. So why build a risky new distributed system for it? Because no matter what we try, that rake is waiting for our foot ## How to Deploy a Pterodactyl Game Server with Docker DevFeed: [How to Deploy a Pterodactyl Game Server with Docker]() Original publisher: [Read original article]() Author: Techno Tim Published: 2022-04-30T13:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Docker](), [Containers](), [Open Source](), [Server]() Tags: [containers](), [docker](), [docker-containers](), [game-servers](), [games](), [homelab](), [how-to](), [install](), [open-source]() ### AI overview This tutorial explains how to deploy a Pterodactyl dedicated game server using Docker containers, including the Pterodactyl Panel, game server nodes, and the Wings agent. It also covers reverse-proxy configuration and stack setup. ### Source excerpt Pterodactyl is a free an open source dedicated game server.It comes with both a panel to configure and deploy your game servers as well as game server nodes to run your games.It runs games in Docker containers to keep them isolated and making them easier than ever to deploy.We're going to also use Docker to create our Pterodactyl server and the Wings agent making this truly Docker to the core. ... ## Spark Joy by Running Fewer Tests DevFeed: [Spark Joy by Running Fewer Tests]() Original publisher: [Read original article]() Author: Jessica Xie Published: 2020-06-11T18:56:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [ci](), [Scalability](), [Development](), [Pull Request](), [Shopify](), [Code](), [Docker]() Tags: [analysis](), [bugs](), [ci](), [code](), [containers](), [developers](), [docker](), [docker-containers](), [performance](), [pull-request](), [quality-assurance](), [scalability](), [shopify](), [spark](), [speed]() ### AI overview This Shopify Engineering article explains how large test suites can slow development, reduce scalability, and increase intermittent failures. It introduces a dynamic test-selection system intended to make continuous integration faster and more stable by running fewer, more relevant tests. ### Source excerpt Developers write tests to ensure correctness and allow future changes to be made safely. However, as the number of features grows, so does the number of tests. Tests are a double-edged sword. On one hand, well-written ones catch bugs and maintain a program's stability, but as the code base grows, a high number of tests impedes scalability because they take a long time to run and increase the likelihood of intermittently failing tests. ## Docker Containers on the Desktop DevFeed: [Docker Containers on the Desktop]() Original publisher: [Read original article]() Published: 2015-02-21T17:16:52Z Content type: tutorial Language: en Sources: [Jessie Frazelle]() Topics: [Docker](), [Containers](), [App](), [Access Control](), [Kernel](), [Bash](), [Chrome]() Tags: [access-control](), [app](), [bash](), [chrome](), [containers](), [docker](), [docker-containers](), [kernel]() ### AI overview A developer explains how they use Docker to run desktop applications in containers. The article discusses isolation inspired by OS X App Sandbox, resource limits for CPU and memory, and examples of text-based and graphical applications launched through shell aliases. ### Source excerpt Hello! If you are not familiar with Docker, it is the popular open source container engine. Most people use Docker for containing applications to deploy into production or for building their applications in a contained environment. This is all fine & dandy, and saves developers & ops engineers huge headaches, but I like to use Docker in a not-so-typical way. I use Docker to run all the desktop apps on my computers. But why would I even want to run all these apps in containers? Well let me explain. I used to be an OS X user, and the great thing about OS X is the OS X App Sandbox. App Sandbox is an access control technology provided in OS X, enforced at the kernel level. Its strategy is twofold: App Sandbox enables you to describe how your app interacts with the system. The system then grants your app the access it needs to get its job done, and no more. App Sandbox provides a last line of defense against the theft, corruption, or deletion of user data if an attacker successfully exploits security holes in your app or the frameworks it is linked against. Apple About App Sandbox I am using the Apple App Sandbox as an example so people can grasp the concept easily. I am not saying this is exactly like that and has all the features. This is not a sandbox. It is more like a cool hack. I hate installing things on my host and the files getting everywhere. I wanted the ability to delete an app and know it is gone fully without some random file hanging around. This gave me that. Not only that, I can control how much CPU and Memory the app uses. Yes, the cpu/memory hungry chrome is now perfectly contained! "What?!?!", you say. Let me show you. The following covers a few of my favorite applications I run in containers. Each of the commands written below is actually pulled directly from my bash aliases. So you can have the same user experience as running one command today. TUIs (Text User Interface, pronounced too-eee) Let's start with some easy text-based applications: 1. Irssi