<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Container on ads' corner</title><link>https://andreas.scherbaum.la/tags/container/</link><description>Recent content in Container on ads' corner</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 15 Jun 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://andreas.scherbaum.la/tags/container/index.xml" rel="self" type="application/rss+xml"/><item><title>How installing nftables broke ssh-copy-id</title><link>https://andreas.scherbaum.la/post/2026-06-15_how-installing-nftables-broke-ssh-copy-id/</link><pubDate>Mon, 15 Jun 2026 00:00:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2026-06-15_how-installing-nftables-broke-ssh-copy-id/</guid><description>&lt;p&gt;While testing a new feature for &lt;a href="https://warehouse-pg.io/"&gt;WarehousePG&lt;/a&gt; in our &lt;a href="https://github.com/EnterpriseDB/warehouse-pg-docker"&gt;Docker containers&lt;/a&gt;, I ran into an unexpected problem: I wanted to block certain network traffic between the &lt;em&gt;Docker&lt;/em&gt; hosts, and therefore installed &lt;code&gt;nftables&lt;/code&gt;. Suddenly very early in the startup process the &lt;code&gt;ssh-copy-id&lt;/code&gt; ssh key exchange broke.&lt;/p&gt;&#10;&lt;p&gt;The error message:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;div style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&#10;&lt;table style="border-spacing:0;padding:0;margin:0;border:0;"&gt;&lt;tr&gt;&lt;td style="vertical-align:top;padding:0;margin:0;border:0;"&gt;&#10;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt; 1&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt; 2&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt; 3&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt; 4&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt; 5&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt; 6&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt; 7&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt; 8&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt; 9&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;10&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;11&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;12&#10;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&#10;&lt;td style="vertical-align:top;padding:0;margin:0;border:0;;width:100%"&gt;&#10;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-plaintext" data-lang="plaintext"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;coordinator | Adding ssh keys for user gpadmin to host standby&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;coordinator | Attempt 1/5: Adding keys for user gpadmin to host standby ...&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;coordinator | Something went wrong adding ssh keys for user gpadmin to host standby.&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;coordinator | Here is the log output:&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;coordinator |&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;coordinator | /usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: &amp;#34;/home/gpadmin/.ssh/id_rsa.pub&amp;#34;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;coordinator | /usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;coordinator | /usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;coordinator | kex_exchange_identification: read: Connection reset by peer&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;coordinator | Connection reset by 169.254.2.66 port 22&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;coordinator |&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;coordinator | Attempt 1 failed with exit code 1.&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&#10;&lt;/div&gt;&#10;&lt;/div&gt;&lt;p&gt;The key question: why is simply installing a new package into the container breaking an unrelated tool?&lt;/p&gt;</description></item><item><title>Docker Secrets and hiding sensitive information in Docker build output</title><link>https://andreas.scherbaum.la/post/2025-07-30_docker-secrets-and-hiding-sensitive-information-in-docker-build-output/</link><pubDate>Wed, 30 Jul 2025 00:00:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2025-07-30_docker-secrets-and-hiding-sensitive-information-in-docker-build-output/</guid><description>&lt;p&gt;While building a container, I need to pass a token into the build process. The container build step needs to download a package using said secret token - and that token is part of the URL. The token will show up on the screen, and potentially in any logfile. Not good.&lt;/p&gt;&#10;&lt;p&gt;Note: This applies to &lt;code&gt;docker compose&lt;/code&gt; (and &lt;code&gt;docker buildx&lt;/code&gt;).&lt;/p&gt;&#10;&lt;p&gt;The step in the &lt;code&gt;Dockerfile&lt;/code&gt; looks like this:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;div style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&#10;&lt;table style="border-spacing:0;padding:0;margin:0;border:0;"&gt;&lt;tr&gt;&lt;td style="vertical-align:top;padding:0;margin:0;border:0;"&gt;&#10;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;1&#10;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&#10;&lt;td style="vertical-align:top;padding:0;margin:0;border:0;;width:100%"&gt;&#10;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;RUN curl -1Lfs &lt;span style="color:#0a3069"&gt;&amp;#34;https://website.example/verysecrettoken/setup.rpm&amp;#34;&lt;/span&gt; -o /root/setup.sh&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&#10;&lt;/div&gt;&#10;&lt;/div&gt;&lt;p&gt;And shows up in the build output on the screen, and in the log:&lt;/p&gt;</description></item><item><title>Show all docker build output</title><link>https://andreas.scherbaum.la/post/2025-05-07_show-all-docker-build-output/</link><pubDate>Wed, 07 May 2025 00:00:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2025-05-07_show-all-docker-build-output/</guid><description>&lt;p&gt;&lt;em&gt;Docker&lt;/em&gt; by default will hide the process output of a step once the step is completed. This makes for a nice and tidy output, not overloading the screen with too many details. Here&amp;rsquo;s such an example:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;div style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&#10;&lt;table style="border-spacing:0;padding:0;margin:0;border:0;"&gt;&lt;tr&gt;&lt;td style="vertical-align:top;padding:0;margin:0;border:0;"&gt;&#10;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;1&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;2&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;3&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;4&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;5&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;6&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;7&#10;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&#10;&lt;td style="vertical-align:top;padding:0;margin:0;border:0;;width:100%"&gt;&#10;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-docker" data-lang="docker"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#953800"&gt;DOCKER_BUILDKIT&lt;/span&gt;&lt;span style="color:#0550ae"&gt;=&lt;/span&gt;&lt;span style="color:#0550ae"&gt;1&lt;/span&gt; docker compose up --force-recreate --build&lt;span style="color:#f6f8fa;background-color:#82071e"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#f6f8fa;background-color:#82071e"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#0550ae"&gt;=&lt;/span&gt;&amp;gt; &lt;span style="color:#0550ae"&gt;[&lt;/span&gt;&lt;span style="color:#6639ba"&gt;test&lt;/span&gt; build-stage 2/20&lt;span style="color:#0550ae"&gt;]&lt;/span&gt; RUN &lt;span style="color:#6639ba"&gt;echo&lt;/span&gt; &lt;span style="color:#0a3069"&gt;&amp;#34;Checksum /etc/hosts&amp;#34;&lt;/span&gt; 0.5s&lt;span style="color:#f6f8fa;background-color:#82071e"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#0550ae"&gt;=&lt;/span&gt;&amp;gt; &lt;span style="color:#0550ae"&gt;[&lt;/span&gt;&lt;span style="color:#6639ba"&gt;test&lt;/span&gt; build-stage 3/20&lt;span style="color:#0550ae"&gt;]&lt;/span&gt; RUN sha256sum /etc/hosts 0.3s&lt;span style="color:#f6f8fa;background-color:#82071e"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#f6f8fa;background-color:#82071e"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#0550ae"&gt;=&lt;/span&gt;&amp;gt; &lt;span style="color:#0550ae"&gt;[&lt;/span&gt;&lt;span style="color:#6639ba"&gt;test&lt;/span&gt; build-stage 2/20&lt;span style="color:#0550ae"&gt;]&lt;/span&gt; RUN &lt;span style="color:#6639ba"&gt;echo&lt;/span&gt; &lt;span style="color:#0a3069"&gt;&amp;#34;Checksum /etc/hosts&amp;#34;&lt;/span&gt; 0.6s&lt;span style="color:#f6f8fa;background-color:#82071e"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#0550ae"&gt;=&lt;/span&gt;&amp;gt; &lt;span style="color:#0550ae"&gt;[&lt;/span&gt;&lt;span style="color:#6639ba"&gt;test&lt;/span&gt; build-stage 3/20&lt;span style="color:#0550ae"&gt;]&lt;/span&gt; RUN sha256sum /etc/hosts 0.3s&lt;span style="color:#f6f8fa;background-color:#82071e"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&#10;&lt;/div&gt;&#10;&lt;/div&gt;&lt;p&gt;As you can see, the actual &lt;code&gt;sha256sum&lt;/code&gt; checksum is not shown once the steps complete.&lt;/p&gt;</description></item><item><title>Clear Docker build cache</title><link>https://andreas.scherbaum.la/post/2024-08-30_clear-docker-build-cache/</link><pubDate>Fri, 30 Aug 2024 00:00:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2024-08-30_clear-docker-build-cache/</guid><description>&lt;p&gt;I have this one &lt;em&gt;Docker&lt;/em&gt; image, which I need every 2-3 months to run a task in an outdated piece of software, which is no longer supported on modern systems. That works fine, but after a while I figured that &lt;em&gt;Docker&lt;/em&gt; is keeping all the build layers, even though I remove the images and containers. Worst, sometimes I update the build for the &lt;em&gt;Docker&lt;/em&gt;file, and the entire image needs to be rebuild. Still &lt;em&gt;Docker&lt;/em&gt; caches all the previous build layers as well.&lt;/p&gt;&#10;&lt;p&gt;Removing the build layers is not obvious, there is no specific &lt;em&gt;Docker&lt;/em&gt; command.&lt;/p&gt;</description></item><item><title>How many Raspberry Pi can be operated in a Shipping Container</title><link>https://andreas.scherbaum.la/post/2024-06-28_how-many-raspberry-pi-can-be-operated-in-a-shipping-container/</link><pubDate>Fri, 28 Jun 2024 10:42:18 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2024-06-28_how-many-raspberry-pi-can-be-operated-in-a-shipping-container/</guid><description>&lt;p&gt;Back in December, during &lt;a href="https://andreas.scherbaum.la/post/2023-12-22_pgconf.eu-2023-review/"&gt;PGConf.EU 2023&lt;/a&gt; in &lt;em&gt;Prague&lt;/em&gt;, we had a discussion about datacenter hosting. Someone brought up Microsoft’s &lt;a href="https://www.theverge.com/2020/9/14/21436746/microsoft-project-natick-data-center-server-underwater-cooling-reliability"&gt;underwater datacenter&lt;/a&gt; experiment from a few years ago. And then someone else asked the obvious question: is it possible to run a datacenter in a shipping container using only &lt;em&gt;Raspberry Pi&lt;/em&gt; computers.&lt;/p&gt;&#10;&lt;p&gt;At first glance, this might seem impractical. But is it really? Let’s crunch the numbers and find out!&lt;/p&gt;</description></item><item><title>Obsidian Snap: version GLIBC_2.33 not found</title><link>https://andreas.scherbaum.la/post/2024-06-07_obsidian-snap-version-glibc_2.33-not-found/</link><pubDate>Fri, 07 Jun 2024 02:04:13 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2024-06-07_obsidian-snap-version-glibc_2.33-not-found/</guid><description>&lt;p&gt;&lt;em&gt;Obsidian&lt;/em&gt; &lt;em&gt;snap&lt;/em&gt; version was upgraded on my &lt;em&gt;Ubuntu&lt;/em&gt; system - and stopped working.&lt;/p&gt;&#10;&lt;p&gt;The whole promise of having a &lt;em&gt;snap&lt;/em&gt; or containerized version of an app is to avoid dependency problems. That&amp;rsquo;s a broken promise.&lt;/p&gt;</description></item><item><title>Firefox Multi-Account Container Extension: Separate containers and cookies for websites</title><link>https://andreas.scherbaum.la/post/2024-05-03_firefox-multi-account-container-extension-separate-containers-and-cookies-for-websites/</link><pubDate>Fri, 03 May 2024 10:50:48 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2024-05-03_firefox-multi-account-container-extension-separate-containers-and-cookies-for-websites/</guid><description>&lt;p&gt;&lt;em&gt;Firefox&lt;/em&gt; is very extensible, and the app store has a large number of extensions one can install.&lt;/p&gt;&#10;&lt;p&gt;One of these extensions is the &lt;a href="https://addons.mozilla.org/en-US/firefox/addon/multi-account-containers/"&gt;Multi-Account-Container plugin&lt;/a&gt;, which allows users to separate websites from each other. What it does is creating a separate environment for all the cookies, you get a separate instance of the browser in every container you create.&lt;/p&gt;&#10;&lt;p&gt;That is very useful to containerise websites which like to track visitors everywhere, like Facebook as example. You create one container for Facebook, where you login into your account. And outside of this container you are not logged in, as far as Facebook is concerned.&lt;/p&gt;</description></item></channel></rss>