As an assignment I have to create a bunch of Docker containers and use pssh to show inter-connectivity of the cluster. Now 10 containers I can manage juts fine, but when I start the process for 500 containers (which is the real assignment) I run into what seems like a randomly “broken” pipe. More importantly it happens during the pssh inter-connectivity block of code. For ease of use I run the script in a VirtualBox VM running an Ubuntu 22.04 (as opposed to my windows host machine due to windows’ issue of not being able to connect to docker containers through direct IP addressing). Earlier I stated the issue seems random and thats because just now it happened on the first set of connections but in an earlier attempt it happened after some 300 successful sets of connections. In my case the set of connections is one container using pssh to connect to the remaining 499 containers while running the hostname command (so altogether I run 500 * 499 connections making this a lengthy process and the issue that more annoying). Now the VM is slow yes but this takes in the ballpark of 7 hours to complete so debugging is key and I just don’t know whats causing the error.

As an assignment I have to create a bunch of Docker containers and use pssh to show inter-connectivity of the cluster. Now 10 containers I can manage juts fine, but when I start the process for 500 containers (which is the real assignment) I run into what seems like a randomly “broken” pipe. More importantly it happens during the pssh inter-connectivity block of code. For ease of use I run the script in a VirtualBox VM running an Ubuntu 22.04 (as opposed to my windows host machine due to windows’ issue of not being able to connect to docker containers through direct IP addressing). Earlier I stated the issue seems random and thats because just now it happened on the first set of connections but in an earlier attempt it happened after some 300 successful sets of connections. In my case the set of connections is one container using pssh to connect to the remaining 499 containers while running the hostname command (so altogether I run 500 * 499 connections making this a lengthy process and the issue that more annoying). Now the VM is slow yes but this takes in the ballpark of 7 hours to complete so debugging is key and I just don’t know whats causing the error.

As an assignment I have to create a bunch of Docker containers and use pssh to show inter-connectivity of the cluster. Now 10 containers I can manage juts fine, but when I start the process for 500 containers (which is the real assignment) I run into what seems like a randomly “broken” pipe. More importantly it happens during the pssh inter-connectivity block of code. For ease of use I run the script in a VirtualBox VM running an Ubuntu 22.04 (as opposed to my windows host machine due to windows’ issue of not being able to connect to docker containers through direct IP addressing). Earlier I stated the issue seems random and thats because just now it happened on the first set of connections but in an earlier attempt it happened after some 300 successful sets of connections. In my case the set of connections is one container using pssh to connect to the remaining 499 containers while running the hostname command (so altogether I run 500 * 499 connections making this a lengthy process and the issue that more annoying). Now the VM is slow yes but this takes in the ballpark of 7 hours to complete so debugging is key and I just don’t know whats causing the error.

As an assignment I have to create a bunch of Docker containers and use pssh to show inter-connectivity of the cluster. Now 10 containers I can manage juts fine, but when I start the process for 500 containers (which is the real assignment) I run into what seems like a randomly “broken” pipe. More importantly it happens during the pssh inter-connectivity block of code. For ease of use I run the script in a VirtualBox VM running an Ubuntu 22.04 (as opposed to my windows host machine due to windows’ issue of not being able to connect to docker containers through direct IP addressing). Earlier I stated the issue seems random and thats because just now it happened on the first set of connections but in an earlier attempt it happened after some 300 successful sets of connections. In my case the set of connections is one container using pssh to connect to the remaining 499 containers while running the hostname command (so altogether I run 500 * 499 connections making this a lengthy process and the issue that more annoying). Now the VM is slow yes but this takes in the ballpark of 7 hours to complete so debugging is key and I just don’t know whats causing the error.

As an assignment I have to create a bunch of Docker containers and use pssh to show inter-connectivity of the cluster. Now 10 containers I can manage juts fine, but when I start the process for 500 containers (which is the real assignment) I run into what seems like a randomly “broken” pipe. More importantly it happens during the pssh inter-connectivity block of code. For ease of use I run the script in a VirtualBox VM running an Ubuntu 22.04 (as opposed to my windows host machine due to windows’ issue of not being able to connect to docker containers through direct IP addressing). Earlier I stated the issue seems random and thats because just now it happened on the first set of connections but in an earlier attempt it happened after some 300 successful sets of connections. In my case the set of connections is one container using pssh to connect to the remaining 499 containers while running the hostname command (so altogether I run 500 * 499 connections making this a lengthy process and the issue that more annoying). Now the VM is slow yes but this takes in the ballpark of 7 hours to complete so debugging is key and I just don’t know whats causing the error.

As an assignment I have to create a bunch of Docker containers and use pssh to show inter-connectivity of the cluster. Now 10 containers I can manage juts fine, but when I start the process for 500 containers (which is the real assignment) I run into what seems like a randomly “broken” pipe. More importantly it happens during the pssh inter-connectivity block of code. For ease of use I run the script in a VirtualBox VM running an Ubuntu 22.04 (as opposed to my windows host machine due to windows’ issue of not being able to connect to docker containers through direct IP addressing). Earlier I stated the issue seems random and thats because just now it happened on the first set of connections but in an earlier attempt it happened after some 300 successful sets of connections. In my case the set of connections is one container using pssh to connect to the remaining 499 containers while running the hostname command (so altogether I run 500 * 499 connections making this a lengthy process and the issue that more annoying). Now the VM is slow yes but this takes in the ballpark of 7 hours to complete so debugging is key and I just don’t know whats causing the error.