https://blog.margrop.net/en/tag/container/ Recent content in Container on Margrop Blog Hugo -- gohugo.io en-US Sat, 13 Jun 2026 07:30:00 +0800 https://blog.margrop.net/en/post/docker-port-bind-half-silent/ Sat, 13 Jun 2026 07:30:00 +0800 https://blog.margrop.net/en/post/docker-port-bind-half-silent/ <blockquote> <p><strong>TL;DR:</strong></p> <p><code>docker ps</code> says everything is fine. <code>docker inspect</code>&rsquo;s <code>HostConfig.PortBindings</code> clearly says <code>203.0.113.14:3001:3000</code>. But on the host, <strong>no <code>docker-proxy</code> is listening</strong>, the iptables <code>nat/DOCKER</code> chain has <strong>no DNAT rule</strong>, and <code>NetworkSettings.Networks</code> and <code>Ports</code> are both <strong>empty <code>{}</code></strong>. This &ldquo;container alive, port dead&rdquo; state is what happens when libnetwork silently rolls back the endpoint creation because the target interface wasn&rsquo;t up at attach time — and Docker doesn&rsquo;t bother to tell you that the port publish never actually happened. <strong>The fix is a single 30-second command</strong>: <code>docker network connect &lt;net&gt; &lt;ctr&gt;</code>.</p> </blockquote> https://blog.margrop.net/en/post/reboot-docker-server-auto-start/ Tue, 06 Apr 2021 14:39:32 +0800 https://blog.margrop.net/en/post/reboot-docker-server-auto-start/ <p>After rebooting the operating system, I found that the Docker service did not start and the containers did not start either. How do you make them start automatically after reboot?</p> <h1 id="solve-two-problems">Solve Two Problems</h1> <ol> <li>Enable automatic restart for the Docker service</li> </ol> <div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>systemctl enable docker.service </span></span></code></pre></div><p><img src="https://blog.margrop.net/post-images/external/cd1b1425e8c3d0f4.png"></p>