Skip to main content
AmigoFish

Docker

DockerVideo

Format:
YouTube channel
New videos:
Irregular
Typical length:
about 35 minutes, not counting Shorts
Latest video:
Not rated yet

About this show

Docker is the platform at the center of how intelligent software gets built. For more than a decade, Docker has helped millions of developers and thousands of organizations build, ship, and run software consistently across any environment. Today, Docker is extending that same trust to the AI era, giving builders and organizations the confidence to adopt any model, tool, or agent without compromising security, governance, or control. Learn more at www.docker.com.

Covers: software development, AI agents, docker sandboxes, AI security, voice AI, developer tools, model context protocol, agentic engineering

Videos come from the channel's public YouTube feed. The artwork is the newest video thumbnail. Last updated . Names, artwork and text belong to their publishers.

Recently on this show

Summary of recent videos, drawn from the publisher's feed.

A Docker channel about creating, delivering and running software, increasingly around AI agents, security and control. Recent videos cover voice AI bots for customer calls, isolated sandboxes that give agents temporary company access, and AI joining development teams.

Report a problem with this summary

Cosmos

Similar in subject

  • Amazon Web Services
    Both cover: developer tools, software development, ai agents
  • Google Cloud Tech
    Both cover: developer tools, software development, ai agents
  • Udacity
    Both cover: ai security, software development, ai agents

See the full Cosmos

Similar shows

See all Technology shows

Videos

  • How does shipping lead to burnout? #ai #docker #aicoding

    · 1 min

    Voice AI is changing how businesses answer calls, qualify leads, and support customers. But building a voice bot that actually works in production takes much more than connecting an AI model to a phone line. In this episode of Ship Happens, host Per Krogslund talks with Seth Wright from CTM (formerly Call Tracking Metrics) about the evolution from call tracking and marketing attribution to configurable telephony platforms powered by AI. CTM's platform helps businesses manage calls, texts, routing, call trees, voice bots, and handoffs to human teams. AI adds another layer of intelligence: enriching call data, identifying high-intent leads, triggering follow-ups, and building customer context that helps systems make better decisions about what should happen next. Seth explains why modern large language models have changed what's possible in voice systems—and why the engineering challenge is far from solved. A voice interaction has to feel immediate. That means minimizing latency, preparing data before it's needed, and designing workflows that can handle real-time decisions such as booking appointments or escalating urgent issues. The conversation goes beyond the voice interface to explore the work required to make these systems dependable: testing realistic conversations, replaying failures, improving observability, explaining AI-driven decisions, and building evaluation pipelines that catch problems before they reach customers. Because when a voice AI system is slow, unreliable, or confidently wrong, customers don't care how impressive the demo looked. Building better voice AI isn't just about making machines talk. It's about engineering systems that listen, understand context, act quickly, and know when to bring in a human. What You'll Learn: • How CTM evolved from call tracking and marketing attribution into a configurable communications platform • How AI can enrich call data, identify hot leads, and trigger follow-up actions • Why voice bots need clear pathways between automation and human support • How LLMs changed the architecture of voice AI • Why latency is one of the defining challenges of real-time voice systems • How preloading customer and appointment data can make conversations faster • How customer memory records can improve routing and personalization • Why explainability matters for lead scoring, sentiment analysis, and automated decisions • How to test, replay, debug, and evaluate AI-driven conversations • Why observability and evaluation pipelines are essential for reliable production systems • How engineering teams can adopt AI without sacrificing quality or burning out • What new engineers should understand about building software in an AI-driven world Key Takeaways: • A great voice bot depends on the whole system. The conversational model is only one part of the experience. Routing, data access, integrations, escalation paths, and operational reliability all matter. • Latency is a product decision. In a live conversation, even a technically correct response can feel broken if it takes too long. Architecture and data preparation directly shape the customer experience. • Context makes automation more useful. Enriched call data and customer memory can help systems route conversations, recognize opportunities, and respond more appropriately. • Human handoffs are part of good automation. Reliable systems need to recognize when a situation calls for human judgment or urgent escalation—not simply keep a conversation going. • AI needs measurable quality controls. Testing, observability, conversation replay, explainability, and evaluation pipelines help teams identify failures and improve performance before problems compound. • Production engineering is still engineering. AI can make it easier to build new capabilities, but teams still need to manage complexity, evaluate tradeoffs, maintain reliability, and build systems people can trust.

    Not rated yet
  • How do we define a high quality lead? #ai #docker #aicustomerservice

    · 1 min

    Voice AI is changing how businesses answer calls, qualify leads, and support customers. But building a voice bot that actually works in production takes much more than connecting an AI model to a phone line. In this episode of Ship Happens, host Per Krogslund talks with Seth Wright from CTM (formerly Call Tracking Metrics) about the evolution from call tracking and marketing attribution to configurable telephony platforms powered by AI. CTM's platform helps businesses manage calls, texts, routing, call trees, voice bots, and handoffs to human teams. AI adds another layer of intelligence: enriching call data, identifying high-intent leads, triggering follow-ups, and building customer context that helps systems make better decisions about what should happen next. Seth explains why modern large language models have changed what's possible in voice systems—and why the engineering challenge is far from solved. A voice interaction has to feel immediate. That means minimizing latency, preparing data before it's needed, and designing workflows that can handle real-time decisions such as booking appointments or escalating urgent issues. The conversation goes beyond the voice interface to explore the work required to make these systems dependable: testing realistic conversations, replaying failures, improving observability, explaining AI-driven decisions, and building evaluation pipelines that catch problems before they reach customers. Because when a voice AI system is slow, unreliable, or confidently wrong, customers don't care how impressive the demo looked. Building better voice AI isn't just about making machines talk. It's about engineering systems that listen, understand context, act quickly, and know when to bring in a human. What You'll Learn: • How CTM evolved from call tracking and marketing attribution into a configurable communications platform • How AI can enrich call data, identify hot leads, and trigger follow-up actions • Why voice bots need clear pathways between automation and human support • How LLMs changed the architecture of voice AI • Why latency is one of the defining challenges of real-time voice systems • How preloading customer and appointment data can make conversations faster • How customer memory records can improve routing and personalization • Why explainability matters for lead scoring, sentiment analysis, and automated decisions • How to test, replay, debug, and evaluate AI-driven conversations • Why observability and evaluation pipelines are essential for reliable production systems • How engineering teams can adopt AI without sacrificing quality or burning out • What new engineers should understand about building software in an AI-driven world Key Takeaways: • A great voice bot depends on the whole system. The conversational model is only one part of the experience. Routing, data access, integrations, escalation paths, and operational reliability all matter. • Latency is a product decision. In a live conversation, even a technically correct response can feel broken if it takes too long. Architecture and data preparation directly shape the customer experience. • Context makes automation more useful. Enriched call data and customer memory can help systems route conversations, recognize opportunities, and respond more appropriately. • Human handoffs are part of good automation. Reliable systems need to recognize when a situation calls for human judgment or urgent escalation—not simply keep a conversation going. • AI needs measurable quality controls. Testing, observability, conversation replay, explainability, and evaluation pipelines help teams identify failures and improve performance before problems compound. • Production engineering is still engineering. AI can make it easier to build new capabilities, but teams still need to manage complexity, evaluate tradeoffs, maintain reliability, and build systems people can trust.

    Not rated yet
  • Beyond the Voice Bot: Engineering Real Time Customer Conversations

    · 50 min

    Voice AI is changing how businesses answer calls, qualify leads, and support customers. But building a voice bot that actually works in production takes much more than connecting an AI model to a phone line. In this episode of Ship Happens, host Per Krogslund talks with Seth Wright from CTM (formerly Call Tracking Metrics) about the evolution from call tracking and marketing attribution to configurable telephony platforms powered by AI. CTM's platform helps businesses manage calls, texts, routing, call trees, voice bots, and handoffs to human teams. AI adds another layer of intelligence: enriching call data, identifying high-intent leads, triggering follow-ups, and building customer context that helps systems make better decisions about what should happen next. Seth explains why modern large language models have changed what's possible in voice systems—and why the engineering challenge is far from solved. A voice interaction has to feel immediate. That means minimizing latency, preparing data before it's needed, and designing workflows that can handle real-time decisions such as booking appointments or escalating urgent issues. The conversation goes beyond the voice interface to explore the work required to make these systems dependable: testing realistic conversations, replaying failures, improving observability, explaining AI-driven decisions, and building evaluation pipelines that catch problems before they reach customers. Because when a voice AI system is slow, unreliable, or confidently wrong, customers don't care how impressive the demo looked. Building better voice AI isn't just about making machines talk. It's about engineering systems that listen, understand context, act quickly, and know when to bring in a human. What You'll Learn: • How CTM evolved from call tracking and marketing attribution into a configurable communications platform • How AI can enrich call data, identify hot leads, and trigger follow-up actions • Why voice bots need clear pathways between automation and human support • How LLMs changed the architecture of voice AI • Why latency is one of the defining challenges of real-time voice systems • How preloading customer and appointment data can make conversations faster • How customer memory records can improve routing and personalization • Why explainability matters for lead scoring, sentiment analysis, and automated decisions • How to test, replay, debug, and evaluate AI-driven conversations • Why observability and evaluation pipelines are essential for reliable production systems • How engineering teams can adopt AI without sacrificing quality or burning out • What new engineers should understand about building software in an AI-driven world Chapters: 00:00 Answer Fast or Lose 01:01 Meet the Guest 01:33 What CTM Does 03:54 AI for Call Insights 05:18 IVRs and Voice Bots 06:18 Why Voice Changed 09:35 Voice Value and Speed 12:03 Engineering Voice Systems 13:54 Voice UI Primitives 17:46 Explainable Lead Scoring 20:54 Decision Models and Sentiment 23:06 Model Choices and Latency 27:32 Real-Time Data Loading 29:09 Testing and Debugging 33:33 Evaluation Pipelines and Teams 42:08 Engineering Craft in AI 44:27 Advice for New Engineers 48:44 Future Assumptions 49:55 Wrap Up and Goodbye Key Takeaways: • A great voice bot depends on the whole system. The conversational model is only one part of the experience. Routing, data access, integrations, escalation paths, and operational reliability all matter. • Latency is a product decision. In a live conversation, even a technically correct response can feel broken if it takes too long. Architecture and data preparation directly shape the customer experience. • Context makes automation more useful. Enriched call data and customer memory can help systems route conversations, recognize opportunities, and respond more appropriately. • Human handoffs are part of good automation. Reliable systems need to recognize when a situation calls for human judgment…

    Not rated yet
  • Safely Giving AI Agents Access to Your Company with Docker Sandboxes | Mark Lechner (CISO, Docker)

    · 33 min

    Agents become more useful when they can access company knowledge, but permanent access creates unnecessary risk. In this talk, I’ll show how to combine Docker Sandboxes with a Cognee Company Brain to build safer agentic workflows. An agent runs inside an isolated sandbox, receives temporary access to company knowledge only when needed, retrieves relevant context, completes its task, and has that access removed. We’ll explore how this pattern separates execution, memory, and permissions, reducing exposure of credentials and sensitive data while enabling powerful AI workflows. Attendees will leave with a practical architecture to give agents safer access to enterprise knowledge. ____ Mark Lechner is CISO at Docker, where he leads security across the platform millions of developers use to build, ship, and run software - including the agentic workloads reshaping modern engineering. Before Docker, he was CISO at DeepOpinion/Otera driving enterprise AI and LLM agentic security, CISO at Bitpanda scaling security through Europe's largest crypto platform, and Head of Cybersecurity at Solaris Bank. Before that he spent nearly a decade at Morgan Stanley in various security roles including the global leadership of security tooling. His focus today: supply chain integrity, agentic AI security, and secure-by-default developer platforms. He is based in Berlin.--

    Not rated yet
  • WeAreDevelopers - Govern the Runtime, Not the Agent with Tushar Jain (CTO, Docker)

    · 31 min

    The industry is converging on a multi-agent, multi-model world. Teams are landing on a few facts at once: the best model changes every couple of months, it makes no economic sense to call a frontier model to classify a ticket, and your unique workflows may sometimes need custom models. So you end up running many models across many harnesses. This makes trust the defining challenge of today. While harnesses do ship some guardrails, each one governs only its own traffic, and we are already seeing where that breaks down. Agents route around rails the harness cannot see, and the rails themselves shift underneath you whenever the model vendor ships an update. Safety cannot depend on the agent making the right decision, or on someone else's release schedule. Tushar Jain, CTO at Docker, makes the case for a meta-runtime: the layer below all your harnesses, covering agent execution, tool calls, credential usage, scoped permissions, token spend. A meta-runtime makes it possible to control and have visibility into all your agents, no matter what model or what harness. Tushar Jain is the Chief Technology Officer at Docker, leading the work of building trust into the infrastructure agents run on. He is responsible for advancing systems that let AI agents operate autonomously without gaining uncontrolled access to sensitive data and services. His work applies Docker's experience with portable software to an emerging challenge: enforcing security boundaries around agents whose plans and permissions can change while they work.

    Not rated yet
  • What Does an AI Advertising Agent Actually Do? #docker #ai #aiadvertising

    · 1 min

    What happens when AI stops being a tool engineers use and starts becoming a member of the development team? In this episode of Ship Happens, host Per Krogslund sits down with Scott Gale, CTO and co-founder of Fluency, to explore the rise of agentic engineering and how AI is changing the way software gets built, tested, deployed, and maintained. Fluency has spent years automating digital advertising across platforms including Google, Meta, Amazon, TikTok, and DSPs. Now, the company is bringing AI agents into that workflow—using them to advise customers, enforce compliance, surface optimization opportunities, and help engineers tackle software development itself. Scott walks Per through what that looks like in practice. At Fluency, engineers can use agents to triage bugs, investigate problems, propose fixes, and open pull requests. But the agents don't get the final say. Humans review changes before they make it into production. That human layer becomes especially important when you're operating systems responsible for roughly $3 billion in annual ad spend. Scott explains why agentic engineering requires more than powerful models: it requires strong DevOps foundations, clear guardrails, reliable processes, and a thoughtful approach to what should—and shouldn't—be automated. The conversation also tackles the bigger questions facing engineering teams: If AI can write more of the code, what should engineers spend their time doing? When should you build versus buy? And as AI makes coding easier, does the real engineering challenge shift toward judgment, architecture, and directing intelligent systems? AI may be joining the dev team. The question is what the rest of the team does differently because it's there. What You'll Learn: • What “agentic engineering” looks like in a real production environment • How AI agents can become part of an engineering team's workflow • How Fluency moved from deterministic templates toward AI-powered agents • What happens when agents triage bugs and propose code changes • Why human review remains critical for production systems • How engineers' roles change when AI can write and modify code • Why deterministic processes still matter in agentic systems • The DevOps foundations needed to safely deploy AI agents • How to design effective guardrails around autonomous workflows • How to think about build-versus-buy decisions in an AI-first world • Why token costs and long-term ownership are becoming important engineering considerations • Whether engineers should still be writing code—and what they may increasingly do instead

    Not rated yet
  • What's the Expensive Part of Writing Software Today? #docker #ai #aiadvertising

    · 1 min

    What happens when AI stops being a tool engineers use and starts becoming a member of the development team? In this episode of Ship Happens, host Per Krogslund sits down with Scott Gale, CTO and co-founder of Fluency, to explore the rise of agentic engineering and how AI is changing the way software gets built, tested, deployed, and maintained. Fluency has spent years automating digital advertising across platforms including Google, Meta, Amazon, TikTok, and DSPs. Now, the company is bringing AI agents into that workflow—using them to advise customers, enforce compliance, surface optimization opportunities, and help engineers tackle software development itself. Scott walks Per through what that looks like in practice. At Fluency, engineers can use agents to triage bugs, investigate problems, propose fixes, and open pull requests. But the agents don't get the final say. Humans review changes before they make it into production. That human layer becomes especially important when you're operating systems responsible for roughly $3 billion in annual ad spend. Scott explains why agentic engineering requires more than powerful models: it requires strong DevOps foundations, clear guardrails, reliable processes, and a thoughtful approach to what should—and shouldn't—be automated. The conversation also tackles the bigger questions facing engineering teams: If AI can write more of the code, what should engineers spend their time doing? When should you build versus buy? And as AI makes coding easier, does the real engineering challenge shift toward judgment, architecture, and directing intelligent systems? AI may be joining the dev team. The question is what the rest of the team does differently because it's there. What You'll Learn: • What “agentic engineering” looks like in a real production environment • How AI agents can become part of an engineering team's workflow • How Fluency moved from deterministic templates toward AI-powered agents • What happens when agents triage bugs and propose code changes • Why human review remains critical for production systems • How engineers' roles change when AI can write and modify code • Why deterministic processes still matter in agentic systems • The DevOps foundations needed to safely deploy AI agents • How to design effective guardrails around autonomous workflows • How to think about build-versus-buy decisions in an AI-first world • Why token costs and long-term ownership are becoming important engineering considerations • Whether engineers should still be writing code—and what they may increasingly do instead

    Not rated yet
  • Agentic Engineering: What Happens When AI Joins the Dev Team?

    · 36 min

    What happens when AI stops being a tool engineers use and starts becoming a member of the development team? In this episode of Ship Happens, host Per Krogslund sits down with Scott Gale, CTO and co-founder of Fluency, to explore the rise of agentic engineering and how AI is changing the way software gets built, tested, deployed, and maintained. Fluency has spent years automating digital advertising across platforms including Google, Meta, Amazon, TikTok, and DSPs. Now, the company is bringing AI agents into that workflow—using them to advise customers, enforce compliance, surface optimization opportunities, and help engineers tackle software development itself. Scott walks Per through what that looks like in practice. At Fluency, engineers can use agents to triage bugs, investigate problems, propose fixes, and open pull requests. But the agents don't get the final say. Humans review changes before they make it into production. That human layer becomes especially important when you're operating systems responsible for roughly $3 billion in annual ad spend. Scott explains why agentic engineering requires more than powerful models: it requires strong DevOps foundations, clear guardrails, reliable processes, and a thoughtful approach to what should—and shouldn't—be automated. The conversation also tackles the bigger questions facing engineering teams: If AI can write more of the code, what should engineers spend their time doing? When should you build versus buy? And as AI makes coding easier, does the real engineering challenge shift toward judgment, architecture, and directing intelligent systems? AI may be joining the dev team. The question is what the rest of the team does differently because it's there. What You'll Learn: • What “agentic engineering” looks like in a real production environment • How AI agents can become part of an engineering team's workflow • How Fluency moved from deterministic templates toward AI-powered agents • What happens when agents triage bugs and propose code changes • Why human review remains critical for production systems • How engineers' roles change when AI can write and modify code • Why deterministic processes still matter in agentic systems • The DevOps foundations needed to safely deploy AI agents • How to design effective guardrails around autonomous workflows • How to think about build-versus-buy decisions in an AI-first world • Why token costs and long-term ownership are becoming important engineering considerations • Whether engineers should still be writing code—and what they may increasingly do instead Episode Chapters 00:00 When AI Code Fails 01:03 Meet Fluency CTO Scott Gale 02:30 Fluency Origins 06:06 From Templates to Agents 07:42 Human Control vs. Autopilot 10:00 Automation vs. Persuasion 11:27 Engineers Managing Agents 17:33 Guardrails and DevOps Layers 28:00 Build, Buy, Standardize 32:11 What Gets Expensive Now 33:29 Should You Still Code? 35:24 Closing

    Not rated yet
  • Connect Docker Sandboxes to MCP in 5 Steps #docker #mcp #dockersandboxes

    · 1 min

    Connect Docker Sandboxes to MCP and external tools! In this video, I show you how to connect Claude running inside a Docker Sandbox to services like Notion and GitHub using Docker’s MCP Gateway. You’ll see how to register an MCP server, control which tools are available inside a sandbox, and use Claude to retrieve feature requests from Notion and turn one into a real GitHub issue. I’ll also demonstrate the difference between static and dynamic MCP access and show how Docker gives you control over which external capabilities an AI agent can use. By combining Docker Sandboxes with MCP, you can keep your agent isolated while still giving it controlled access to the tools and services that are part of your development workflow. 🔥 Want More Docker Content? If you found this demo exciting, hit that like button and subscribe for more! We’ve got even more Docker demos coming your way in this ongoing series showcasing new tools, integrations, and powerful workflows to level up your projects. Stay tuned! Where to find Docker: Docker: https://www.docker.com/ LinkedIn: https://www.linkedin.com/company/docker Bluesky: https://bsky.app/profile/docker.com X: @docker Instagram: @dockerinc

    Not rated yet
  • How to Connect Docker Sandboxes to MCP and External Tools

    · 8 min

    Connect Docker Sandboxes to MCP and external tools! In this video, I show you how to connect Claude running inside a Docker Sandbox to services like Notion and GitHub using Docker’s MCP Gateway. You’ll see how to register an MCP server, control which tools are available inside a sandbox, and use Claude to retrieve feature requests from Notion and turn one into a real GitHub issue. I’ll also demonstrate the difference between static and dynamic MCP access and show how Docker gives you control over which external capabilities an AI agent can use. By combining Docker Sandboxes with MCP, you can keep your agent isolated while still giving it controlled access to the tools and services that are part of your development workflow. 🔥 Want More Docker Content? If you found this demo exciting, hit that like button and subscribe for more! We’ve got even more Docker demos coming your way in this ongoing series showcasing new tools, integrations, and powerful workflows to level up your projects. Stay tuned! Where to find Docker: Docker: https://www.docker.com/ LinkedIn: https://www.linkedin.com/company/docker Bluesky: https://bsky.app/profile/docker.com X: @docker Instagram: @dockerinc

    Not rated yet
  • Kelsey Hightower: ZTA: Zero Token Architecture -- Docker x WeAreDevelopers

    · 35 min

    ZTA: Zero Token Architecture with Kelsey Hightower @ WeAreDevelopers 2026 -- About This Session Infer once; run everywhere. While burning tokens is being celebrated as a sign of productivity, it’s irresponsible to ignore the fundamentals around efficiency, and pragmatic engineering. This talk aims to bring us back to reality. -- Kelsey is a former Google Distinguished Engineer, open source contributor, investor, author, and minimalist trying to figure out what comes next. Kelsey believes the fundamentals are worth learning even if the machines can do it.

    Not rated yet
  • WeAreDevelopers - Opening Keynote with Mark Cavage (President and COO of Docker)

    · 31 min

    Manufacturing trust: speed and safety in the age of agents -- About This Session Agents have made building software faster, but infrastructure has to catch up. In the world we now live in, developers review code they did not write, or don’t review it at all. An agent can generate and execute changes faster than any person or team can inspect them. And while prompts and skills can steer an agent, they cannot guarantee trust. For decades, we established trust in software through people and process: shared context, code review, CI, and ownership, all of which run at human speed. Agents do not. If a person has to watch every step, the agent is not autonomous, and most of the promised speed disappears. Trust has to move into the system itself. Mark Cavage, President and COO of Docker, makes the case for enforceable boundaries around nondeterministic agents. When you can’t inherit trust, you have to manufacture it. That means isolating where agents run, limiting what they can reach, recording what they do, and making failures reproducible. These controls are not the price of moving fast. They are what let you move fast without losing control. The test for an agent platform is simple: Does security hold when the prompt does not? Can you audit what happened? Can you switch models and tools without rebuilding the trust layer? The goal is not to trust the agent. It is to trust the system around it enough to close your laptop, while the work continues. -- Mark Cavage is President of Docker. Over a 25-year career spanning AWS, Oracle, Heroku, Stripe, and Docker, he has moved from senior and principal engineer to engineering leader to business leader. That arc gives him a perspective few executives have: he has written the systems, led the teams building them, and run the businesses that depend on them. Today, Mark is leading Docker through the shift to agentic software development, helping more than 20 million developers give AI agents real autonomy while keeping control of their code, credentials, and infrastructure.

    Not rated yet
  • Don’t Let AI Go Rogue: Human Governance for Agentic Systems

    · 42 min

    As AI systems become more capable of reasoning, using tools, accessing data, and taking action on their own, a new question is becoming impossible to ignore: how much autonomy should we actually give them? In this episode of Ship Happens, host Per Krogslund sits down with Justin Kuiper, Lead Architect at Future Tech, to explore the security and governance challenges of agentic AI—and what engineers can do to keep increasingly autonomous systems within safe and understandable boundaries. With a background in Air Force space operations and cybersecurity, Justin brings lessons from mission-critical systems to the rapidly evolving world of AI. He explains how different environments prioritize availability, confidentiality, and mission assurance, and why those tradeoffs become even more important when software can make decisions and take actions with real-world consequences. Per and Justin dig into the importance of human governance, least privilege, agent identity, observability, break-glass controls, and specification engineering. They explore the risk of “confident misalignment”—when an AI system confidently pursues an outcome that isn't actually what its human operators intended—and why giving agents more capability doesn't mean giving them unlimited authority. The conversation also looks at AI in space, data sovereignty, model selection, token economics, and the emerging challenge of securing entire agent ecosystems rather than individual applications. The practical message for builders is clear: define what your agents are allowed to do, know who is responsible for their actions, constrain their access, observe what they're doing, document the system, and keep humans in control when the stakes are high. Because autonomous software can move fast. Your governance needs to move with it. What You’ll Learn: • Why agentic AI introduces a different class of security and governance challenges • What space systems can teach us about designing software for high-consequence environments • Why human governance becomes more important as AI systems become more autonomous • What “confident misalignment” means and why it can be dangerous • How least privilege can be applied to AI agents and the tools they use • Why every agent needs a clear identity and an accountable owner • How observability and break-glass controls can help keep autonomous workflows under control • Why the workflow—not just the individual application—can become the security problem • How specification engineering can create stronger guardrails around AI behavior • What data sovereignty means in an increasingly agent-driven ecosystem • How model selection and token economics factor into AI architecture • Why organizations need to decide on an agentic operating model before deploying autonomous systems • Why “fail closed” can be an important principle for high-consequence AI systems About Justin Kuiper: Justin Kuiper is a Lead Architect at Future Tech with a background in Air Force space operations and cybersecurity. His experience working with complex, mission-critical systems gives him a unique perspective on the challenges of securing increasingly autonomous technology. In this episode, Justin connects lessons from space systems and cybersecurity with the emerging world of agentic AI, exploring how engineers can build systems that are not only capable, but also constrained, observable, and accountable. Chapters: 00:00 Satan in the Workflow 01:25 Meet Justin Kuiper 03:22 Securing Software in Space 06:06 AI Security and Black Boxes 11:33 Human Governance for Agents 13:51 Least Privilege for Tools 16:03 Agent Identity and Accountability 17:27 Agents in Production Workflows 19:55 Confident Misalignment Risks 20:52 Accountability for AI Weapons 22:12 Technology That Explores 22:38 Balancing Human Control 24:05 Losing Institutional Know-How 26:19 Specification Engineering Guardrails 26:52 AI in Space: The Timeline 27:44 Model Choices and Sovereignty 28:44 Tokenomics…

    Not rated yet
  • What happens when AI is more than just code? #ai #docker #aicoding

    · 1 min

    As AI systems become more capable of reasoning, using tools, accessing data, and taking action on their own, a new question is becoming impossible to ignore: how much autonomy should we actually give them? In this episode of Ship Happens, host Per Krogslund sits down with Justin Kuiper, Lead Architect at Future Tech, to explore the security and governance challenges of agentic AI—and what engineers can do to keep increasingly autonomous systems within safe and understandable boundaries. With a background in Air Force space operations and cybersecurity, Justin brings lessons from mission-critical systems to the rapidly evolving world of AI. He explains how different environments prioritize availability, confidentiality, and mission assurance, and why those tradeoffs become even more important when software can make decisions and take actions with real-world consequences. Per and Justin dig into the importance of human governance, least privilege, agent identity, observability, break-glass controls, and specification engineering. They explore the risk of “confident misalignment”—when an AI system confidently pursues an outcome that isn't actually what its human operators intended—and why giving agents more capability doesn't mean giving them unlimited authority. The conversation also looks at AI in space, data sovereignty, model selection, token economics, and the emerging challenge of securing entire agent ecosystems rather than individual applications. The practical message for builders is clear: define what your agents are allowed to do, know who is responsible for their actions, constrain their access, observe what they're doing, document the system, and keep humans in control when the stakes are high. Because autonomous software can move fast. Your governance needs to move with it. What You’ll Learn: • Why agentic AI introduces a different class of security and governance challenges • What space systems can teach us about designing software for high-consequence environments • Why human governance becomes more important as AI systems become more autonomous • What “confident misalignment” means and why it can be dangerous • How least privilege can be applied to AI agents and the tools they use • Why every agent needs a clear identity and an accountable owner • How observability and break-glass controls can help keep autonomous workflows under control • Why the workflow—not just the individual application—can become the security problem • How specification engineering can create stronger guardrails around AI behavior • What data sovereignty means in an increasingly agent-driven ecosystem • How model selection and token economics factor into AI architecture • Why organizations need to decide on an agentic operating model before deploying autonomous systems • Why “fail closed” can be an important principle for high-consequence AI systems About Justin Kuiper: Justin Kuiper is a Lead Architect at Future Tech with a background in Air Force space operations and cybersecurity. His experience working with complex, mission-critical systems gives him a unique perspective on the challenges of securing increasingly autonomous technology. In this episode, Justin connects lessons from space systems and cybersecurity with the emerging world of agentic AI, exploring how engineers can build systems that are not only capable, but also constrained, observable, and accountable.

    Not rated yet
  • When will we have AI in outer space? #ai #docker #aiinspace

    · 1 min

    As AI systems become more capable of reasoning, using tools, accessing data, and taking action on their own, a new question is becoming impossible to ignore: how much autonomy should we actually give them? In this episode of Ship Happens, host Per Krogslund sits down with Justin Kuiper, Lead Architect at Future Tech, to explore the security and governance challenges of agentic AI—and what engineers can do to keep increasingly autonomous systems within safe and understandable boundaries. With a background in Air Force space operations and cybersecurity, Justin brings lessons from mission-critical systems to the rapidly evolving world of AI. He explains how different environments prioritize availability, confidentiality, and mission assurance, and why those tradeoffs become even more important when software can make decisions and take actions with real-world consequences. Per and Justin dig into the importance of human governance, least privilege, agent identity, observability, break-glass controls, and specification engineering. They explore the risk of “confident misalignment”—when an AI system confidently pursues an outcome that isn't actually what its human operators intended—and why giving agents more capability doesn't mean giving them unlimited authority. The conversation also looks at AI in space, data sovereignty, model selection, token economics, and the emerging challenge of securing entire agent ecosystems rather than individual applications. The practical message for builders is clear: define what your agents are allowed to do, know who is responsible for their actions, constrain their access, observe what they're doing, document the system, and keep humans in control when the stakes are high. Because autonomous software can move fast. Your governance needs to move with it. What You’ll Learn: • Why agentic AI introduces a different class of security and governance challenges • What space systems can teach us about designing software for high-consequence environments • Why human governance becomes more important as AI systems become more autonomous • What “confident misalignment” means and why it can be dangerous • How least privilege can be applied to AI agents and the tools they use • Why every agent needs a clear identity and an accountable owner • How observability and break-glass controls can help keep autonomous workflows under control • Why the workflow—not just the individual application—can become the security problem • How specification engineering can create stronger guardrails around AI behavior • What data sovereignty means in an increasingly agent-driven ecosystem • How model selection and token economics factor into AI architecture • Why organizations need to decide on an agentic operating model before deploying autonomous systems • Why “fail closed” can be an important principle for high-consequence AI systems About Justin Kuiper: Justin Kuiper is a Lead Architect at Future Tech with a background in Air Force space operations and cybersecurity. His experience working with complex, mission-critical systems gives him a unique perspective on the challenges of securing increasingly autonomous technology. In this episode, Justin connects lessons from space systems and cybersecurity with the emerging world of agentic AI, exploring how engineers can build systems that are not only capable, but also constrained, observable, and accountable.

    Not rated yet
  • Let AI Agents Run Free MCP Docker CISO Panel

    · 1 min

    🔥 Want More Docker Content? If you found this demo exciting, hit that like button and subscribe for more! We’ve got even more Docker demos coming your way in this ongoing series showcasing new tools, integrations, and powerful workflows to level up your projects. Stay tuned! Where to find Docker: Docker: https://www.docker.com/ LinkedIn: https://www.linkedin.com/company/docker Bluesky: https://bsky.app/profile/docker.com X: @docker Instagram: @dockerinc

    Not rated yet
  • Why Modern Software Needs a Blast Radius Strategy #mcp #ai #docker

    · 13 sec

    🔥 Want More Docker Content? If you found this demo exciting, hit that like button and subscribe for more! We’ve got even more Docker demos coming your way in this ongoing series showcasing new tools, integrations, and powerful workflows to level up your projects. Stay tuned! Where to find Docker: Docker: https://www.docker.com/ LinkedIn: https://www.linkedin.com/company/docker Bluesky: https://bsky.app/profile/docker.com X: @docker Instagram: @dockerinc

    Not rated yet
  • Customizing and Using a Sandbox Kit #docker #sandboxes #dockertutorial

    · 56 sec

    Customize Docker Sandboxes to match your workflow! In this video, I show you how to personalize your development environment using Docker Sandbox Kits—from installing tools and dependencies to configuring environment variables, startup commands, and project-specific settings. You’ll also see how to open your customized sandbox in VS Code and learn why you’re not limited to a single editor. Because Docker Sandboxes connect over SSH, you can use the same environment with VS Code, Cursor, and other supported development tools. Whether you’re creating a setup for yourself or standardizing development across your team, Docker Sandbox Kits make it fast, consistent, and easy to reuse your ideal environment. 🔥 Want More Docker Content? If you found this demo exciting, hit that like button and subscribe for more! We’ve got even more Docker demos coming your way in this ongoing series showcasing new tools, integrations, and powerful workflows to level up your projects. Stay tuned! Where to find Docker: Docker: https://www.docker.com/ LinkedIn: https://www.linkedin.com/company/docker Bluesky: https://bsky.app/profile/docker.com X: @docker Instagram: @dockerinc

    Not rated yet
  • How to Customize Docker Sandboxes for Your Workflow

    · 8 min

    Customize Docker Sandboxes to match your workflow! In this video, I show you how to personalize your development environment using Docker Sandbox Kits—from installing tools and dependencies to configuring environment variables, startup commands, and project-specific settings. You’ll also see how to open your customized sandbox in VS Code and learn why you’re not limited to a single editor. Because Docker Sandboxes connect over SSH, you can use the same environment with VS Code, Cursor, and other supported development tools. Whether you’re creating a setup for yourself or standardizing development across your team, Docker Sandbox Kits make it fast, consistent, and easy to reuse your ideal environment. 🔥 Want More Docker Content? If you found this demo exciting, hit that like button and subscribe for more! We’ve got even more Docker demos coming your way in this ongoing series showcasing new tools, integrations, and powerful workflows to level up your projects. Stay tuned! Where to find Docker: Docker: https://www.docker.com/ LinkedIn: https://www.linkedin.com/company/docker Bluesky: https://bsky.app/profile/docker.com X: @docker Instagram: @dockerinc

    Not rated yet
  • Docker Sandboxes: Run AI Agents in YOLO Mode, Safely

    · 23 min

    Docker Sandboxes (sbx) let you run coding agents — and any other workload — in isolated, safe, managed environments. No more worrying about what an agent in YOLO mode could do to your machine, or what a malicious site might access. Eric Jia (Staff Product Manager) and Kevin Wittek (Staff Software Engineer), both part of the team building Docker Sandboxes, walk you through what they are, how to get started, and the tips and tricks to get the most out of them. In this video, we cover what Sandboxes are, how to get started, and the tips and tricks to get the most out of them: Chapters: 00:00 What are Docker Sandboxes 01:00 Why sandboxes, not containers 02:22 Installing SBX and network policies 04:40 Authenticating your agent (with credential caching) 05:20 Running a containerized workload inside a sandbox 07:00 Statefulness: sandboxes remember what you install 07:50 Controlling what goes in and out (filesystem, network, secrets, MCP) 10:45 Managing secrets with SBX 13:52 The --clone flag for stronger isolation 14:54 Multiplexing agent sessions with git worktrees 17:20 Pulling agent changes back to your host 17:50 Connecting a GUI (Claude Desktop, VS Code, Cursor) over SSH 20:45 Shell sandboxes for anything else you want to run 21:20 Kits and mixins: reusable, shareable sandbox configs Learn more: https://docs.docker.com/ai/sandboxes Get help: https://support.docker.com Install & releases: https://docker.com/products/docker-sandboxes Where to find Docker: Docker: https://www.docker.com/ LinkedIn: https://www.linkedin.com/company/docker Bluesky: https://bsky.app/profile/docker.com X: @docker Instagram: @dockerinc #Docker #DockerSandboxes #AIAgents #AIGovernance #Security

    Not rated yet