<p>After going crazy for half a day I found the answer to this issue and I'm sharing hoping others don't go through the same.</p>
<p>Turns out nitro still had knowledge of the previous installs (I suppose) and all I needed to do was run <code>nitro destroy</code>. I found out after almost uninstalling nitro altogether.</p>

CC BY-SA 4.0
2022-03-09T11:06:56.093Z
2022-03-09T11:06:56.093Z
cballenar
<p>I did an update of Docker and to my surprise all my containers/images/etc were gone. So I figured I simply needed to init and start nitro again.</p>
<p>When attempting to start or init it keeps resulting in errors such as:</p>
<pre><code>unable to pull from docker hub context deadline exceeded
</code></pre>
<p>I'm not sure what's keeping it stuck. I've tried updating multiple commands with no luck.</p>

<nitro><docker>
Nitro unable to init or start after Docker update
# Nitro unable to init or start after Docker update

(Asked by: username_0 on 2022-03-09)

I did an update of Docker and to my surprise all my containers/images/etc were gone. So I figured I simply needed to init and start nitro again.
When attempting to start or init it keeps resulting in errors such as:
unable to pull from docker hub context deadline exceeded

I'm not sure what's keeping it stuck. I've tried updating multiple commands with no luck.

**Tags:** nitro, docker


---

## 1 answers

### Answer by username_0 on 2022-03-09. Score: 1 | Accepted answer

After going crazy for half a day I found the answer to this issue and I'm sharing hoping others don't go through the same.

Turns out nitro still had knowledge of the previous installs (I suppose) and all I needed to do was run `nitro destroy`. I found out after almost uninstalling nitro altogether.


---

