# Docker image \> where is node-red's home?

**URL:** https://discourse.nodered.org/t/docker-image-where-is-node-reds-home/86105
**Category:** General
**Tags:** docker
**Created:** [3 March 2024 22:40 UTC](https://discourse.nodered.org/t/docker-image-where-is-node-reds-home/86105 "2024-03-03T22:40:32Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![FloRu](https://avatars.discourse-cdn.com/v4/letter/f/db5fbb/32.png) [@FloRu](https://discourse.nodered.org/u/FloRu)
#### Post date: [3 March 2024 23:23 UTC](https://discourse.nodered.org/t/docker-image-where-is-node-reds-home/86105/3 "2024-03-03T23:23:26Z")

</div>

Thanks Nexus for this information, I think I found what I've been looking for. Please correct me, if I'm wrong:

1. There _ **is** _ user data stored inside the container, even if I'm not able to see it in terminal (at the host).
2. This data can be accessed via "docker cp" command, ran at the host's terminal, to copy out some of the data that is stored in the container's directories.
3. node-red (the user, that Node-RED is running under) data is found in the directory /usr/src/node-red/ inside the container, so to copy out data that is stored inside a container, I can use

`docker cp Containername:/usr/src/node-red/some-data-file.txt /path-of-the-host-where-i-want-the-file-to-store`

[Edit]  
And - of course - I could use the Volume mapping you described above, to also have direct access to the information that I want to store.

---

_[View the full topic](https://discourse.nodered.org/t/docker-image-where-is-node-reds-home/86105)._