# Docker

Docker is a platform and tooling for developing, shipping, and running containerized applications.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Meet the New Docker: Built to Run on Trust

DevFeed: [Meet the New Docker: Built to Run on Trust](<https://devfeed.tech/articles/meet-the-new-docker-built-to-run-on-trust-144458.md>)

Original publisher: [Read original article](<https://www.docker.com/blog/meet-the-new-docker-built-to-run-on-trust/>)

Author: Jin Kim

Published: 2026-11-19T17:00:00Z

Content type: release

Language: en

Sources: [Docker](<https://devfeed.tech/sources/docker.md>)

Topics: [trust](<https://devfeed.tech/topics/trust.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [Docker AI Governance](<https://devfeed.tech/topics/docker-ai-governance.md>), [Docker Sandboxes](<https://devfeed.tech/topics/docker-sandboxes.md>), [Local AI](<https://devfeed.tech/topics/local-ai.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [brand](<https://devfeed.tech/tags/brand.md>), [community](<https://devfeed.tech/tags/community.md>), [company](<https://devfeed.tech/tags/company.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-ai-governance](<https://devfeed.tech/tags/docker-ai-governance.md>), [moby](<https://devfeed.tech/tags/moby.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

Docker presents its rebrand as an expansion of its role for the AI-agent era, while retaining its developer-first approach, openness, simplicity and container work. It argues that containers isolate workloads, but agents act autonomously by choosing what to run, access and change, so organizations need purpose-built isolation and governance to give them autonomy while maintaining control. Docker frames its next chapter around a trusted supply chain, an agent runtime and an ecosystem intended to cover governance and risk across enterprises, including third-party layers without vendor lock-in. It points readers to Docker Sandboxes and Docker AI Governance as ways to explore the approach, but provides no implementation details or comparative evidence for those products.

### Source excerpt

Docker launches a new brand built on trust. Learn why Docker is evolving for AI agents, what stays the same, and how to run agents securely with Docker.

## Pulse Monitors Your Proxmox and Docker Servers From One Dashboard

DevFeed: [Pulse Monitors Your Proxmox and Docker Servers From One Dashboard](<https://devfeed.tech/articles/pulse-monitors-your-proxmox-and-docker-servers-from-one-dashboard-144123.md>)

Original publisher: [Read original article](<https://noted.lol/pulse-self-hosted-proxmox-docker-monitoring/>)

Author: Jeremy

Published: 2026-11-19T12:19:13Z

Content type: article

Language: en

Sources: [Noted](<https://devfeed.tech/sources/noted.md>)

Topics: [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [Homelab](<https://devfeed.tech/topics/homelab.md>), [Proxmox](<https://devfeed.tech/topics/proxmox.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [Docker Compose](<https://devfeed.tech/topics/docker-compose.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Self Hosted AI Tools](<https://devfeed.tech/topics/self-hosted-ai-tools.md>)

Tags: [access-controls](<https://devfeed.tech/tags/access-controls.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-monitoring](<https://devfeed.tech/tags/ai-monitoring.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [api](<https://devfeed.tech/tags/api.md>), [audit-logging](<https://devfeed.tech/tags/audit-logging.md>), [availability](<https://devfeed.tech/tags/availability.md>), [backup](<https://devfeed.tech/tags/backup.md>), [backups](<https://devfeed.tech/tags/backups.md>), [charts](<https://devfeed.tech/tags/charts.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [docker](<https://devfeed.tech/tags/docker.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [proxmox](<https://devfeed.tech/tags/proxmox.md>), [pulse](<https://devfeed.tech/tags/pulse.md>), [resource](<https://devfeed.tech/tags/resource.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [self-hosted-web-tools](<https://devfeed.tech/tags/self-hosted-web-tools.md>), [servers](<https://devfeed.tech/tags/servers.md>), [tracking](<https://devfeed.tech/tags/tracking.md>)

### AI overview

Pulse brings monitoring for Proxmox, Docker, and other listed platforms into a self-hosted dashboard, with resource history, backup status, service availability checks, and configurable alerts. Proxmox connects through its API with a read-only token and needs no host agent; Docker uses a lightweight agent, and the central Pulse container does not need direct Docker socket access. Alerts can require a condition to persist, helping avoid notifications for brief resource spikes. The free MIT-licensed Community edition has seven days of metric history and no system-count limit; Pro adds 90 days, more AI investigation capabilities, role-based access controls, and audit logging. Pulse Patrol is optional and can use a local model or external AI provider.

### Source excerpt

Pulse is a self-hosted monitoring dashboard for Proxmox and Docker, with resource tracking, backup monitoring, and customizable alerts.

## DockNest Backs Up Your Docker Apps and Tests Whether They Can Be Restored

DevFeed: [DockNest Backs Up Your Docker Apps and Tests Whether They Can Be Restored](<https://devfeed.tech/articles/docknest-backs-up-your-docker-apps-and-tests-whether-they-can-be-restored-133644.md>)

Original publisher: [Read original article](<https://noted.lol/docknest/>)

Author: Jeremy

Published: 2026-11-13T14:12:33Z

Content type: article

Language: en

Sources: [Noted](<https://devfeed.tech/sources/noted.md>)

Topics: [backups](<https://devfeed.tech/topics/backups.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Docker Compose](<https://devfeed.tech/topics/docker-compose.md>)

Tags: [aes](<https://devfeed.tech/tags/aes.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [application-management](<https://devfeed.tech/tags/application-management.md>), [arm](<https://devfeed.tech/tags/arm.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [backup](<https://devfeed.tech/tags/backup.md>), [backup-and-recovery](<https://devfeed.tech/tags/backup-and-recovery.md>), [backups](<https://devfeed.tech/tags/backups.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [containers](<https://devfeed.tech/tags/containers.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [database](<https://devfeed.tech/tags/database.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-compose](<https://devfeed.tech/tags/docker-compose.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [self-hosted-web-tools](<https://devfeed.tech/tags/self-hosted-web-tools.md>), [servers](<https://devfeed.tech/tags/servers.md>), [tests](<https://devfeed.tech/tags/tests.md>)

### AI overview

DockNest is a self-hosted tool for backing up Docker Compose projects and static nginx sites across Linux servers, then checking whether backups can start in an isolated environment without disturbing live services. It connects over SSH, backs up images, volumes, bind mounts and supported databases, and offers per-application schedules and retention. Encrypted backups use AES-256-GCM and can be stored via SFTP or S3-compatible services. For migration, DockNest backs up an application, tests a copy on the destination, waits for DNS changes, and keeps the original stopped for seven days as a rollback option. Setup requires Node.js 24 initially; managed servers need SSH, Python 3.9+ and Docker access. The excerpt notes that incremental backups and some management features are not fully supported, ARM users must build from source, and losing data/master.key makes encrypted backups unrecoverable.

### Source excerpt

DockNest is a self-hosted Docker backup and recovery tool that automates backups, tests restores, and helps migrate applications between servers.

## Taming Autonomous AI Agents with Rootless Docker

DevFeed: [Taming Autonomous AI Agents with Rootless Docker](<https://devfeed.tech/articles/taming-autonomous-ai-agents-with-rootless-docker-121591.md>)

Original publisher: [Read original article](<https://hackernoon.com/taming-autonomous-ai-agents-with-rootless-docker?source=rss>)

Author: Siva Sai Krishna Suryadevara

Published: 2026-11-06T15:00:45Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Docker](<https://devfeed.tech/topics/docker.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [cgroups](<https://devfeed.tech/topics/cgroups.md>), [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [autonomous-ai-agents](<https://devfeed.tech/tags/autonomous-ai-agents.md>), [cgroups](<https://devfeed.tech/tags/cgroups.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [container-security](<https://devfeed.tech/tags/container-security.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-engine-api](<https://devfeed.tech/tags/docker-engine-api.md>), [docker-hardening](<https://devfeed.tech/tags/docker-hardening.md>), [docker-security](<https://devfeed.tech/tags/docker-security.md>), [linux](<https://devfeed.tech/tags/linux.md>), [linux-containers](<https://devfeed.tech/tags/linux-containers.md>), [mcp-servers](<https://devfeed.tech/tags/mcp-servers.md>), [namespaces](<https://devfeed.tech/tags/namespaces.md>), [rootless-docker](<https://devfeed.tech/tags/rootless-docker.md>)

### AI overview

Rootless Docker can bound the host impact of autonomous coding agents, but only if they use the rootless daemon's socket and cannot fall back to the rootful system socket. User namespaces map container root to the service account and subordinate host IDs; cgroups v2 with systemd can limit resources, though limits may be silently ignored when the cgroup driver is `none` or controllers are not delegated. The article recommends a dedicated low-privilege account, explicit per-container memory, CPU and PID limits, and restrictive settings such as dropping capabilities, read-only filesystems and disabled networking where possible. Rootless networking uses user-mode drivers such as `slirp4netns`, with lower throughput and separate host firewall concerns. Configure agents and MCP servers to honor `DOCKER_HOST`, discover `$XDG_RUNTIME_DIR/docker.sock`, and allow the rootful socket only by policy; rootless Docker is an execution boundary, not an application-level policy proxy.

### Source excerpt

How rootless Docker, Linux user namespaces, and cgroups v2 contain autonomous AI coding agents without escalating to host root privileges.

## Demystifying Linux Cgroups: The Hidden Engine Powering Docker and Kubernetes

DevFeed: [Demystifying Linux Cgroups: The Hidden Engine Powering Docker and Kubernetes](<https://devfeed.tech/articles/demystifying-linux-cgroups-the-hidden-engine-powering-docker-and-kubernetes-121431.md>)

Original publisher: [Read original article](<https://blog.devops.dev/demystifying-linux-cgroups-the-hidden-engine-powering-docker-and-kubernetes-e6627f9fe75d?source=rss----33f8b2d9a328---4>)

Author: Techie Crow

Published: 2026-11-06T09:45:56Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [cgroups](<https://devfeed.tech/topics/cgroups.md>), [Linux Kernel](<https://devfeed.tech/topics/linux-kernel.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Docker](<https://devfeed.tech/topics/docker.md>)

Tags: [cgroup](<https://devfeed.tech/tags/cgroup.md>), [cgroups](<https://devfeed.tech/tags/cgroups.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [containers](<https://devfeed.tech/tags/containers.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devops-engineer](<https://devfeed.tech/tags/devops-engineer.md>), [docker](<https://devfeed.tech/tags/docker.md>), [google](<https://devfeed.tech/tags/google.md>), [groups](<https://devfeed.tech/tags/groups.md>), [i-o](<https://devfeed.tech/tags/i-o.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-yaml-manifests](<https://devfeed.tech/tags/kubernetes-yaml-manifests.md>), [linux](<https://devfeed.tech/tags/linux.md>), [linux-kernel](<https://devfeed.tech/tags/linux-kernel.md>), [memory](<https://devfeed.tech/tags/memory.md>), [node](<https://devfeed.tech/tags/node.md>), [performance](<https://devfeed.tech/tags/performance.md>), [pod](<https://devfeed.tech/tags/pod.md>)

### AI overview

Linux cgroups are kernel controls for allocating, restricting, prioritizing, and monitoring resources used by groups of processes. The excerpt identifies memory, CPU, and disk I/O as resources that can be capped, and says cgroups can prioritize CPU or disk throughput under system pressure. It frames cgroups as underlying resource controls relevant to containers, but the excerpt does not explain how they map to Kubernetes settings or determine pod priority.

### Source excerpt

Ever wondered how your server handles hundreds of isolated containers without losing its mind? Or how Kubernetes ensures that a single... Continue reading on DevOps.dev "

## Docker Sandboxes vs. Containers: Choosing the Right Isolation for AI Agents

DevFeed: [Docker Sandboxes vs. Containers: Choosing the Right Isolation for AI Agents](<https://devfeed.tech/articles/docker-sandboxes-vs-containers-choosing-the-right-isolation-for-ai-agents-120910.md>)

Original publisher: [Read original article](<https://www.docker.com/blog/docker-sandboxes-vs-containers/>)

Author: Jackie Frederick

Published: 2026-11-06T03:17:04Z

Content type: article

Language: en

Sources: [Docker](<https://devfeed.tech/sources/docker.md>)

Topics: [Docker Sandboxes](<https://devfeed.tech/topics/docker-sandboxes.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [virtualization](<https://devfeed.tech/topics/virtualization.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [Docker AI Governance](<https://devfeed.tech/topics/docker-ai-governance.md>)

Tags: [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [cloud-sandboxes](<https://devfeed.tech/tags/cloud-sandboxes.md>), [concepts](<https://devfeed.tech/tags/concepts.md>), [containers](<https://devfeed.tech/tags/containers.md>), [docker-sandboxes](<https://devfeed.tech/tags/docker-sandboxes.md>), [products](<https://devfeed.tech/tags/products.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Containers isolate processes while sharing the host kernel, making them fast and well suited to packaged applications, CI jobs, and short-lived execution. Docker Sandboxes place autonomous coding agents in dedicated microVMs with their own kernel, filesystem, network, and private Docker Engine; agents can use sudo, build images, and run Compose without access to the host Docker daemon. Host-enforced network rules and credential mediation can limit access, while workspace files, MCP servers, and skills remain reachable if shared. Sandboxes preserve session state but require a supported hypervisor and more memory and disk; cloud sandboxes are an option when local resources are limiting. The article recommends containers for controlled workloads and Sandboxes when agents run unattended, handle untrusted input, need Docker capabilities or protected credentials, or work across longer sessions. Kits and environment files support repeatable setups, though both are described as early access or experimental.

### Source excerpt

A container shares the host kernel. Docker Sandboxes are microVMs with their own kernel and private Docker Engine. See how they differ and when to use each.

## Docker and ActiveState Extending Secure Defaults to the Packages Developers Install

DevFeed: [Docker and ActiveState Extending Secure Defaults to the Packages Developers Install](<https://devfeed.tech/articles/docker-and-activestate-extending-secure-defaults-to-the-packages-developers-install-119503.md>)

Original publisher: [Read original article](<https://www.docker.com/blog/docker-activestate-trusted-content/>)

Author: Vishrut Iyengar

Published: 2026-11-05T15:28:22Z

Content type: release

Language: en

Sources: [Docker](<https://devfeed.tech/sources/docker.md>)

Topics: [Docker Hardened Images](<https://devfeed.tech/topics/docker-hardened-images.md>), [AI software supply chain security](<https://devfeed.tech/topics/ai-software-supply-chain-security.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [npm](<https://devfeed.tech/topics/npm.md>), [pip](<https://devfeed.tech/topics/pip.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [ai-coding-assistants](<https://devfeed.tech/tags/ai-coding-assistants.md>), [artifactory](<https://devfeed.tech/tags/artifactory.md>), [attack-surface](<https://devfeed.tech/tags/attack-surface.md>), [axios](<https://devfeed.tech/tags/axios.md>), [blast-radius](<https://devfeed.tech/tags/blast-radius.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [built-from-source](<https://devfeed.tech/tags/built-from-source.md>), [content](<https://devfeed.tech/tags/content.md>), [developers](<https://devfeed.tech/tags/developers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-hardened-images](<https://devfeed.tech/tags/docker-hardened-images.md>), [packages](<https://devfeed.tech/tags/packages.md>), [partners](<https://devfeed.tech/tags/partners.md>), [partnerships](<https://devfeed.tech/tags/partnerships.md>), [products](<https://devfeed.tech/tags/products.md>), [secure-defaults](<https://devfeed.tech/tags/secure-defaults.md>), [security](<https://devfeed.tech/tags/security.md>), [solutions](<https://devfeed.tech/tags/solutions.md>), [standard](<https://devfeed.tech/tags/standard.md>), [teams](<https://devfeed.tech/tags/teams.md>), [trusted-supply-chain](<https://devfeed.tech/tags/trusted-supply-chain.md>)

### AI overview

Docker and ActiveState extend supply chain controls from container images to application dependencies. Docker Hardened Images (DHI) are minimal, source-built images with signed SBOMs, SLSA Level 3 provenance, full CVE visibility, and--on paid tiers--a 7-day SLA for critical and high CVEs. ActiveState's Curated Catalog is a policy-governed repository containing team-approved packages, compiled from source with SLSA Level 3 provenance and complete SBOMs; it automatically rebuilds components after upstream fixes, with SLAs of 5 business days for critical CVEs and 10 for high CVEs. Teams can route Artifactory or Nexus through the catalog while developers and coding assistants retain familiar pip and npm workflows. The article says these controls complement pinned digests, cooldown periods, and sandboxed agents; the integration does not replace them.

### Source excerpt

Docker partners with ActiveState to continue to provide one standard for trusted content across everything you and your teams build on.

## I got tired of remembering ports for 30 Docker apps in my homelab. Here's how I fixed it

DevFeed: [I got tired of remembering ports for 30 Docker apps in my homelab. Here's how I fixed it](<https://devfeed.tech/articles/i-got-tired-of-remembering-ports-for-30-docker-apps-in-my-homelab-here-s-how-i-fixed-it-117109.md>)

Original publisher: [Read original article](<https://blog.adafruit.com/2026/11/04/i-got-tired-of-remembering-ports-for-30-docker-apps-in-my-homelab-heres-how-i-fixed-it/>)

Author: Anne Barela

Published: 2026-11-04T16:58:29Z

Content type: article

Language: en

Sources: [Adafruit Industries](<https://devfeed.tech/sources/adafruit-industries-makers-hackers-artists-designers-and-engineers.md>)

Topics: [tailscale](<https://devfeed.tech/topics/tailscale.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [Homelab](<https://devfeed.tech/topics/homelab.md>)

Tags: [docker](<https://devfeed.tech/tags/docker.md>), [github](<https://devfeed.tech/tags/github.md>), [go](<https://devfeed.tech/tags/go.md>), [homelab](<https://devfeed.tech/tags/homelab.md>), [projects](<https://devfeed.tech/tags/projects.md>), [software](<https://devfeed.tech/tags/software.md>), [tailscale](<https://devfeed.tech/tags/tailscale.md>)

### AI overview

Tailscale Services lets the author reach homelab apps by service name instead of remembering each machine's IP address and port. A Service has a name and virtual IP on the tailnet and can be advertised by tagged machines; access rules can target an individual Service, allowing Jellyfin to be shared without exposing its whole host. Setting this up manually requires a tagged host, a policy with an auto-approver, and a service definition and serve command for each app. The author found that cumbersome across about 30 containers, with configuration split between Docker Compose and the admin console, and wrote DockTail, an AGPL-3.0 Go program that watches Docker events and turns container labels into Services.

### Source excerpt

A community writer at It's FOSS runs a homelab of 5 machines and about 30 Docker containers, and got tired of a bookmarks folder full of IP addresses and port numbers. Tailscale got them into the network from anywhere, but once inside they still had to remember which box ran what. Tailscale Services gave them [...]

## Docker Urges Isolation and Governance for AI Agent Security

DevFeed: [Docker Urges Isolation and Governance for AI Agent Security](<https://devfeed.tech/articles/docker-urges-isolation-and-governance-for-ai-agent-security-116316.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/docker-ai-agent-security/>)

Author: Matt Saunders

Published: 2026-11-04T09:00:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [ai-governance](<https://devfeed.tech/topics/ai-governance.md>), [Docker AI Governance](<https://devfeed.tech/topics/docker-ai-governance.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [credential-based attacks](<https://devfeed.tech/topics/credential-based-attacks.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-security](<https://devfeed.tech/tags/agent-security.md>), [agentic-ai-architecture](<https://devfeed.tech/tags/agentic-ai-architecture.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agent-security](<https://devfeed.tech/tags/ai-agent-security.md>), [ai-security](<https://devfeed.tech/tags/ai-security.md>), [devops](<https://devfeed.tech/tags/devops.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-ai-agent-security](<https://devfeed.tech/tags/docker-ai-agent-security.md>), [governance](<https://devfeed.tech/tags/governance.md>), [human-oversight](<https://devfeed.tech/tags/human-oversight.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [news](<https://devfeed.tech/tags/news.md>), [risks](<https://devfeed.tech/tags/risks.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Docker identifies prompt injection, tool misuse, excessive autonomy, credential exposure and data exfiltration as risks amplified by agents that choose tools, chain actions and may inherit a user's permissions. It argues prompt injection cannot reliably be solved through model instructions alone, so defenses should limit the impact of a hijacked agent. Its guidance includes giving agents only task-required tools, containing broad automation within security boundaries, using separate short-lived credentials injected at runtime, allow-listing network egress and treating agent handoffs as untrusted. Docker proposes disposable microVM sandboxes with filesystem and network controls, plus AI Governance to enforce permitted actions, tools and credentials. The article also notes that isolation choices depend on workload trust boundaries: community commenters question Docker's authority limits and shared-kernel suitability for code run on others' behalf, suggesting deny-by-default controls or microVM/gVisor isolation in those cases.

### Source excerpt

Docker has published a guide to five security risks that arise when AI agents are allowed to browse, run code and call tools with limited human oversight. They argue that the autonomy that makes agents useful also makes conventional application security controls insufficient. The company positions isolation and governance, rather than model improvements alone, as the main defences. By Matt Saunders

## I Got Tired of Remembering Ports for 30 Docker Apps in My Homelab. Here's How I Fixed it

DevFeed: [I Got Tired of Remembering Ports for 30 Docker Apps in My Homelab. Here's How I Fixed it](<https://devfeed.tech/articles/i-got-tired-of-remembering-ports-for-30-docker-apps-in-my-homelab-here-s-how-i-fixed-it-116435.md>)

Original publisher: [Read original article](<https://feed.itsfoss.com/link/24361/17515094/tailscale-services>)

Author: Community

Published: 2026-11-04T06:36:35Z

Content type: tutorial

Language: en

Sources: [It's FOSS](<https://devfeed.tech/sources/it-s-foss.md>)

Topics: [tailscale](<https://devfeed.tech/topics/tailscale.md>), [Homelab](<https://devfeed.tech/topics/homelab.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [Docker Compose](<https://devfeed.tech/topics/docker-compose.md>), [traefik](<https://devfeed.tech/topics/traefik.md>)

Tags: [access-controls](<https://devfeed.tech/tags/access-controls.md>), [apps](<https://devfeed.tech/tags/apps.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [clients](<https://devfeed.tech/tags/clients.md>), [compose](<https://devfeed.tech/tags/compose.md>), [config](<https://devfeed.tech/tags/config.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [containers](<https://devfeed.tech/tags/containers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-container](<https://devfeed.tech/tags/docker-container.md>), [homelab](<https://devfeed.tech/tags/homelab.md>), [https](<https://devfeed.tech/tags/https.md>), [ip](<https://devfeed.tech/tags/ip.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [reverse](<https://devfeed.tech/tags/reverse.md>), [reverse-proxy](<https://devfeed.tech/tags/reverse-proxy.md>), [services](<https://devfeed.tech/tags/services.md>), [sidecar](<https://devfeed.tech/tags/sidecar.md>), [tailnet](<https://devfeed.tech/tags/tailnet.md>), [tailscale](<https://devfeed.tech/tags/tailscale.md>)

### AI overview

Tailscale Services give Docker apps their own HTTPS names on a tailnet while keeping them off the Machines list. A host advertises each Service; `tailscaled` terminates HTTPS and forwards plain HTTP to the app, adding `X-Forwarded-For`. Manual setup requires a tagged host, suitable tag policy and approval, and a `tailscale serve` command per app; published host ports are needed for that route. DockTail automates Service creation and routing from Docker labels, watches container events, and can target container IPs without published ports. It requires Docker socket access, Tailscale state access, and an OAuth client with Services: Write and Devices Core: Write scoped to the host tag. Apps that validate proxy headers may need trusted proxy settings. The author prefers this for changing homelabs because Compose labels track app lifecycle, while noting manual setup is adequate for a few stable containers and a reverse proxy remains preferable for public services on a custom domain.

### Source excerpt

Stop bookmarking IP:ports. Tailscale Services gives every Docker container in your homelab its own HTTPS name on your tailnet, without a reverse proxy or a sidecar per container.

## How to Automate Docker Image Creation for Postgres Using Shell Commands

DevFeed: [How to Automate Docker Image Creation for Postgres Using Shell Commands](<https://devfeed.tech/articles/how-to-automate-docker-image-creation-for-postgres-using-shell-commands-116222.md>)

Original publisher: [Read original article](<https://www.freecodecamp.org/news/how-to-automate-docker-image-creation-for-postgres-using-shell/>)

Author: jabo Landry

Published: 2026-11-03T18:40:47Z

Content type: tutorial

Language: en

Sources: [Free Code Camp](<https://devfeed.tech/sources/freecodecamp-programming-tutorials-python-javascript-git-more.md>)

Topics: [Bash](<https://devfeed.tech/topics/bash.md>), [Shell](<https://devfeed.tech/topics/shell.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [Docker Compose](<https://devfeed.tech/topics/docker-compose.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>)

Tags: [automate](<https://devfeed.tech/tags/automate.md>), [automation](<https://devfeed.tech/tags/automation.md>), [bash](<https://devfeed.tech/tags/bash.md>), [bash-shell](<https://devfeed.tech/tags/bash-shell.md>), [cli](<https://devfeed.tech/tags/cli.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-compose](<https://devfeed.tech/tags/docker-compose.md>), [docker-image](<https://devfeed.tech/tags/docker-image.md>), [docker-images](<https://devfeed.tech/tags/docker-images.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [shell](<https://devfeed.tech/tags/shell.md>), [shell-scripting](<https://devfeed.tech/tags/shell-scripting.md>), [vibe-coding](<https://devfeed.tech/tags/vibe-coding.md>), [workflow-automation](<https://devfeed.tech/tags/workflow-automation.md>)

### AI overview

The guide shows how to build a Bash script that generates a Docker Compose file for a Postgres container. It checks whether a nonempty `docker-compose.yml` already exists, gathers database name, user, and password interactively or from positional arguments, validates required values, and supplies defaults for container name, port, and volume. It demonstrates writing Compose content with a heredoc, using `getopts` and `-D` to skip container prompts, then making the script executable and adding its directory to `PATH` via `~/.bash_profile` for use from any terminal. The prerequisites include Bash-compatible terminal use and Docker; Postgres experience is optional. The excerpt provides the workflow and examples but does not establish that the displayed Compose configuration or credential handling has been tested or is production-ready.

### Source excerpt

If you have certain lines of code that repeat over and over again in a project, there's a pretty standard solution for it: using a function. But what about when you have the same project file setup th

## Where should your code live in a Docker Sandbox?

DevFeed: [Where should your code live in a Docker Sandbox?](<https://devfeed.tech/articles/where-should-your-code-live-in-a-docker-sandbox-113426.md>)

Original publisher: [Read original article](<https://www.docker.com/blog/docker-sandbox-code-checkout-workflows/>)

Author: Jin Kim

Published: 2026-11-02T14:00:00Z

Content type: comparison

Language: en

Sources: [Docker](<https://devfeed.tech/sources/docker.md>)

Topics: [Docker Sandboxes](<https://devfeed.tech/topics/docker-sandboxes.md>), [versioning](<https://devfeed.tech/topics/versioning.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [remote-development](<https://devfeed.tech/topics/remote-development.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai-ml](<https://devfeed.tech/tags/ai-ml.md>), [clone](<https://devfeed.tech/tags/clone.md>), [code](<https://devfeed.tech/tags/code.md>), [devex](<https://devfeed.tech/tags/devex.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-sandbox](<https://devfeed.tech/tags/docker-sandbox.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [git](<https://devfeed.tech/tags/git.md>), [git-worktrees](<https://devfeed.tech/tags/git-worktrees.md>), [products](<https://devfeed.tech/tags/products.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [sandboxes](<https://devfeed.tech/tags/sandboxes.md>), [worktrees](<https://devfeed.tech/tags/worktrees.md>)

### AI overview

Docker Sandboxes offer several ways to place code, with different tradeoffs in collaboration, Git access, isolation, and handoff. A direct host mount lets you watch edits in your local editor and share Git operations, but branch switches and edits affect the agent's working tree; dependencies may also conflict across host and sandbox operating systems. A linked Git worktree gives each task its own directory and branch, but its `.git` metadata sits outside the mount, so Git status, branching, and commits must happen on the host. Clone mode gives the agent an independent checkout with Git and keeps its branches and dependencies separate; results return through a host remote or the repository's normal Git workflow. A mountless sandbox keeps code and tools inside the sandbox, with work returned by pushing or copying it out; previews require a published port, and removing the sandbox deletes files stored only there. Multiple repositories can be mounted or cloned together, including read-only references, though writable checkouts need coordination. These arrangements can be combined to fit a task.

### Source excerpt

Docker Sandboxes support three ways to organize an agent's code: shared mounts, Git worktrees, and clone mode. Here's how to choose between them.

## The Ecosystem is the Answer: Docker, the Blueprint Alliance, and the Importance of Collaboration in the Agentic Era

DevFeed: [The Ecosystem is the Answer: Docker, the Blueprint Alliance, and the Importance of Collaboration in the Agentic Era](<https://devfeed.tech/articles/the-ecosystem-is-the-answer-docker-the-blueprint-alliance-and-the-importance-of-collaboration-in-the-agentic-era-113425.md>)

Original publisher: [Read original article](<https://www.docker.com/blog/docker-blueprint-alliance-agent-baseline/>)

Author: Jin Kim

Published: 2026-11-02T14:00:00Z

Content type: opinion

Language: en

Sources: [Docker](<https://devfeed.tech/sources/docker.md>)

Topics: [ai-governance](<https://devfeed.tech/topics/ai-governance.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [Docker Sandboxes](<https://devfeed.tech/topics/docker-sandboxes.md>), [shadow AI](<https://devfeed.tech/topics/shadow-ai.md>), [Docker Hardened Images](<https://devfeed.tech/topics/docker-hardened-images.md>), [Docker AI Governance](<https://devfeed.tech/topics/docker-ai-governance.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>)

Tags: [2015](<https://devfeed.tech/tags/2015.md>), [2025](<https://devfeed.tech/tags/2025.md>), [academics](<https://devfeed.tech/tags/academics.md>), [actions](<https://devfeed.tech/tags/actions.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [blueprint](<https://devfeed.tech/tags/blueprint.md>), [blueprint-alliance](<https://devfeed.tech/tags/blueprint-alliance.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [company](<https://devfeed.tech/tags/company.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-ai-governance](<https://devfeed.tech/tags/docker-ai-governance.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [era](<https://devfeed.tech/tags/era.md>), [governance](<https://devfeed.tech/tags/governance.md>), [partnerships](<https://devfeed.tech/tags/partnerships.md>), [questions](<https://devfeed.tech/tags/questions.md>), [reference](<https://devfeed.tech/tags/reference.md>), [reference-architecture](<https://devfeed.tech/tags/reference-architecture.md>), [security](<https://devfeed.tech/tags/security.md>), [security-packages](<https://devfeed.tech/tags/security-packages.md>)

### AI overview

The Blueprint Alliance maps how enterprise AI governance components connect, while Agent Baseline defines what those components must do and how to verify it. The Alliance's 12 founding companies are pursuing interoperability over MCP, OCSF, SSF and CAEP and publishing reference integrations; its architecture addresses agent discovery, permissions, activity and response. Agent Baseline v1.0-draft defines six outcomes and 35 open, versioned controls. The excerpt recommends assessing against the baseline, beginning with discovery before policy, and testing containment in advance. It places Docker at the execution boundary: Docker Sandboxes support isolated execution, while Docker MCP Gateway and Docker Hardened Images address tool access and software supply chain. The article argues runtime support matters because API-driven containment without a way to pause an agent may provide a false sense of security. This is an excerpt, so it does not establish full-document coverage.

### Source excerpt

Docker is a founding member of the Blueprint Alliance, a 12-company reference architecture for securing AI agents, built around four governance questions.

## LHB Linux Digest #26.17: SSH Config, Docker Compose Override, Bash History Tricks and More

DevFeed: [LHB Linux Digest #26.17: SSH Config, Docker Compose Override, Bash History Tricks and More](<https://devfeed.tech/articles/lhb-linux-digest-26-17-ssh-config-docker-compose-override-bash-history-tricks-and-more-108351.md>)

Original publisher: [Read original article](<https://linuxhandbook.com/newsletter/26-17/>)

Author: Abhishek Prakash

Published: 2026-10-30T12:19:19Z

Content type: tutorial

Language: en

Sources: [Linux Handbook](<https://devfeed.tech/sources/linux-handbook.md>)

Topics: [ssh](<https://devfeed.tech/topics/ssh.md>), [Docker Compose](<https://devfeed.tech/topics/docker-compose.md>), [Bash](<https://devfeed.tech/topics/bash.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Linux Kernel](<https://devfeed.tech/topics/linux-kernel.md>)

Tags: [bash](<https://devfeed.tech/tags/bash.md>), [bash-history](<https://devfeed.tech/tags/bash-history.md>), [compose](<https://devfeed.tech/tags/compose.md>), [config](<https://devfeed.tech/tags/config.md>), [digest](<https://devfeed.tech/tags/digest.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-compose](<https://devfeed.tech/tags/docker-compose.md>), [history](<https://devfeed.tech/tags/history.md>), [linux](<https://devfeed.tech/tags/linux.md>), [newsletter](<https://devfeed.tech/tags/newsletter.md>), [override](<https://devfeed.tech/tags/override.md>), [ssh](<https://devfeed.tech/tags/ssh.md>)

### AI overview

Put frequently used SSH settings in `~/.ssh/config` to replace long connection commands with aliases such as `ssh web`; `ProxyJump` can route a private server connection through another host. A `Host *` block sets shared defaults, and the text advises placing it last because SSH uses the first value found for each option. Aliases also work with `scp` and `rsync`, and the config file should be private. For self-hosted apps, place custom Compose changes in `compose.override.yml` so updates can replace the upstream file; Compose merges the override on `up`, and `docker compose config` previews the result. Bash can reuse prior command arguments with `!command:1`, `!command:$`, or `!command:*` for the first, last, or all arguments.

### Source excerpt

Type less, connect faster.

## Win the Agentic Era, Together: Introducing the Docker Navigator Partner Program

DevFeed: [Win the Agentic Era, Together: Introducing the Docker Navigator Partner Program](<https://devfeed.tech/articles/win-the-agentic-era-together-introducing-the-docker-navigator-partner-program-105872.md>)

Original publisher: [Read original article](<https://www.docker.com/blog/docker-navigator-partner-program/>)

Author: Jin Kim

Published: 2026-10-28T13:00:00Z

Content type: release

Language: en

Sources: [Docker](<https://devfeed.tech/sources/docker.md>)

Topics: [ai-governance](<https://devfeed.tech/topics/ai-governance.md>), [Docker AI Governance](<https://devfeed.tech/topics/docker-ai-governance.md>), [Docker](<https://devfeed.tech/topics/docker.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [blueprint](<https://devfeed.tech/tags/blueprint.md>), [blueprint-alliance](<https://devfeed.tech/tags/blueprint-alliance.md>), [company](<https://devfeed.tech/tags/company.md>), [crowdstrike](<https://devfeed.tech/tags/crowdstrike.md>), [databricks](<https://devfeed.tech/tags/databricks.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [deal](<https://devfeed.tech/tags/deal.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-ai-governance](<https://devfeed.tech/tags/docker-ai-governance.md>), [docker-partner](<https://devfeed.tech/tags/docker-partner.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [ge-appliances](<https://devfeed.tech/tags/ge-appliances.md>), [navigator](<https://devfeed.tech/tags/navigator.md>), [partner](<https://devfeed.tech/tags/partner.md>), [partner-program](<https://devfeed.tech/tags/partner-program.md>), [partnership](<https://devfeed.tech/tags/partnership.md>), [partnerships](<https://devfeed.tech/tags/partnerships.md>)

### AI overview

Docker's Navigator Partner Program organizes partners into three tiers: Crew for onboarding and initial deal registration, Explorer for enabled and certified partners actively selling and co-marketing AI governance solutions, and Navigator for strategic co-selling, joint account planning, and reference architecture work. Existing partners enter at a matching tier, which is protected through April 30, 2027 while they work toward requirements. Navigator benefits include a dedicated partner success manager, deal protection, quarterly roadmap briefings, co-funded marketing, and event and advisory opportunities. Partner-sourced registered deals receive the highest tier discount. Until January 31, 2027, approved AI Governance deal registrations earn 10 extra discount points, provided the deals close by April 30, 2027. Partners can register deals, take free sales certification, request marketing funds, and track tier progress in the portal. The article also describes Docker's role in a shared AI-agent security architecture as providing the execution environment, isolation, runtime governance, and supply-chain security.

### Source excerpt

Docker is launching the Navigator Partner Program, with three tiers, co-selling benefits, and a new incentive for every registered AI governance deal.

## Your Docker Host Is Patched. Your Containers Might Not Be.

DevFeed: [Your Docker Host Is Patched. Your Containers Might Not Be.](<https://devfeed.tech/articles/your-docker-host-is-patched-your-containers-might-not-be-100735.md>)

Original publisher: [Read original article](<https://www.virtualizationhowto.com/2026/10/your-docker-host-is-patched-your-containers-might-not-be/>)

Author: Brandon Lee

Published: 2026-10-26T12:22:13Z

Content type: article

Language: en

Sources: [Virtualization Howto](<https://devfeed.tech/sources/virtualization-howto.md>)

Topics: [container-security](<https://devfeed.tech/topics/container-security.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [Docker Compose](<https://devfeed.tech/topics/docker-compose.md>), [image tags vs digests](<https://devfeed.tech/topics/image-tags-vs-digests.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Ubuntu](<https://devfeed.tech/topics/ubuntu.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [about-you](<https://devfeed.tech/tags/about-you.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [announcement](<https://devfeed.tech/tags/announcement.md>), [containers](<https://devfeed.tech/tags/containers.md>), [discussion](<https://devfeed.tech/tags/discussion.md>), [docker](<https://devfeed.tech/tags/docker.md>), [first](<https://devfeed.tech/tags/first.md>), [howto](<https://devfeed.tech/tags/howto.md>), [i](<https://devfeed.tech/tags/i.md>), [patched](<https://devfeed.tech/tags/patched.md>), [patching](<https://devfeed.tech/tags/patching.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [post](<https://devfeed.tech/tags/post.md>), [reddit](<https://devfeed.tech/tags/reddit.md>), [this](<https://devfeed.tech/tags/this.md>), [virtualization](<https://devfeed.tech/tags/virtualization.md>), [vs](<https://devfeed.tech/tags/vs.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

Patching a Docker host does not patch software inside its containers: containers share the host kernel but carry their own filesystems, applications, and dependencies. The article recommends inventorying containers with `docker ps` or `docker compose images`, then checking relevant documentation and advisories and scanning images with Trivy or Grype (also available through Dockhand). A newer image is not automatically safer, so review release notes and interpret scan results. Updating requires pulling and recreating containers with Compose; restarting alone keeps the old image. Tags may be mutable or fixed, while digest pins require changing the referenced digest to select new content. For images you build, rebuild from an updated base, account for pinned references and build cache, then verify the running image and application. A changed image ID confirms replacement, not that a specific vulnerability was fixed. Host, engine, and image updates need separate checks.

### Source excerpt

This past week, I saw some discussion on Reddit around the recent PHP2shell vulnerability and how some were wondering on patching their hosts vs patching their Docker containers. This confusion... The post Your Docker Host Is Patched. Your Containers Might Not Be. appeared first on Virtualization Howto.

## Access Your Version Controlled Configuration from a Docker Container

DevFeed: [Access Your Version Controlled Configuration from a Docker Container](<https://devfeed.tech/articles/access-your-version-controlled-configuration-from-a-docker-container-100792.md>)

Original publisher: [Read original article](<https://spin.atomicobject.com/accessing-your-version-controlled-configuration-from-a-docker-container/>)

Author: Matt Fletcher

Published: 2026-10-26T12:00:45Z

Content type: article

Language: en

Sources: [Atomic Object](<https://devfeed.tech/sources/atomic-object.md>)

Topics: [Docker Compose](<https://devfeed.tech/topics/docker-compose.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [.env](<https://devfeed.tech/topics/dotenv.md>)

Tags: [bind](<https://devfeed.tech/tags/bind.md>), [compose](<https://devfeed.tech/tags/compose.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [directory](<https://devfeed.tech/tags/directory.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-container](<https://devfeed.tech/tags/docker-container.md>), [extracurricular-activities](<https://devfeed.tech/tags/extracurricular-activities.md>), [git](<https://devfeed.tech/tags/git.md>), [homelab](<https://devfeed.tech/tags/homelab.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>)

### AI overview

To avoid keeping separate copies of version-controlled configuration and Docker service data, the author bind-mounts the configuration file directly from the homelab repository into the container. The Gatus Compose example maps `${HOMELAB_DIR}/gatus/config/config.yaml` to `/config/config.yaml:ro`, while its writable data directory comes from `${SERVICE_DATA_DIR}/gatus/data`. The `.env` file sets those host directories separately. The read-only mount fits Gatus because, according to the author, the application has no reason to change its configuration.

### Source excerpt

For years now, I've stubbornly duplicated version-controlled configuration files into my running Docker containers. Meaning, instead of making the files accessible directly by the container, I've been maintaining both the version-controlled file and copies used by the containers. At last, I've found a solution to help avoid the duplication. The problem Right now I keep [...] The post Access Your Version Controlled Configuration from a Docker Container appeared first on Atomic Spin.

## PHP2Shell and eMudhra Patched

DevFeed: [PHP2Shell and eMudhra Patched](<https://devfeed.tech/articles/php2shell-and-emudhra-patched-101227.md>)

Original publisher: [Read original article](<https://www.docker.com/blog/php2shell-and-emudhra-patched/>)

Author: Vishrut Iyengar

Published: 2026-10-23T13:08:08Z

Content type: news

Language: en

Sources: [Docker](<https://devfeed.tech/sources/docker.md>)

Topics: [Docker Hardened Images](<https://devfeed.tech/topics/docker-hardened-images.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [certificates](<https://devfeed.tech/topics/certificates.md>), [trust](<https://devfeed.tech/topics/trust.md>), [Docker](<https://devfeed.tech/topics/docker.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [22](<https://devfeed.tech/tags/22.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [apache](<https://devfeed.tech/tags/apache.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [composer](<https://devfeed.tech/tags/composer.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [container](<https://devfeed.tech/tags/container.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [docker](<https://devfeed.tech/tags/docker.md>), [emudhra](<https://devfeed.tech/tags/emudhra.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [image](<https://devfeed.tech/tags/image.md>), [patched](<https://devfeed.tech/tags/patched.md>), [php](<https://devfeed.tech/tags/php.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [products](<https://devfeed.tech/tags/products.md>), [published](<https://devfeed.tech/tags/published.md>), [security](<https://devfeed.tech/tags/security.md>), [store](<https://devfeed.tech/tags/store.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

The excerpt describes two container foundation risks: PHP2Shell vulnerabilities CVE-2026-109618 and CVE-2026-109619, which it says enable unauthenticated server code execution, and eight eMudhra intermediate certificates with computable private keys that could be used to issue trusted website certificates. Docker says it published a patched dhi.io/php image within 24 hours and rebuilt trust stores across its catalog; by 10pm UTC on October 22, almost all catalog tags had the fixed CA store. It says users should pull current DHI tags and redeploy, rebuild custom images based on DHI, and check the PHP version inside other containers before rebuilding on a patched base. DHI Enterprise customizations are rebuilt automatically when the base is patched. The account says SBOMs can verify the PHP version and CA store for each published tag.

### Source excerpt

PHP2Shell and the eMudhra certificate compromise landed in the same week. Docker published a fixed PHP image within 24 hours and rebuilt the trust store across the catalog.

## Security Update on PHP2Shell: Impact for Docker Customers

DevFeed: [Security Update on PHP2Shell: Impact for Docker Customers](<https://devfeed.tech/articles/security-update-on-php2shell-impact-for-docker-customers-96227.md>)

Original publisher: [Read original article](<https://www.docker.com/blog/security-update-on-php2shell-impact-for-docker-customers/>)

Author: PeiFang Sung

Published: 2026-10-22T17:22:47Z

Content type: news

Language: en

Sources: [Docker](<https://devfeed.tech/sources/docker.md>)

Topics: [vulnerability management](<https://devfeed.tech/topics/vulnerability-management.md>), [Docker Hardened Images](<https://devfeed.tech/topics/docker-hardened-images.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [common vulnerabilities and exposures](<https://devfeed.tech/topics/common-vulnerabilities-and-exposures.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [critical](<https://devfeed.tech/tags/critical.md>), [customers](<https://devfeed.tech/tags/customers.md>), [cve-2026-109618](<https://devfeed.tech/tags/cve-2026-109618.md>), [cve-2026-109619](<https://devfeed.tech/tags/cve-2026-109619.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-hardened-images](<https://devfeed.tech/tags/docker-hardened-images.md>), [docker-hub](<https://devfeed.tech/tags/docker-hub.md>), [end-of-life](<https://devfeed.tech/tags/end-of-life.md>), [eol](<https://devfeed.tech/tags/eol.md>), [packages](<https://devfeed.tech/tags/packages.md>), [patches](<https://devfeed.tech/tags/patches.md>), [php](<https://devfeed.tech/tags/php.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [remote](<https://devfeed.tech/tags/remote.md>), [security](<https://devfeed.tech/tags/security.md>), [update](<https://devfeed.tech/tags/update.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

PHP2Shell (CVE-2026-109618 and CVE-2026-109619) comprises two critical PHP core flaws that can enable remote code execution: one involves uninitialized memory read during cleanup after a request runs out of memory, and the other uses stale state pointing to freed memory. Affected releases span PHP 5.4 onward, including supported 8.2-8.5 and end-of-life 5.x, 7.x, 8.0, and 8.1. The article says upgrading is the only complete mitigation, naming PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12 or later in those branches; if an immediate upgrade is impossible, it recommends taking the system offline. Docker reports that Official Images were updated on Docker Hub and mirrored to Amazon ECR, while Docker Hardened Images were updated on Docker Hub and passed their testing and verification processes. Users of these images should update.

### Source excerpt

On Tuesday, October 20, 2026, Docker began tracking two critical vulnerabilities in PHP, CVE-2026-109618 and CVE-2026-109619, commonly known as PHP2Shell.

## Enhanced CPU Pods Now Support Docker and Network Volumes

DevFeed: [Enhanced CPU Pods Now Support Docker and Network Volumes](<https://devfeed.tech/articles/enhanced-cpu-pods-now-support-docker-and-network-volumes-94557.md>)

Original publisher: [Read original article](<https://www.runpod.io/blog/enhanced-cpu-pods-docker-network>)

Author: Brendan McKeag

Published: 2026-10-22T02:42:59Z

Content type: release

Language: en

Sources: [Runpod Blog.](<https://devfeed.tech/sources/runpod-blog.md>)

Topics: [Docker](<https://devfeed.tech/topics/docker.md>), [self-service](<https://devfeed.tech/topics/self-service.md>), [GPU](<https://devfeed.tech/topics/gpu.md>)

Tags: [cpu](<https://devfeed.tech/tags/cpu.md>), [docker](<https://devfeed.tech/tags/docker.md>), [network](<https://devfeed.tech/tags/network.md>), [pods](<https://devfeed.tech/tags/pods.md>)

### AI overview

Runpod CPU pods now support Docker runtime and network volumes. Docker is presented as consistent with local development, faster to start and lower overhead than Kata Containers, and compatible with standard container tooling and CI/CD workflows. However, Docker-in-Docker is no longer supported; the text recommends pre-building images and storing them in a container registry. Existing setups will continue to work for now, with a planned move of all CPU customers to Docker over time. Network volumes persist independently of pod lifecycles, can be mounted by multiple pods and resized dynamically. The text says moving storage to them can cut storage costs by up to half; stopped pod containers are wiped and incur no applicable charge. Users can configure network volumes through the dashboard. These features are available immediately to CPU pod users.

### Source excerpt

Runpod CPU pods now have Docker runtime and network volume support, giving you more flexibility, better storage options, and smoother dev workflows.

## Don't Hand Claude Your Docker Socket -- Build It a Guarded One

DevFeed: [Don't Hand Claude Your Docker Socket -- Build It a Guarded One](<https://devfeed.tech/articles/don-t-hand-claude-your-docker-socket-build-it-a-guarded-one-93924.md>)

Original publisher: [Read original article](<https://hackernoon.com/dont-hand-claude-your-docker-socket-build-it-a-guarded-one?source=rss>)

Author: Siva Sai Krishna Suryadevara

Published: 2026-10-21T21:17:14Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Docker](<https://devfeed.tech/topics/docker.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Docker Compose](<https://devfeed.tech/topics/docker-compose.md>), [anthropic](<https://devfeed.tech/topics/anthropic.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [ci](<https://devfeed.tech/tags/ci.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-ai](<https://devfeed.tech/tags/claude-ai.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [compose](<https://devfeed.tech/tags/compose.md>), [devops](<https://devfeed.tech/tags/devops.md>), [docker](<https://devfeed.tech/tags/docker.md>), [llm-security](<https://devfeed.tech/tags/llm-security.md>), [llm-tools](<https://devfeed.tech/tags/llm-tools.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [python](<https://devfeed.tech/tags/python.md>), [socket](<https://devfeed.tech/tags/socket.md>)

### AI overview

The Python FastMCP server gives Claude four Docker tools: container listing, inspection, log retrieval with anomaly scanning, and guarded restart. A read-only socket mount does not block Docker API writes, so restart is disabled by default and, when enabled, checked against Docker's resolved container name to prevent ID-based bypasses; a denylist takes precedence over an optional allowlist. Inspection returns environment variable names but withholds values, while log output and scans are capped. The server returns structured errors for daemon failures and keeps diagnostics off stdio JSON-RPC stdout. Its 47 tests mock Docker and do not require a daemon. The article cautions that tool-layer guards are not a security boundary for other processes with socket access, and suggests a filtering proxy for API-level restriction. It also pins the official `mcp` SDK below 2 because the documented FastMCP API changed in 2.x.

### Source excerpt

A Python MCP server that gives Claude read-only access to Docker, with a name-resolved restart guard, secret redaction, and a 47-test mocked suite.

## Do You Really Need Proxmox If You Only Run Docker?

DevFeed: [Do You Really Need Proxmox If You Only Run Docker?](<https://devfeed.tech/articles/do-you-really-need-proxmox-if-you-only-run-docker-92751.md>)

Original publisher: [Read original article](<https://www.virtualizationhowto.com/2026/10/do-you-really-need-proxmox-if-you-only-run-docker/>)

Author: Brandon Lee

Published: 2026-10-21T12:39:52Z

Content type: article

Language: en

Sources: [Virtualization Howto](<https://devfeed.tech/sources/virtualization-howto.md>)

Topics: [Homelab](<https://devfeed.tech/topics/homelab.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [Self-hosted](<https://devfeed.tech/topics/self-hosted.md>)

Tags: [ai-apps](<https://devfeed.tech/tags/ai-apps.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [backup](<https://devfeed.tech/tags/backup.md>), [backups](<https://devfeed.tech/tags/backups.md>), [bridges](<https://devfeed.tech/tags/bridges.md>), [cgroups](<https://devfeed.tech/tags/cgroups.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [compose](<https://devfeed.tech/tags/compose.md>), [containers](<https://devfeed.tech/tags/containers.md>), [coral](<https://devfeed.tech/tags/coral.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [docker](<https://devfeed.tech/tags/docker.md>), [home-lab](<https://devfeed.tech/tags/home-lab.md>), [home-server](<https://devfeed.tech/tags/home-server.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [proxmox](<https://devfeed.tech/tags/proxmox.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [virtualization](<https://devfeed.tech/tags/virtualization.md>)

### AI overview

Docker on bare-metal Linux is a practical choice for a small host running only a few containers when no other operating systems or virtualization experiments are needed; it avoids Proxmox's added management overhead. Running Docker in a Proxmox VM adds centralized host management, snapshots, cloning, VM backups, migration, and stronger workload separation through separate VMs and network configuration. VM backups can simplify full-system recovery, and Proxmox Backup Server adds deduplication and incremental restore points, but VM backups are not automatically database-aware; guest-agent filesystem freezing improves filesystem consistency. Direct Linux may simplify GPU and device access, while Proxmox can require passthrough configuration. Docker in LXC is lightweight but may require nesting and can encounter permissions or storage-driver issues; the article says Proxmox recommends a QEMU VM. The choice depends on workload and desired management, recovery, and isolation capabilities.

### Source excerpt

I think for many home labbers and those running self-hosted infrastructure at home, there are two platforms that account for the majority of where we run applications. That includes Proxmox... The post Do You Really Need Proxmox If You Only Run Docker? appeared first on Virtualization Howto.

## Running Pulumi Neo in a Docker Sandbox: workshop recap

DevFeed: [Running Pulumi Neo in a Docker Sandbox: workshop recap](<https://devfeed.tech/articles/running-pulumi-neo-in-a-docker-sandbox-workshop-recap-92883.md>)

Original publisher: [Read original article](<https://www.pulumi.com/blog/running-pulumi-neo-in-a-docker-sandbox/>)

Author: Mike Coleman

Published: 2026-10-21T00:00:00Z

Content type: article

Language: en

Sources: [Pulumi](<https://devfeed.tech/sources/pulumi.md>)

Topics: [pulumi-neo](<https://devfeed.tech/topics/pulumi-neo.md>), [Docker Sandboxes](<https://devfeed.tech/topics/docker-sandboxes.md>), [pulumi](<https://devfeed.tech/topics/pulumi.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [personal access token](<https://devfeed.tech/topics/personal-access-token.md>), [World models](<https://devfeed.tech/topics/world-models.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [api](<https://devfeed.tech/tags/api.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [community](<https://devfeed.tech/tags/community.md>), [data](<https://devfeed.tech/tags/data.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-sandbox](<https://devfeed.tech/tags/docker-sandbox.md>), [esc](<https://devfeed.tech/tags/esc.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [neo](<https://devfeed.tech/tags/neo.md>), [policy](<https://devfeed.tech/tags/policy.md>), [production](<https://devfeed.tech/tags/production.md>), [prompt](<https://devfeed.tech/tags/prompt.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [pulumi](<https://devfeed.tech/tags/pulumi.md>), [pulumi-neo](<https://devfeed.tech/tags/pulumi-neo.md>), [recap](<https://devfeed.tech/tags/recap.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [security](<https://devfeed.tech/tags/security.md>), [token](<https://devfeed.tech/tags/token.md>), [workshop](<https://devfeed.tech/tags/workshop.md>)

### AI overview

The workshop describes running Pulumi Neo in a Docker Sandbox with controls outside the agent's prompt. Neo runs in an isolated microVM with access limited to mounted files and permitted network hosts; a proxy injects the Pulumi token so Neo does not hold the real credential. Pulumi governs permissions and approvals: manual asks before each tool call, balanced before `pulumi up`, and auto never asks. Read-only blocks Pulumi Cloud writes but does not prevent access to ESC environments or their cloud accounts; role permissions must restrict environment access. Preventative Pulumi Policies can block violations, `protect: true` can stop deletion of protected resources, and ESC can issue short-lived AWS credentials, which limit leak damage but do not prevent it. Docker's network proxy can deny unapproved hosts, though allowed hosts still receive what Neo sends. The excerpt recommends starting with a locked-down network preset and balanced approvals near production. Centralized Docker sandbox controls are paid; local sandboxes and the `sbx` CLI are free. The final teardown demonstration was not completed.

### Source excerpt

The more an agent can do on its own, the more infrastructure work you can hand it, as long as its limits hold when it gets something wrong. In April, they didn't hold for PocketOS. A coding agent on a routine staging task deleted the company's production volume in 9 seconds. According to founder Jer Crane's account, it used an API token it found in an unrelated file. Its explanation afterward: "I guessed that deleting a staging volume via the API would be scoped to staging only. I didn't verify." Railway recovered the data two days later. The agent had been told not to. "System prompts are advisory, not enforcing," Crane wrote afterward. If the prompt can't stop an agent, the limits have to sit where the agent can't negotiate with them. That was the premise of Neo in a Docker Sandbox, the workshop Adam Gordon Bell and I ran with Mike Coleman from Docker. So we gave Pulumi Neo two layers. The first is a Docker Sandbox. Neo runs in its own microVM and reaches only the files and hosts we allow. The Pulumi token gets injected by a proxy on the way out, so Neo never holds the real credential. The second is Pulumi itself, which decides what Neo may change and when it has to ask. With both in place, you can let Neo work without approving every step. For why YOLO mode belongs in a sandbox at all, see my August post. Mike Coleman is a Principal Solutions Architect at Docker. His running joke is that agents "want to be helpful". It happens in his own demos: Mike Coleman I talk to people about agents a lot. They just really want to please you. I don't know how many times I've done a demo [of] governance for MCP servers, and I'll be like, "Can you write to my Notion page?" And there will be a policy applied to the sandbox that says it can't. But I have a connector enabled in Claude somewhere. And it's like, "Well, not with that MCP server, but I can use this thing over here to do it." Mike's answer is to close those doors before the agent finds them: Mike Coleman The more you c

## Parsing JSON-structured Docker logs with the OpenTelemetry Collector

DevFeed: [Parsing JSON-structured Docker logs with the OpenTelemetry Collector](<https://devfeed.tech/articles/parsing-json-structured-docker-logs-with-the-opentelemetry-collector-90027.md>)

Original publisher: [Read original article](<https://dev.37signals.com/parsing-json-docker-logs-with-opentelemetry-collector/>)

Author: Lewis Buckley

Published: 2026-10-19T17:00:00Z

Content type: tutorial

Language: en

Sources: [37signals Dev](<https://devfeed.tech/sources/37signals-dev.md>)

Topics: [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [JSON](<https://devfeed.tech/topics/json.md>), [Docker](<https://devfeed.tech/topics/docker.md>)

Tags: [docker](<https://devfeed.tech/tags/docker.md>), [json](<https://devfeed.tech/tags/json.md>), [logs](<https://devfeed.tech/tags/logs.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [opentelemetry-collector](<https://devfeed.tech/tags/opentelemetry-collector.md>), [parsing](<https://devfeed.tech/tags/parsing.md>)

### AI overview

The article explains how to configure the OpenTelemetry Collector's filelog receiver to process Docker JSON logs. It describes unwrapping Docker's JSON envelope, filtering plain-text lines, recombining entries split at 16KB boundaries, and parsing the application's JSON. It also details two configuration mistakes that caused lost logs and how sample-file checks exposed them.

### Source excerpt

How we use the filelog receiver's operator chain to parse, recombine, and route JSON-structured log lines from Docker containers.

[Next page](<https://devfeed.tech/topics/docker.md?cursor=WyIyMDI2LTEwLTE5VDE3OjAwOjAwKzAwOjAwIiwgIjhjNmQ0ZmZiLTU5ZmYtNGJjMi05ZDJhLTI0ZmUwNjY3YTRhNSJd>)