# Exec node under docker

**URL:** <https://discourse.nodered.org/t/exec-node-under-docker/84748>\
**Category:** General\
**Tags:** docker\
**Created:** [20 January 2024 05:45 UTC](https://discourse.nodered.org/t/exec-node-under-docker/84748 "2024-01-20T05:45:58Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![jodelkoenig](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jodelkoenig/32/44645_2.png) [@jodelkoenig](https://discourse.nodered.org/u/jodelkoenig)\
**Post date:** [20 January 2024 09:42 UTC](https://discourse.nodered.org/t/exec-node-under-docker/84748/7 "2024-01-20T09:42:12Z")

</div>

You can still "escape" your docker container with the exec node by ssh'ing onto the host system and attach your command at the end.

I do so with a certificate and a special user with non-root rights in order to do some backup jobs on host level.

I decribed in more details how I am doing it [here](https://discourse.nodered.org/t/node-red-in-a-docker-container-doesnt-seem-to-be-able-to-execute-some-programs-with-the-exec-node/78826/3)

EDIT  
Aaaand 🙂 ... if you'd like to run a script which temporarily stops your docker container after you started the script with above mentioned approach, check [here](https://discourse.nodered.org/t/does-anybody-know-the-correct-command-line-for-sshpass-to-ssh-in-start-a-script-and-log-out-again/82974/7) to get everything up and running again, as you like.

---

_[View the full topic](https://discourse.nodered.org/t/exec-node-under-docker/84748)._