<?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 The Blog of Boban Acimovic</title><link>https://acim.net/tags/docker/</link><description>Recent content in Docker on The Blog of Boban Acimovic</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>The Blog of Boban Acimovic &amp;copy; 2026</copyright><lastBuildDate>Fri, 03 Jun 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://acim.net/tags/docker/index.xml" rel="self" type="application/rss+xml"/><item><title>Build Rust container images faster using layer caching</title><link>https://acim.net/blog/rust-container-image-buildkit-buildx/</link><pubDate>Fri, 03 Jun 2022 00:00:00 +0000</pubDate><guid>https://acim.net/blog/rust-container-image-buildkit-buildx/</guid><description>&lt;p&gt;In the previous blog post I described how to define GitHub Actions pipeline to benefit from caching Rust dependencies and container images&amp;rsquo; layers. But the final result may also depend on your Dockerfile. Namely, &lt;a href="https://github.com/marketplace/actions/docker-buildx" target="_blank" rel="noopener"&gt;Docker Buildx Action&lt;/a&gt;
 supports &lt;a href="https://github.com/moby/buildkit" target="_blank" rel="noopener"&gt;BuildKit&lt;/a&gt;
 and &lt;a href="https://github.com/docker/buildx" target="_blank" rel="noopener"&gt;buildx&lt;/a&gt;
 and in order to benefit from this, your &lt;code&gt;Dockerfile&lt;/code&gt; has to explicitly cache layers. Actually, this is quite easy to achieve, let&amp;rsquo;s see the example:&lt;/p&gt;</description></item><item><title>Using kubectl patch in continuous deployment</title><link>https://acim.net/blog/using-kubectl-patch-to-deploy/</link><pubDate>Wed, 23 Oct 2019 00:00:00 +0000</pubDate><guid>https://acim.net/blog/using-kubectl-patch-to-deploy/</guid><description>&lt;p&gt;How to deploy new Docker images to your Kubernetes cluster? Of course, there are many ways and one of the most common ways is to use &lt;em&gt;kubectl set image&lt;/em&gt;, for example:&lt;/p&gt;</description></item><item><title>New kind on the Block</title><link>https://acim.net/blog/new-kind-on-the-block/</link><pubDate>Thu, 03 Oct 2019 00:00:00 +0000</pubDate><guid>https://acim.net/blog/new-kind-on-the-block/</guid><description>&lt;p&gt;Few months ago I wrote an article about &lt;a href="https://acim.net/blog/forget-about-minikube-try-microk8s/"&gt;replacing Minikube with MicroK8s&lt;/a&gt;
, but now we have even better soluion, &lt;a href="https://kind.sigs.k8s.io/" target="_blank" rel="noopener"&gt;kind&lt;/a&gt;
. Like dind allows running Docker inside Docker containers, kind allows running Kubernetes inside Docker containers. kind basically abstracts nodes as Docker containers and then runs Kubernetes inside.&lt;/p&gt;</description></item></channel></rss>