<p dir="auto">I have just started noticing new(?) errors in the kubelet.log after a pull saturday.</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="E0810 16:21:55.554843 13225 volume.go:174] Could not read directory: /var/lib/kubelet/.bash_logout/volumes, (open /var/lib/kubelet/.bash_logout/volumes: not a directory)
E0810 16:21:55.554867 13225 volume.go:174] Could not read directory: /var/lib/kubelet/.bashrc/volumes, (open /var/lib/kubelet/.bashrc/volumes: not a directory)
E0810 16:21:55.554899 13225 volume.go:174] Could not read directory: /var/lib/kubelet/.profile/volumes, (open /var/lib/kubelet/.profile/volumes: not a directory)"><pre class="notranslate"><code class="notranslate">E0810 16:21:55.554843 13225 volume.go:174] Could not read directory: /var/lib/kubelet/.bash_logout/volumes, (open /var/lib/kubelet/.bash_logout/volumes: not a directory)
E0810 16:21:55.554867 13225 volume.go:174] Could not read directory: /var/lib/kubelet/.bashrc/volumes, (open /var/lib/kubelet/.bashrc/volumes: not a directory)
E0810 16:21:55.554899 13225 volume.go:174] Could not read directory: /var/lib/kubelet/.profile/volumes, (open /var/lib/kubelet/.profile/volumes: not a directory)
</code></pre></div>
<p dir="auto">This error appears every 10 seconds (with .bash_logout &amp; .bash_profile also), when set up with vagrant:</p>
<p dir="auto">Aug 12 23:16:58 kubernetes-minion-1 kubelet[10777]: E0812 23:16:58.200218 10777 volume.go:174] Could not read directory: /var/lib/kubelet/.bashrc/volumes, (open /var/lib/kubelet/.bashrc/volumes: not a directory)</p>
<p dir="auto">This is because the kubelet root directory defaults to /var/lib/kubelet, which is also the homedir for the kubelet user, and so the user's default files trip up kubelet.  Manually deleting the files (rm /var/lib/kubelet/.bash*) causes the errors to stop without any obvious ill-effects.</p>