<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Devops on Kaisekukun</title><link>https://netguide.jp/zh/tags/devops/</link><description>Recent content in Devops on Kaisekukun</description><generator>Hugo -- gohugo.io</generator><language>zh</language><copyright>Kaisekukun</copyright><atom:link href="https://netguide.jp/zh/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting Up a Local Dev Environment with Docker</title><link>https://netguide.jp/zh/software/docker-local-development/</link><pubDate>Sun, 21 Jun 2026 11:00:00 +0900</pubDate><guid>https://netguide.jp/zh/software/docker-local-development/</guid><description>&lt;img src="https://netguide.jp/img/thumbnail/docker-local-development-zh.png" alt="Featured image of post Setting Up a Local Dev Environment with Docker" /&gt;&lt;p&gt;&amp;ldquo;It works on my machine&amp;rdquo; is a phrase every developer knows all too well. Docker solves this by packaging your application and its dependencies into portable containers. This article walks through setting up a local development environment with Docker.&lt;/p&gt;
&lt;h2 id="the-three-core-concepts"&gt;The Three Core Concepts
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Dockerfile&lt;/strong&gt;: A blueprint for your container — which base image to use and what to install.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;docker-compose.yml&lt;/strong&gt;: A configuration file for managing multiple containers (web server, database, cache, etc.) together.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Volume mount&lt;/strong&gt;: Lets the container reference files on your host machine. Essential for hot reload.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="multi-service-设置-with-docker-compose"&gt;Multi-Service 设置 with docker-compose
&lt;/h2&gt;&lt;p&gt;A typical frontend + backend + database setup can be defined in a single &lt;code&gt;docker-compose.yml&lt;/code&gt;:&lt;/p&gt;</description></item><item><title>Accelerating GitHub Actions CI/CD workflows using Caching</title><link>https://netguide.jp/zh/software/github-actions-cicd-caching/</link><pubDate>Wed, 15 Apr 2026 12:00:00 +0900</pubDate><guid>https://netguide.jp/zh/software/github-actions-cicd-caching/</guid><description>&lt;img src="https://netguide.jp/img/thumbnail/github-actions-cicd-caching-zh.png" alt="Featured image of post Accelerating GitHub Actions CI/CD workflows using Caching" /&gt;&lt;p&gt;Optimizing CI/CD workflow times directly impacts developer productivity and reduces computing expenses. This article shows you how to integrate dependency caching in GitHub Actions, helping you slash compilation and package setup times.&lt;/p&gt;
&lt;p&gt;We provide YAML workflow templates for Node.js, Python, and Rust, alongside best practices to ensure optimal cache hits.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="1-why-cache-dependencies-in-cicd"&gt;1. Why Cache Dependencies in CI/CD?
&lt;/h2&gt;&lt;p&gt;When a CI agent starts without caching, it spins up a clean container and fetches every dependency from package registries. This introduces several drawbacks:&lt;/p&gt;</description></item><item><title>Docker Container Image 安全 最佳 Practices</title><link>https://netguide.jp/zh/software/docker-container-security/</link><pubDate>Tue, 10 Mar 2026 12:00:00 +0900</pubDate><guid>https://netguide.jp/zh/software/docker-container-security/</guid><description>&lt;img src="https://netguide.jp/img/thumbnail/docker-container-security-zh.png" alt="Featured image of post Docker Container Image 安全 最佳 Practices" /&gt;&lt;p&gt;In modern cloud-native development, &lt;strong&gt;Docker containers&lt;/strong&gt; are the default standard for deploying web applications.&lt;/p&gt;
&lt;p&gt;然而, generic Dockerfiles often yield images containing OS vulnerabilities, unnecessary tooling, or root process privileges. 在本指南中, we cover the essential best practices to harden your Docker container images for production.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id="1-enforce-multi-stage-builds"&gt;1. Enforce Multi-stage Builds
&lt;/h3&gt;&lt;p&gt;Leaving build tools, compiler caches, or developer dependencies (like npm or git) inside your final runtime image increases the container size and broadens the attack surface.&lt;/p&gt;</description></item></channel></rss>