# Make a documentation suggestion?

**URL:** <https://discourse.nodered.org/t/make-a-documentation-suggestion/16941>\
**Category:** General\
**Created:** [21 October 2019 00:09 UTC](https://discourse.nodered.org/t/make-a-documentation-suggestion/16941 "2019-10-21T00:09:57Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![jbob762](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jbob762/32/13434_2.png) [@jbob762](https://discourse.nodered.org/u/jbob762)\
**Post date:** [21 October 2019 00:09 UTC](https://discourse.nodered.org/t/make-a-documentation-suggestion/16941/1 "2019-10-21T00:09:57Z")

</div>

Where is the right place to suggest a documentation change? Just beginning using node-red, but really liking what I have seen so far.

I was using the node-red docs to install in docker:

[https://nodered.org/docs/getting-started/docker#running-headless](https://nodered.org/docs/getting-started/docker#running-headless)

In that documentation there is a note about using chown to change the ownership of the filesystem where the /data is mounted because errors. I was running into those errors. The proposed method works, but there is another way:

sudo docker volume create noderedvol  
sudo docker run -d -p 1880:1880 --name="mynodered" --mount src=noderedvol,dst=/data nodered/node-red

Those commands create a docker volume and use that as the mount point for the /data folder which seems to work just as well as the chown method but probably better practice.

Jon

---

<div class="post-metadata">

**Author:** ![miker256](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/miker256/32/13042_2.png) [@miker256](https://discourse.nodered.org/u/miker256)\
**Post date:** [21 October 2019 00:26 UTC](https://discourse.nodered.org/t/make-a-documentation-suggestion/16941/2 "2019-10-21T00:26:20Z")

</div>

I would start here. [https://github.com/node-red/node-red/wiki](https://github.com/node-red/node-red/wiki)

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [21 October 2019 05:43 UTC](https://discourse.nodered.org/t/make-a-documentation-suggestion/16941/3 "2019-10-21T05:43:20Z")

</div>

Once you have a volume, could you explain how you can access the files (ie. get a backup of your flows.json/settings.js) ?

Volumes are usually used to share data between containers (not applicable).

I suspect you are overcomplicating things and you will find out down the road.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [21 October 2019 07:35 UTC](https://discourse.nodered.org/t/make-a-documentation-suggestion/16941/4 "2019-10-21T07:35:20Z")

</div>

@jbob762 - I think that approach is documented here - [https://nodered.org/docs/getting-started/docker#using-named-data-volumes](https://nodered.org/docs/getting-started/docker#using-named-data-volumes)  
alongside the alternative bind-mount.  
As with all things docker there are many possible options so I hope we have covered most of the important ones, but happy to have suggestions for improvement.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [21 October 2019 07:49 UTC](https://discourse.nodered.org/t/make-a-documentation-suggestion/16941/5 "2019-10-21T07:49:21Z")

</div>

@bakman2 - if the container is running you can use `docker cp` from the host to access into the data volume - eg to read the /data dir (which is where the flows etc are mounted internally from a container named mynodered

```auto
docker cp mynodered:/data /your/host/path/of/choice

```

---

<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:** [21 October 2019 07:51 UTC](https://discourse.nodered.org/t/make-a-documentation-suggestion/16941/6 "2019-10-21T07:51:36Z")

</div>

> [@miker256](#):
>
> I would start here. ...

Do not use the wiki to make suggestions. The wiki is a working space for the project, not somewhere for discussion or proposals to be started.

Posting a thread to this forum is a great place to make a suggestion that can be discussed and then move to a Pull Request against the docs if necessary. Please just ensure the title of the thread reflects the topic you want to discuss.

---

<div class="post-metadata">

**Author:** ![jbob762](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jbob762/32/13434_2.png) [@jbob762](https://discourse.nodered.org/u/jbob762)\
**Post date:** [21 October 2019 23:17 UTC](https://discourse.nodered.org/t/make-a-documentation-suggestion/16941/7 "2019-10-21T23:17:14Z")

</div>

Well there it is! Thanks for pointing it out. Was trying to follow the instructions from top to bottom. Maybe put the volumes first? Using the bind mount, encountering errors, finding the note about chown was a little troublesome but you are welcome to consider the source. I am very new to docker (and NR) and still on the steep part of the learning curve. Actually stumbled on the volumes through the docker docs and it worked well out of the box.

Jon

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [22 October 2019 06:27 UTC](https://discourse.nodered.org/t/make-a-documentation-suggestion/16941/8 "2019-10-22T06:27:38Z")

</div>

Volumes for node-red are overkill.

Easiest is to map a local directory to the container dir

Eg: -v /localdir:/data