<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>#Containerization on Home</title>
    <link>https://yakinin.com/en/tags/%23containerization/</link>
    <description>Recent content in #Containerization on Home</description>
    <generator>Hugo -- 0.148.2</generator>
    <language>en</language>
    <lastBuildDate>Wed, 06 Aug 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://yakinin.com/en/tags/%23containerization/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why Docker Calls MCP a &#39;Security Nightmare&#39;—And How to Fix It</title>
      <link>https://yakinin.com/en/posts/20250806-docker-warns-mcp-security-risks/</link>
      <pubDate>Wed, 06 Aug 2025 00:00:00 +0000</pubDate>
      <guid>https://yakinin.com/en/posts/20250806-docker-warns-mcp-security-risks/</guid>
      <description>&lt;h1 id=&#34;why-docker-calls-mcp-a-security-nightmareand-how-to-fix-it&#34;&gt;Why Docker Calls MCP a &amp;lsquo;Security Nightmare&amp;rsquo;—And How to Fix It&lt;/h1&gt;
&lt;p&gt;The Model Context Protocol (MCP) was introduced as a universal standard—the &amp;ldquo;USB-C for AI applications&amp;rdquo;—to allow AI agents to seamlessly interact with external tools, APIs, and data. Major players like Microsoft, Google, and OpenAI quickly adopted it, and thousands of MCP server tools emerged. The promise was simple: write an integration once, and any AI agent can use it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Trend: &#39;Own Hardware&#39; Instead of Cloud - Is It True?</title>
      <link>https://yakinin.com/en/posts/2412-barebone-or-cloud/</link>
      <pubDate>Mon, 23 Dec 2024 14:30:00 +0000</pubDate>
      <guid>https://yakinin.com/en/posts/2412-barebone-or-cloud/</guid>
      <description>&lt;p&gt;Yes, it&amp;rsquo;s true. For more than two years, we have observed this trend while consulting companies and working on IT projects. More and more companies are choosing to host IT solutions on their own servers. And it makes sense. In practice, it becomes evident that most disruptions are not caused by the hardware itself but by human factors and the level of expertise of the specialists involved. &amp;ldquo;Own hardware&amp;rdquo; allows better control over data (especially to prevent leaks to competitors), significantly reduces costs, and adapts infrastructure to specific needs. For projects involving containerization and orchestration, the &amp;ldquo;advantage&amp;rdquo; of clouds nearly disappears.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
