# Docker problems

**URL:** https://meta.discourse.org/t/docker-problems/359438
**Category:** Self-hosting
**Created:** [March 29, 2025, 2:08pm UTC](https://meta.discourse.org/t/docker-problems/359438 "2025-03-29T14:08:01Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 1, 2025, 3:31pm UTC](https://meta.discourse.org/t/docker-problems/359438/13 "2025-04-01T15:31:32Z")

</div>

Just saw this again on a server I upgraded. . .

> [@geoff777](#):
>
> Was showing as FATAL. Otherwise I’d have been unaware as in all previous installs.

The error you’re talking about is this one:

```plaintext

I, [2025-04-01T15:14:58.799796 #1] INFO -- : > awk -F\# '{print $1;}' ~/.ssh/authorized_keys | awk 'BEGIN { print "Authorized SSH keys for this container:"; } NF>=2 {print $NF
;}'
awk: fatal: cannot open file `/root/.ssh/authorized_keys' for reading: No such file or directory
I, [2025-04-01T15:14:58.810714 #1] INFO -- : Authorized SSH keys for this container:

```

And though `awk` thinks it’s fatal. I promise, it’s not actually a problem. You’ve been ignoring t for years. 🙂

> [@geoff777](#):
>
> Perhaps this Docker Hub login requirement needs to go in the [official install](https://meta.discourse.org/t/142537?silent=true). It seems necessary. .. as root!

I’ve been wondering when that was going to be true, but it seems not to be for many folks so far. I think I’ve seen one other example.

> [@geoff777](#):
>
> So I run into LetsEncrypt limits and … when I get out of SSL jail

You can get out of jail free by adding another hostname (like just add `www.` as another name) as described at [Setup Multisite Configuration with Let's Encrypt and no Reverse Proxy](https://meta.discourse.org/t/setup-multisite-configuration-with-lets-encrypt-and-no-reverse-proxy/175285) and include just the `after_ssl` stanza.

---

_[View the full topic](https://meta.discourse.org/t/docker-problems/359438)._
