We're excited to announce a major evolution in how we deliver Docker Desktop updates to you. Starting with Docker Desktop release 4.45.0 on 28 August we're moving to releases every two weeks, with the goal of reaching weekly releases by the end of 2025. Why We're Making This Change You've told us you want faster
In a previous blog post I presented Portainer, a simple Docker stacks management interface. One of the nice features of Portainer is the possibility to create webhooks to automatically update existing stacks. In this post I'll show how to combine this feature with GitLab pipelines to implement continuous deployment of Docker stacks.
Docker has released fixes to address a critical security flaw affecting the Docker Desktop app for Windows and macOS that could potentially allow an attacker to break out of the confines of a container. The vulnerability, tracked as CVE-2025-9074, carries a CVSS score of 9.3 out of 10.0. It has been addressed in version 4.44.3. "A malicious container running on Docker Desktop could access the
A critical vulnerability in Docker Desktop for Windows and macOS allows compromising the host by running a malicious container, even if the Enhanced Container Isolation (ECI) protection is active.
Docker and containers have revolutionized the way we build, ship, and run applications! However, managing multiple containers and services can become increasingly complex. That's where Portainer comes in! This powerful and intuitive container management web application makes it easy to deploy, manage, and monitor your Docker environments.
A newly disclosed vulnerability in Docker Desktop for Windows has revealed how a simple Server-Side Request Forgery (SSRF) attack could lead to complete host system compromise. CVE-2025-9074, discovered by Felix Boulet and reported on August 21, 2025, affects all Docker Desktop versions prior to 4.44.3 and demonstrates how container isolation can be completely bypassed through
submitted by /u/digicat [link] [comments]
submitted by /u/Wanazabadee [link] [comments]
submitted by /u/Wanazabadee [link] [comments]
Every developer remembers their first docker run hello-world. The mix of excitement and wonder as that simple command pulls an image, creates a container, and displays a friendly message. But what if AI could make that experience even better? As a technical writer on Docker's Docs team, I spend my days thinking about developer experience.
Docker periodically highlights blog posts featuring use cases and success stories from Docker partners and practitioners. This story was contributed by Dylen Turnbull and Timo Stark. With over 29 years in enterprise and open-source software development, Dylen Turnbull has held roles at Symantec, Veritas, F5 Networks, and most recently as a Developer Advocate for NGINX.
Building AI agents in the real world often involves more than just making model calls - it requires integrating with external tools, handling complex workflows, and ensuring the solution can scale in production. In this post, we'll walk through a real-world developer setup for creating an agent using the Docker MCP Toolkit. To make things
Power doesn't just disappear in one big breach. It slips away in the small stuff - a patch that's missed, a setting that's wrong, a system no one is watching. Security usually doesn't fail all at once; it breaks slowly, then suddenly. Staying safe isn't about knowing everything - it's about acting fast and clear before problems pile up. Clarity keeps control. Hesitation creates risk. Here are this
Recently introduced, there might be a better way to run Kali directly using Apple's new Container framework. It's lightweight and seems to work much better compared to Docker. Due to the lack of tutorials showcasing how to run and properly achieve full persistency of Kali with same container even after start, stop, restart. I've created a repo with ready made setup scripts, aliases and instructions to do so easily: https://github.com/n0mi1k/kali-on-apple-container submitted by /u/n0mi1k [link]...