# Create node that runs a docker while node-red is also running in docker

**URL:** <https://discourse.nodered.org/t/create-node-that-runs-a-docker-while-node-red-is-also-running-in-docker/90659>\
**Category:** Developing Nodes\
**Tags:** docker\
**Created:** [2 September 2024 16:39 UTC](https://discourse.nodered.org/t/create-node-that-runs-a-docker-while-node-red-is-also-running-in-docker/90659 "2024-09-02T16:39:00Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [3 September 2024 14:50 UTC](https://discourse.nodered.org/t/create-node-that-runs-a-docker-while-node-red-is-also-running-in-docker/90659/4 "2024-09-03T14:50:10Z")

</div>

there is nothing stopping your node-red executing docker commands and spinning up containers.

Another way could be to have multiple node-reds running and offload work to them using simple MQTT comms as a control + command API.

keeping everything in Node-RED will give the visual benefits.

* * *

company hat on for a moment - most of what you are asking (like spinning up more nodes, docker/Kubernetes orchestration) has pretty much been solved by [FlowFuse](https://flowfuse.com/) (which is open source) - maybe worth checking it out?

---

_[View the full topic](https://discourse.nodered.org/t/create-node-that-runs-a-docker-while-node-red-is-also-running-in-docker/90659)._