# Does docker automatically restarts the Node?

**URL:** <https://forum.storj.io/t/does-docker-automatically-restarts-the-node/7816>\
**Category:** FAQ\
**Tags:** docker, downtime, web-dashboard\
**Created:** [June 26, 2020, 7:18am UTC](https://forum.storj.io/t/does-docker-automatically-restarts-the-node/7816 "2020-06-26T07:18:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dominik](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/dominik/32/1133_2.png) [@dominik](https://forum.storj.io/u/dominik)\
**Post date:** [June 26, 2020, 7:18am UTC](https://forum.storj.io/t/does-docker-automatically-restarts-the-node/7816/1 "2020-06-26T07:18:24Z")

</div>

Hello guys,

I have a Question about the usage of docker with a rpi 3.

Yesterday morning my rpi wasn’t reachable via SSH I thought again a problem with my ISP. But also Uptime Robot told that it isn’t available. This morning still no connection possible.

I made a hard reboot at my rpi and tried to start docker. But it tells that the container is already in use.

```
docker: Error response from daemon: Conflict. The container name "/storagenode" is already in use by container "9f305db4c51cbaa5999a46bf710478e66c96e46fc392ff2455466dccdbeaa613". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.

```

I was wondering why it’s running after a hard reboot. Then I looked at the Node Dashboard and it also say’s that the node is running.  
Is Docker automatically restarting the container after a hard reboot?

Since my node was probably down for round about 35h is there any possibility to check the status of dq? Is it the vatting report?

Thanks guys!

Update:  
I have checked the nodedashboard, all satellites except asia-east have 100% uptime and 100% audit checks. The asia-east one have 99.9% uptime.  
How does it work, when I even from my home network hadn’t the possibility to connect to the node?

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [June 26, 2020, 7:54am UTC](https://forum.storj.io/t/does-docker-automatically-restarts-the-node/7816/2 "2020-06-26T07:54:17Z")

</div>

Because you specified `--restart unless-stopped` in the `docker run` command:

> **[Start containers automatically](https://docs.docker.com/config/containers/start-containers-automatically/#use-a-restart-policy)**
>
> How to start containers automatically

> [@](#):
>
> | Flag | Description |
> | --- | --- |
> | `unless-stopped` | Similar to `always` , except that when the container is stopped (manually or otherwise), it is not restarted even after Docker daemon restarts. |

> [@dominik](#):
>
> Since my node was probably down for round about 35h is there any possibility to check the status of dq? Is it the vatting report?

You can see your status on the web dashboard.  
The disqualification for downtime is currently disabled, it’s re-designed:

> [@Blueprint: tracking downtime with audits](https://forum.storj.io/t/blueprint-tracking-downtime-with-audits/6745):
>
> Hey everyone, we have a new design here for tracking downtime with audits We had a previous discussion on a related document here [Blueprint: Downtime Disqualification](https://forum.storj.io/t/blueprint-downtime-disqualification/5502) , but we decided to reconsider using audits to measure storage node downtime. Let us know what you think