<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Docker on Mi&amp;Bee Blog</title><link>/en/tags/docker/</link><description>Recent content in Docker on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Tue, 26 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="/en/tags/docker/rss.xml" rel="self" type="application/rss+xml"/><item><title>MiBeeHive: The "Hive" Toolbox I Built for My Studio</title><link>/en/posts/mibee-oss/mibeehive-introduction/</link><pubDate>Tue, 26 May 2026 00:00:00 +0000</pubDate><guid>/en/posts/mibee-oss/mibeehive-introduction/</guid><description>&lt;p&gt;Coming from an operations background, later transitioning to development, the number of projects I maintain keeps growing. Various middleware, databases, monitoring components… each version upgrade is a manual labor: go to the official site to find the download link, compare version numbers, manually download to the internal network, then distribute to each machine. I used to write a bunch of Shell scripts to periodically pull the latest versions to the LAN — functional but not user-friendly: scripts scattered everywhere, adding new software required writing parsing logic by hand, and there was nothing to check when things went wrong.&lt;/p&gt;</description></item><item><title>Practices and Pitfalls of Dockerizing Enterprise Applications — From Traditional Virtualization to Containerization</title><link>/en/archives/05-docker-enterprise-application/</link><pubDate>Mon, 17 Apr 2017 00:00:00 +0000</pubDate><guid>/en/archives/05-docker-enterprise-application/</guid><description>&lt;h2 id="introduction-why-containerize-enterprise-applications"&gt;Introduction (Why Containerize Enterprise Applications)&lt;/h2&gt;
&lt;p&gt;In the era of cloud computing, the way enterprise applications are deployed and managed is undergoing a profound transformation. While traditional virtualization technology solved the resource isolation problem, it still has many pain points in terms of operational efficiency, resource utilization, and deployment speed. The rise of Docker container technology has provided a brand-new solution for the modernization of enterprise applications.&lt;/p&gt;
&lt;p&gt;This article shares our practical experience in the containerization migration of an enterprise email system, including technology selection, infrastructure construction, the full process of migrating from OpenVZ virtualization to Docker, and various issues encountered in production along with their solutions. Through these practical cases, we hope to provide valuable reference for teams that are currently or planning to undertake containerization migration.&lt;/p&gt;</description></item><item><title>Raspberry Pi Docker Cluster</title><link>/en/archives/rasp_pi_docker/</link><pubDate>Wed, 08 Mar 2017 00:00:00 +0000</pubDate><guid>/en/archives/rasp_pi_docker/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;At the time, I was learning Docker cluster management and wanted a low-cost lab environment to experiment with, so I thought of using Raspberry Pis. Following the &lt;a href="http://blog.hypriot.com/"&gt;Hypriot&lt;/a&gt; blog, I bought one Raspberry Pi 2 board and two Raspberry Pi 3 boards. The reasoning was that the Pi 2 was cheaper so it would be the master, and the Pi 3s had better performance for worker nodes — together they made a small cluster.&lt;/p&gt;</description></item><item><title>Building a Cross-City LAN with Docker</title><link>/en/archives/mi-docker-net/</link><pubDate>Fri, 20 Jan 2017 00:00:00 +0000</pubDate><guid>/en/archives/mi-docker-net/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;At the time, I had servers both at home and at the office and wanted unified management, but the two internal networks were isolated. Traditional port forwarding was too cumbersome, and some services I didn&amp;rsquo;t want exposed to the public internet. After trying several approaches, I found Docker OpenVPN to be the most hassle-free solution.&lt;/p&gt;
&lt;p&gt;I chose Docker OpenVPN over traditional VPN mainly because containerized deployment is extremely convenient, and certificate management is much simpler. The end result was great — I could access various services on the remote internal network via domain names, saving a lot of configuration hassle.&lt;/p&gt;</description></item></channel></rss>