# Node-Red in Docker Backup - Flows location

**URL:** <https://discourse.nodered.org/t/node-red-in-docker-backup-flows-location/3681>\
**Category:** General\
**Created:** [4 October 2018 11:58 UTC](https://discourse.nodered.org/t/node-red-in-docker-backup-flows-location/3681 "2018-10-04T11:58:23Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gnomi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gnomi/32/67756_2.png) [@Gnomi](https://discourse.nodered.org/u/Gnomi)\
**Post date:** [4 October 2018 11:58 UTC](https://discourse.nodered.org/t/node-red-in-docker-backup-flows-location/3681/1 "2018-10-04T11:58:23Z")

</div>

Hi,  
perhaps I have overseen it. But my Docker is always restarting after my last Node-Red flow extensions. perhaps due to the node-red-contrib-ccu node. I did not store some flows with export but have a docker .tar export of the Node-Red container. Where can I find the flows to use them in a new container again? Docker is only mentioned to understand my environment. I think it is a Node-Red question in its file structure.

Thanks,  
Joerg

---

<div class="post-metadata">

**Author:** ![janvda](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/janvda/32/234_2.png) [@janvda](https://discourse.nodered.org/u/janvda)\
**Post date:** [4 October 2018 14:10 UTC](https://discourse.nodered.org/t/node-red-in-docker-backup-flows-location/3681/2 "2018-10-04T14:10:26Z")

</div>

You can normally find them under the folder `~/.node-red/`

---

<div class="post-metadata">

**Author:** ![craigcurtin](https://avatars.discourse-cdn.com/v4/letter/c/94ad74/32.png) [@craigcurtin](https://discourse.nodered.org/u/craigcurtin)\
**Post date:** [4 October 2018 22:07 UTC](https://discourse.nodered.org/t/node-red-in-docker-backup-flows-location/3681/3 "2018-10-04T22:07:31Z")

</div>

Which docker image did you build from ?

More importantly what is your docker run command ?

Craig

---

<div class="post-metadata">

**Author:** ![Gnomi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gnomi/32/67756_2.png) [@Gnomi](https://discourse.nodered.org/u/Gnomi)\
**Post date:** [5 October 2018 07:58 UTC](https://discourse.nodered.org/t/node-red-in-docker-backup-flows-location/3681/4 "2018-10-05T07:58:03Z")

</div>

I used this image: [Docker](https://hub.docker.com/r/nodered/node-red-docker/)  
and I started all on a synology with the standard parameters of the docker environment.

this is in the log: start /usr/src/node-red

> node $NODE\_OPTIONS node\_modules/node-red/red.js -v $FLOWS "--userDir" "/data"

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [5 October 2018 08:29 UTC](https://discourse.nodered.org/t/node-red-in-docker-backup-flows-location/3681/5 "2018-10-05T08:29:09Z")

</div>

so have you looked in "~/data"?

---

<div class="post-metadata">

**Author:** ![Gnomi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gnomi/32/67756_2.png) [@Gnomi](https://discourse.nodered.org/u/Gnomi)\
**Post date:** [5 October 2018 08:44 UTC](https://discourse.nodered.org/t/node-red-in-docker-backup-flows-location/3681/6 "2018-10-05T08:44:34Z")

</div>

Thank you, never looked to this start command parameters. I just found there some data but now need to ckeck, if they are really containing the lost flows I am searching for.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [5 October 2018 08:49 UTC](https://discourse.nodered.org/t/node-red-in-docker-backup-flows-location/3681/7 "2018-10-05T08:49:45Z")

</div>

The node-red-docker readme has a section on managing user data - [https://github.com/node-red/node-red-docker#managing-user-data](https://github.com/node-red/node-red-docker#managing-user-data)