<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Go on nobe4</title><link>https://nobe4.fr/tags/go/</link><description>Recent content in Go on nobe4</description><generator>Hugo</generator><language>en-us</language><copyright>&lt;a href="https://creativecommons.org/licenses/by-sa/4.0/"&gt;CC BY-SA&lt;/a&gt;</copyright><lastBuildDate>Sat, 27 Jun 2026 12:13:35 +0200</lastBuildDate><atom:link href="https://nobe4.fr/tags/go/index.xml" rel="self" type="application/rss+xml"/><item><title>When Go user.Lookup fails</title><link>https://nobe4.fr/posts/when-go-user.lookup-fails/</link><pubDate>Thu, 11 Jun 2026 00:00:00 +0000</pubDate><guid>https://nobe4.fr/posts/when-go-user.lookup-fails/</guid><description>&lt;p&gt;A Docker base image bump turned into a multi-day debug of Go&amp;rsquo;s &lt;code&gt;os/user&lt;/code&gt;
package, NSS, SSSD, LDAP and GLIBC ABI. Here is what happened and what I
learned.&lt;/p&gt;
&lt;p&gt;Throughout this post, &lt;code&gt;alice&lt;/code&gt; is an admin account with a hardcoded entry in
&lt;code&gt;/etc/passwd&lt;/code&gt;, and &lt;code&gt;bob&lt;/code&gt; is a regular user who only exists in the central LDAP
directory. All details of &lt;code&gt;/bin/client&lt;/code&gt; are fictitious for the purpose of this
post.&lt;/p&gt;
&lt;h2 id="how-it-started-glibc-errors"&gt;How it started: GLIBC errors&lt;/h2&gt;
&lt;p&gt;After deploying a routine docker update, users started seeing errors:&lt;/p&gt;</description></item></channel></rss>