# Discourse Update Error: Your Docker installation is not working correctly

**URL:** https://meta.discourse.org/t/discourse-update-error-your-docker-installation-is-not-working-correctly/351253
**Category:** Support
**Created:** [February 8, 2025, 5:44pm UTC](https://meta.discourse.org/t/discourse-update-error-your-docker-installation-is-not-working-correctly/351253 "2025-02-08T17:44:53Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![hanisch](https://avatars.discourse-cdn.com/v4/letter/h/ecae2f/32.png) [@hanisch](https://meta.discourse.org/u/hanisch)
#### Post date: [February 8, 2025, 5:44pm UTC](https://meta.discourse.org/t/discourse-update-error-your-docker-installation-is-not-working-correctly/351253/1 "2025-02-08T17:44:54Z")

</div>

I’ve been self-hosting a Discourse installation on a DigitalOcean droplet for several years and have updated Discourse many times with no problems both via the admin page and ssh-ing in and using the CLI. This is the first time I’m having a problem. Today (February 8th, 2025) I updated the Docker container via the admin page just fine. Then I stared updating Discourse, and it failed. I ssh’d in and ran:

```plaintext
sudo ./launcher rebuild app

```

and got this error:

```plaintext
WARNING: Docker version 20.10.14 deprecated, recommend upgrade to 24.0.7 or newer.

x86_64 arch detected.

WARNING: We are about to start downloading the Discourse base image

This process may take anywhere between a few minutes to an hour, depending on your network speed

Please be patient

2.0.20250129-0720: Pulling from discourse/base

toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

Unable to find image 'discourse/base:2.0.20250129-0720' locally

docker: Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit.

See 'docker run --help'.

Your Docker installation is not working correctly

See: https://meta.discourse.org/t/docker-error-on-bootstrap/13657/18?u=sam

```

(I no longer have access to the error messages from the admin update page since the Discourse server is down.)

Does anyone know why this is happening and what I need to do?

Please help!

---

<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: [February 8, 2025, 6:24pm UTC](https://meta.discourse.org/t/discourse-update-error-your-docker-installation-is-not-working-correctly/351253/2 "2025-02-08T18:24:26Z")

</div>

> [@hanisch](#):
>
> Does anyone know why this is happening and what I need to do?

You need to upgrade docker, or will soon.

> [@hanisch](#):
>
> for several years

It’s a good bet you need to upgrade your OS too.

What does `lsb_release -a` tell you?

> [@hanisch](#):
>
> ```plaintext
> docker: Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit.
> 
> ```

But this is a bit more concerning.

> **[Docker Hub usage and limits](https://docs.docker.com/docker-hub/usage/)**
>
> Learn about usage and limits for Docker Hub.

Perhaps you can wait an hour and try again?

You should be able to restart the old container with

```
   ./launcher start app

```

---

<div class="post-metadata">

### Author: ![hanisch](https://avatars.discourse-cdn.com/v4/letter/h/ecae2f/32.png) [@hanisch](https://meta.discourse.org/u/hanisch)
#### Post date: [February 8, 2025, 6:47pm UTC](https://meta.discourse.org/t/discourse-update-error-your-docker-installation-is-not-working-correctly/351253/3 "2025-02-08T18:47:23Z")

</div>

Hi Jay,

Thank you so much for your response!

Is there a webpage you can recommend with instructions on how to upgrade Docker?

Running `lsb_release -a` yields:

```plaintext
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.4 LTS
Release:	20.04
Codename:	focal

```

(I’ve been putting off updating linux, as I’ve never done an os upgrade on a DigitalOcean droplet, but I know I’ll have to bite the bullet soon.)

I looked at the website you sent about Docker Usage and limits before I posted here, but I don’t know how to make heads or tails of it. Do I have to pay for Docker just to update Discourse?

I did try to restart by running `./launcher start app` but got an almost identical error message to that when I ran `./launcher rebuild app`.

It’s been over an hour, so I just tried to `./launcher rebuild app` again, but got the same error.

I very much appreciate any more guidance you can provide.

---

<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: [February 8, 2025, 6:53pm UTC](https://meta.discourse.org/t/discourse-update-error-your-docker-installation-is-not-working-correctly/351253/4 "2025-02-08T18:53:47Z")

</div>

EDIT: Oh, but you have the “too many requests” error. I think what I’d do is type

```
  docker login

```

and follow the instructions. It looks like a free authenticated version might solve your problem.

> [@hanisch](#):
>
> (I’ve been putting off updating linux, as I’ve never done an os upgrade on a DigitalOcean droplet, but I know I’ll have to bite the bullet soon.)

I’d recommend just getting a new one and following [Move a Discourse site to another VPS with rsync](https://meta.discourse.org/t/move-a-discourse-site-to-another-vps-with-rsync/43812). There’s little downtime and if something goes wrong, you can just delete the new droplet and try again.

But you’re fine for now, so you could just be able to

```plaintext
sudo apt update
sudo apt upgrade 
# or if you want to just upgrade docker, this will probably do it.
sudo apt install docker-ce

```

---

<div class="post-metadata">

### Author: ![hanisch](https://avatars.discourse-cdn.com/v4/letter/h/ecae2f/32.png) [@hanisch](https://meta.discourse.org/u/hanisch)
#### Post date: [February 8, 2025, 7:29pm UTC](https://meta.discourse.org/t/discourse-update-error-your-docker-installation-is-not-working-correctly/351253/5 "2025-02-08T19:29:17Z")

</div>

Hi Jay,

I ran `sudo apt update` and `sudo apt upgrade` without incident. I then tried to run `sudo ./launcher rebuild app` again and got the error:

```plaintext
WARNING: Docker version 24.0.2 deprecated, recommend upgrade to 24.0.7 or newer.
x86_64 arch detected.

WARNING: We are about to start downloading the Discourse base image
This process may take anywhere between a few minutes to an hour, depending on your network speed

Please be patient

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
Unable to find image 'discourse/base:2.0.20250129-0720' locally
docker: Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit.
See 'docker run --help'.
Your Docker installation is not working correctly

```

Note that it’s the same error as before except now the deprecated version is 24.0.2 instead of 20.10.14. I tried `sudo apt install docker-ce` but get the same error when running `sudo ./launcher rebuild app`. It doesn’t seem to want to upgrade to 24.0.7 or newer.

I just successfully created a Docker login from the Docker website. I can log into the Docker site, but when I run `docker login` from the command line and enter my username and password (which I copied and pasted from my keychain to avoid typos) I get:

```plaintext
permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/auth": dial unix /var/run/docker.sock: connect: permission denied

```

I’ve tried it several times in case I pasted the password wrong, all to no avail. Is there a different login that I have to create?

I greatly appreciate any more advice you may be able to provide!

---

<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: [February 8, 2025, 7:33pm UTC](https://meta.discourse.org/t/discourse-update-error-your-docker-installation-is-not-working-correctly/351253/6 "2025-02-08T19:33:22Z")

</div>

> [@hanisch](#):
>
> Note that it’s the same error as before except now the deprecated version is 24.0.2 instead of 20.10.14.

That’s as good as it gets with your OS. It’s probably good enough.

> [@hanisch](#):
>
> I tried `sudo apt install docker-ce` but get the same error when running `sudo ./launcher rebuild app`.

Yup. It’ll try to upgrade only docker. Docker goes by some different names in some different cases, so I thought upgrading everything was a more sure solution.

> [@hanisch](#):
>
> I run `docker login` from the command line and enter my username and password

That’s your _docker_ credentials it wants, not your OS credentials. When I do that I get something like this:

```plaintext
USING WEB-BASED LOGIN
To sign in with credentials on the command line, use 'docker login -u <username>'

Your one-time device confirmation code is: WZYX-ABCD
Press ENTER to open your browser or submit your device code here: https://login.docker.com/activate

```

Are you running this as root, or as some user that doesn’t have permission to use docker?

---

<div class="post-metadata">

### Author: ![hanisch](https://avatars.discourse-cdn.com/v4/letter/h/ecae2f/32.png) [@hanisch](https://meta.discourse.org/u/hanisch)
#### Post date: [February 8, 2025, 8:05pm UTC](https://meta.discourse.org/t/discourse-update-error-your-docker-installation-is-not-working-correctly/351253/7 "2025-02-08T20:05:25Z")

</div>

Hi Jay,

Yes, the problem was that I ran `docker login` instead of `sudo docker login` as I was not running as root. But I did enter my Docker username and password, not my os username and password. I’m not _that_ bad!

I just ran `sudo ./launcher rebuild app` again and didn’t get the errors! It asked me to run it again, so I complied. I then ran `sudo ./launcher start app` and everything is up and running!

Thank you so much! I just needed to have a docker login (and then log in, as root).

You’ve been such a tremendous help! Thanks again for your generosity and patience! Hopefully this topic will help others encountering the same issue.

---

<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: [February 8, 2025, 8:31pm UTC](https://meta.discourse.org/t/discourse-update-error-your-docker-installation-is-not-working-correctly/351253/8 "2025-02-08T20:31:20Z")

</div>

> [@hanisch](#):
>
> I’m not _that_ bad!

Well, I can’t always guess what things make sense to whom.

Glad you figured it out.

Thanks for the update! This is the first time I’ve seen this problem, and I’m glad my suggested solution worked. I’m wondering whether this is going to be a more common problem going forward.
