# Installing second node in same machine/Docker **URL:** \ **Category:** Node Operators\ **Tags:** docker, multiple-nodes\ **Created:** [January 5, 2024, 7:24am UTC](https://forum.storj.io/t/installing-second-node-in-same-machine-docker/24841 "2024-01-05T07:24:59Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![snorkel](https://storj.bcdn.literatehosting.com/letter_avatar/snorkel/32/6_449c533f586939b6e5f246632a46421f.png) [@snorkel](https://forum.storj.io/u/snorkel)\ **Post date:** [January 5, 2024, 7:24am UTC](https://forum.storj.io/t/installing-second-node-in-same-machine-docker/24841/1 "2024-01-05T07:24:59Z")
Sorry for asking noob questions after 3 years of farming storj 😇, but I want to install a second node in Docker (Synology) and should I use method 1 or 2? 1. Stop and remove node 1, stop and remove watchtower, update the images of storagenode/latest and watchtower/latest, install the second node, start node 1 and watchtower. 2. Just install second node, without stoping and removing anything, because the images are there anyways, and they probably are up-to-date, or they will be in a month or so. The watchtower run command has no image names, so it updates all the containers as I understand it, even if I add nodes afterwords? Or I have to restart it to make it see the new nodes? ---
**Author:** ![Roberto](https://storj.bcdn.literatehosting.com/letter_avatar/roberto/32/6_449c533f586939b6e5f246632a46421f.png) [@Roberto](https://forum.storj.io/u/Roberto)\ **Post date:** [January 5, 2024, 8:10am UTC](https://forum.storj.io/t/installing-second-node-in-same-machine-docker/24841/2 "2024-01-05T08:10:09Z")
On qnap when I installed the second node I didn’t have to stop it. Only the image is common ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [January 5, 2024, 8:26am UTC](https://forum.storj.io/t/installing-second-node-in-same-machine-docker/24841/3 "2024-01-05T08:26:36Z")
Perhaps you would need to update the watchtower `docker run` command to include name of the second node. The first node doesn’t prevent you from running the second one… However, I would consider to use `docker-compose.yaml`, since you would have at least three containers now. ---
**Author:** ![snorkel](https://storj.bcdn.literatehosting.com/letter_avatar/snorkel/32/6_449c533f586939b6e5f246632a46421f.png) [@snorkel](https://forum.storj.io/u/snorkel)\ **Post date:** [January 5, 2024, 8:29am UTC](https://forum.storj.io/t/installing-second-node-in-same-machine-docker/24841/4 "2024-01-05T08:29:11Z")
How would that benefit me? I don’t know what is composer, I only saw some posts about it. The watchtower command dosen’t have containers names in it. The NASes only run Storj and it can update all containers that it finds. ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [January 5, 2024, 8:32am UTC](https://forum.storj.io/t/installing-second-node-in-same-machine-docker/24841/5 "2024-01-05T08:32:27Z")
Just simpler in my opinion. To update all images: ```auto docker compose pull ``` To run all containers: ```auto docker compose up -d ``` If you changed something, you would again execute only ```auto docker compose up -d ``` it will automatically detect, which container should be stopped, removed and started again. And you would have all configuration options in the one file. However, I’m not sure that Synology has a `compose` plugin. ---
**Author:** ![Aitor](https://storj.bcdn.literatehosting.com/letter_avatar/aitor/32/6_449c533f586939b6e5f246632a46421f.png) [@Aitor](https://forum.storj.io/u/Aitor)\ **Post date:** [January 5, 2024, 10:49am UTC](https://forum.storj.io/t/installing-second-node-in-same-machine-docker/24841/6 "2024-01-05T10:49:18Z")
You don’t need to stop storagenode1 to install a new one, at less on Linux with docker.