<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mount on ads' corner</title><link>https://andreas.scherbaum.la/tags/mount/</link><description>Recent content in Mount on ads' corner</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 30 Jul 2025 00:00:00 +0200</lastBuildDate><atom:link href="https://andreas.scherbaum.la/tags/mount/index.xml" rel="self" type="application/rss+xml"/><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>Arch Linux: mount: unknown filesystem type 'exfat'</title><link>https://andreas.scherbaum.la/post/2024-08-12_arch-linux-mount-unknown-filesystem-type-exfat/</link><pubDate>Mon, 12 Aug 2024 00:49:15 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2024-08-12_arch-linux-mount-unknown-filesystem-type-exfat/</guid><description>&lt;p&gt;A short while ago I moved a couple of laptops from &lt;em&gt;Ubuntu&lt;/em&gt; to &lt;em&gt;Manjaro&lt;/em&gt; (that&amp;rsquo;s an &lt;em&gt;Arch Linux&lt;/em&gt; distribution). It&amp;rsquo;s all going well, except today &lt;a href="https://pascal.scherbaum.la/"&gt;the kid&lt;/a&gt; came to me and told me: &amp;ldquo;Can&amp;rsquo;t open the SDcard from my camera. It&amp;rsquo;s not working.&amp;rdquo;&lt;/p&gt;</description></item><item><title>How to determine the mount point for a device on Linux</title><link>https://andreas.scherbaum.la/post/2024-07-26_how-to-identify-the-mount-point-for-a-device-on-linux/</link><pubDate>Fri, 26 Jul 2024 10:16:48 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2024-07-26_how-to-identify-the-mount-point-for-a-device-on-linux/</guid><description>&lt;p&gt;While &lt;a href="https://andreas.scherbaum.la/post/2024-07-22_install-debian-bookworm-on-a-software-raid-and-efi/"&gt;reinstalling a server&lt;/a&gt; and moving it to &lt;em&gt;Debian&lt;/em&gt;, I ran into the problem that I need to sync the &lt;em&gt;EFI&lt;/em&gt; partitions. The system is using a &lt;em&gt;RAID&lt;/em&gt; on two disks (&lt;em&gt;RAID 1&lt;/em&gt;), but the &lt;em&gt;EFI&lt;/em&gt; partitions can&amp;rsquo;t be a &lt;em&gt;RAID&lt;/em&gt; and need to exist on both disks. Or rather it is useful to have the &lt;em&gt;EFI&lt;/em&gt; partition on every disk: if one disk fails, the system can boot from the other disk.&lt;/p&gt;&#10;&lt;p&gt;&lt;code&gt;grub&lt;/code&gt; only installs the necessary files on one partition. However one can use a script as &lt;code&gt;grub&lt;/code&gt; hook, and sync all partitions.&lt;/p&gt;&#10;&lt;p&gt;This script needs to determine if a device (the &lt;em&gt;EFI&lt;/em&gt; partition) is already mounted somewhere, or needs to be mounted. Turns out there is a little and not well-known tool for this.&lt;/p&gt;</description></item><item><title>Install Debian Bookworm on a Software RAID and EFI</title><link>https://andreas.scherbaum.la/post/2024-07-22_install-debian-bookworm-on-a-software-raid-and-efi/</link><pubDate>Fri, 19 Jul 2024 22:11:01 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2024-07-22_install-debian-bookworm-on-a-software-raid-and-efi/</guid><description>&lt;p&gt;Moving my systems away from &lt;em&gt;Ubuntu&lt;/em&gt;, I also have to reinstall a server at home. This system has two equal disks for a &lt;em&gt;RAID&lt;/em&gt; system, and my plan is to install &lt;em&gt;Debian&lt;/em&gt; on it. Turns out, setting up a Software &lt;em&gt;RAID&lt;/em&gt; on &lt;em&gt;Debian&lt;/em&gt; and booting from &lt;em&gt;EFI&lt;/em&gt; is not a straightforward approach. This blog posting describes the steps.&lt;/p&gt;</description></item><item><title>Ansible: Just mount an existing filesystem</title><link>https://andreas.scherbaum.la/post/2019-12-09_ansible-just-mount-an-existing-filesystem/</link><pubDate>Mon, 09 Dec 2019 01:04:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2019-12-09_ansible-just-mount-an-existing-filesystem/</guid><description>&lt;p&gt;There is no easy way to &amp;ldquo;just mount&amp;rdquo; an existing filesystem in &lt;a href="https://www.ansible.com/"&gt;Ansible&lt;/a&gt;, using the &lt;a href="https://docs.ansible.com/ansible/latest/modules/mount_module.html"&gt;mount&lt;/a&gt; module. I just want to mount an already defined mount point, and don&amp;rsquo;t really care about all the configuration here.&lt;/p&gt;</description></item></channel></rss>