after running the docker-compose up for peerplays witnesses peerplays-base and ubuntu-for-peerplays containers status are shown as stopped

prandnum commented

2021-10-08 05:11:24 +00:00

(Migrated from gitlab.com)

after running the docker-compose up for peerplays witnesses peerplays-base and ubuntu-for-peerplays containers status are shown as stopped. see below

8f480fddfe89cd9b44daa0f6ab8ea804c19830ef6fb0bb33d7013ce211cafff2 peerplays-base "bash" 2 minutes ago Exited (0) 2 minutes ago peerplaysqaenvironment_peerplays-base_1
a5ff5feae3a34a1be448448428763213e18eb1ba16068511fb376bbf95bf393c ubuntu-for-peerplays "bash" 2 minutes ago Exited (0) 2 minutes ago peerplaysqaenvironment_ubuntu-for-peerplays_1

Earlier version of the environment allowed the containers to run, if these containers are only used temporarily for bringup and then clean them up after docker-compose to avoid end user confusion(i.e. whether the env is having issues)

With earlier env:

ubuntu@ip-172-31-35-225:~/peerplays-utils$ sudo docker ps -a --no-trunc
CONTAINER ID                                                       IMAGE                   COMMAND                                       CREATED        STATUS                      PORTS                                                                                                                                             NAMES
c6edbc57588034d9a82d65e7489fa7840ffcdd890b051e7dd04512be045aa2ce   faucet-for-peerplays    "/home/peerplays/faucet/start.sh"             23 hours ago   Up 23 hours                 22/tcp, 0.0.0.0:5000->5000/tcp, :::5000->5000/tcp                                                                                                 peerplaysqaenvironment_faucet-for-peerplays_1
4a1182d2c1b82e4da1574cfce6d099048e99a73ed1de6f126bd3a60d3db16e22   redis:latest            "docker-entrypoint.sh redis-server"           23 hours ago   Up 23 hours                 6379/tcp                                                                                                                                          peerplaysqaenvironment_redis-for-peerplays_1
8e76f01058a6c6827815c51698b7d5db12e94e6d8222e4c04d032a03dceef092   peerplays01             "./witness_node -d ./witness_node_data_dir"   23 hours ago   Up 23 hours                 0.0.0.0:8090->8090/tcp, :::8090->8090/tcp, 22/tcp, 0.0.0.0:9777->9777/tcp, :::9777->9777/tcp                                                      peerplaysqaenvironment_peerplays01_1
59c3b01451fbb54e7609798d3a63c72dde760512c29996bd93d103dc1ea858ab   peerplays12             "./witness_node -d ./witness_node_data_dir"   23 hours ago   Up 23 hours                 22/tcp, 0.0.0.0:8101->8090/tcp, :::8101->8090/tcp, 0.0.0.0:9788->9777/tcp, :::9788->9777/tcp                                                      peerplaysqaenvironment_peerplays12_1
548327945a04449f54c3c8b257abed3986fa06f3539c83c5ee2d45aaa95a1f3b   peerplays09             "./witness_node -d ./witness_node_data_dir"   23 hours ago   Exited (139) 21 hours ago                                                                                                                                                     peerplaysqaenvironment_peerplays09_1
d1a60ff963469f988ebe028f3cef838d566dbbecf0e4d9004be75e11d4a73b42   peerplays03             "./witness_node -d ./witness_node_data_dir"   23 hours ago   Exited (139) 17 hours ago                                                                                                                                                     peerplaysqaenvironment_peerplays03_1
a0aca92243aa4b13d34682d9cd162b33f93af24e20f8b8fe47df6b7ecb35e603   peerplays10             "./witness_node -d ./witness_node_data_dir"   23 hours ago   Exited (139) 16 hours ago                                                                                                                                                     peerplaysqaenvironment_peerplays10_1
df87c5231716d040f6af350fbcbfe730a29651ce665a913728a3081eee32da31   peerplays07             "./witness_node -d ./witness_node_data_dir"   23 hours ago   Exited (139) 16 hours ago                                                                                                                                                     peerplaysqaenvironment_peerplays07_1
dc411901f1e1a2a27d2f8aadced17837c09ad75f9c6c25af74f902fa16c4dfb8   peerplays15             "./witness_node -d ./witness_node_data_dir"   23 hours ago   Up 23 hours                 22/tcp, 0.0.0.0:8104->8090/tcp, :::8104->8090/tcp, 0.0.0.0:9791->9777/tcp, :::9791->9777/tcp                                                      peerplaysqaenvironment_peerplays15_1
15d2b1651e18b431af779e43a6e4f02ea339d420e57656f288ce9b95e881d39e   peerplays14             "./witness_node -d ./witness_node_data_dir"   23 hours ago   Up 23 hours                 22/tcp, 0.0.0.0:8103->8090/tcp, :::8103->8090/tcp, 0.0.0.0:9790->9777/tcp, :::9790->9777/tcp                                                      peerplaysqaenvironment_peerplays14_1
e60b5d106322bb826d80227d393cce9c8d459e48ebc944e0835c46e6bddf5022   peerplays02             "./witness_node -d ./witness_node_data_dir"   23 hours ago   Exited (139) 17 hours ago                                                                                                                                                     peerplaysqaenvironment_peerplays02_1
1a8606c25b4c75c6cc622f8f2b7f5bbc472f4f0d923e4d73f021a20860d9fa0e   peerplays13             "./witness_node -d ./witness_node_data_dir"   23 hours ago   Exited (139) 12 hours ago                                                                                                                                                     peerplaysqaenvironment_peerplays13_1
5706c8586b99e94febc6348bcff2240666bc554a3eea45230248d2bd7581d3f1   peerplays11             "./witness_node -d ./witness_node_data_dir"   23 hours ago   Exited (139) 7 hours ago                                                                                                                                                      peerplaysqaenvironment_peerplays11_1
62d4b5c75460e40ff7046c7490f926510274632a99fcdb277efa2bfcf9e08dd4   peerplays06             "./witness_node -d ./witness_node_data_dir"   23 hours ago   Up 23 hours                 22/tcp, 0.0.0.0:8095->8090/tcp, :::8095->8090/tcp, 0.0.0.0:9782->9777/tcp, :::9782->9777/tcp                                                      peerplaysqaenvironment_peerplays06_1
522ce75f33340494d97480a0d2e0cfa3c52de36ae43c560fe6831ceee2b03825   peerplays16             "./witness_node -d ./witness_node_data_dir"   23 hours ago   Up 23 hours                 22/tcp, 0.0.0.0:8105->8090/tcp, :::8105->8090/tcp, 0.0.0.0:9792->9777/tcp, :::9792->9777/tcp                                                      peerplaysqaenvironment_peerplays16_1
66d346cd1deb720e04552566fa7757fbfb0d2cd537b687e6888b4df47afaf0bb   peerplays08             "./witness_node -d ./witness_node_data_dir"   23 hours ago   Up 23 hours                 22/tcp, 0.0.0.0:8097->8090/tcp, :::8097->8090/tcp, 0.0.0.0:9784->9777/tcp, :::9784->9777/tcp                                                      peerplaysqaenvironment_peerplays08_1
8f3d6add51bf0e6307dc437fa70f28c612fa377543e0a54f8b547130c58ee8fe   peerplays05             "./witness_node -d ./witness_node_data_dir"   23 hours ago   Exited (139) 21 hours ago                                                                                                                                                     peerplaysqaenvironment_peerplays05_1
cb3d23dd97c80206c17a0cf6996e4b89b6b4542f15c0787843550e13b1f71140   peerplays04             "./witness_node -d ./witness_node_data_dir"   23 hours ago   Up 23 hours                 22/tcp, 0.0.0.0:8093->8090/tcp, :::8093->8090/tcp, 0.0.0.0:9780->9777/tcp, :::9780->9777/tcp                                                      peerplaysqaenvironment_peerplays04_1
7b7cc801beb34ba56cff4b4801d20c56aaa429e7f2dc38f92c0f6a608f2a4e40   peerplays-base          "/usr/sbin/sshd -D"                           23 hours ago   Up 23 hours                 22/tcp, 8090/tcp, 9777/tcp                                                                                                                        peerplaysqaenvironment_peerplays-base_1
8300c8e6d8ccb679a85363e52ad9a1b8237fd28ed430a9ed649d032fef817bc7   hive-for-peerplays      "./hived -d ./hived_data_dir"                 23 hours ago   Up 23 hours                 22/tcp, 0.0.0.0:28090-28091->28090-28091/tcp, :::28090-28091->28090-28091/tcp                                                                     peerplaysqaenvironment_hive-for-peerplays_1
2436d50f1a3b24b3b1ce8852a608599c6dc8cc914b5a4574e4528b6f6b0c0e49   bitcoin-for-peerplays   "./bitcoind -datadir=./network/"              23 hours ago   Up 23 hours                 0.0.0.0:8332->8332/tcp, :::8332->8332/tcp, 0.0.0.0:11111->11111/tcp, :::11111->11111/tcp, 22/tcp, 0.0.0.0:18444->18444/tcp, :::18444->18444/tcp   peerplaysqaenvironment_bitcoin-for-peerplays_1
03def757e19e952630788bc4cec8a8584ffe461e0d5a7b548650227e579c8309   ubuntu-for-peerplays    "/usr/sbin/sshd -D"                           23 hours ago   Up 23 hours                 0.0.0.0:2000->22/tcp, :::2000->22/tcp                                                                                                             peerplaysqaenvironment_ubuntu-for-peerplays_1
ubuntu@ip-172-31-35-225:~/peerplays-utils$

container logs: 08oct.tar.gz

after running the docker-compose up for peerplays witnesses peerplays-base and ubuntu-for-peerplays containers status are shown as stopped. see below 8f480fddfe89cd9b44daa0f6ab8ea804c19830ef6fb0bb33d7013ce211cafff2 peerplays-base "bash" 2 minutes ago Exited (0) 2 minutes ago peerplaysqaenvironment_peerplays-base_1 a5ff5feae3a34a1be448448428763213e18eb1ba16068511fb376bbf95bf393c ubuntu-for-peerplays "bash" 2 minutes ago Exited (0) 2 minutes ago peerplaysqaenvironment_ubuntu-for-peerplays_1 Earlier version of the environment allowed the containers to run, if these containers are only used temporarily for bringup and then clean them up after docker-compose to avoid end user confusion(i.e. whether the env is having issues) With earlier env: ``` ubuntu@ip-172-31-35-225:~/peerplays-utils$ sudo docker ps -a --no-trunc CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES c6edbc57588034d9a82d65e7489fa7840ffcdd890b051e7dd04512be045aa2ce faucet-for-peerplays "/home/peerplays/faucet/start.sh" 23 hours ago Up 23 hours 22/tcp, 0.0.0.0:5000->5000/tcp, :::5000->5000/tcp peerplaysqaenvironment_faucet-for-peerplays_1 4a1182d2c1b82e4da1574cfce6d099048e99a73ed1de6f126bd3a60d3db16e22 redis:latest "docker-entrypoint.sh redis-server" 23 hours ago Up 23 hours 6379/tcp peerplaysqaenvironment_redis-for-peerplays_1 8e76f01058a6c6827815c51698b7d5db12e94e6d8222e4c04d032a03dceef092 peerplays01 "./witness_node -d ./witness_node_data_dir" 23 hours ago Up 23 hours 0.0.0.0:8090->8090/tcp, :::8090->8090/tcp, 22/tcp, 0.0.0.0:9777->9777/tcp, :::9777->9777/tcp peerplaysqaenvironment_peerplays01_1 59c3b01451fbb54e7609798d3a63c72dde760512c29996bd93d103dc1ea858ab peerplays12 "./witness_node -d ./witness_node_data_dir" 23 hours ago Up 23 hours 22/tcp, 0.0.0.0:8101->8090/tcp, :::8101->8090/tcp, 0.0.0.0:9788->9777/tcp, :::9788->9777/tcp peerplaysqaenvironment_peerplays12_1 548327945a04449f54c3c8b257abed3986fa06f3539c83c5ee2d45aaa95a1f3b peerplays09 "./witness_node -d ./witness_node_data_dir" 23 hours ago Exited (139) 21 hours ago peerplaysqaenvironment_peerplays09_1 d1a60ff963469f988ebe028f3cef838d566dbbecf0e4d9004be75e11d4a73b42 peerplays03 "./witness_node -d ./witness_node_data_dir" 23 hours ago Exited (139) 17 hours ago peerplaysqaenvironment_peerplays03_1 a0aca92243aa4b13d34682d9cd162b33f93af24e20f8b8fe47df6b7ecb35e603 peerplays10 "./witness_node -d ./witness_node_data_dir" 23 hours ago Exited (139) 16 hours ago peerplaysqaenvironment_peerplays10_1 df87c5231716d040f6af350fbcbfe730a29651ce665a913728a3081eee32da31 peerplays07 "./witness_node -d ./witness_node_data_dir" 23 hours ago Exited (139) 16 hours ago peerplaysqaenvironment_peerplays07_1 dc411901f1e1a2a27d2f8aadced17837c09ad75f9c6c25af74f902fa16c4dfb8 peerplays15 "./witness_node -d ./witness_node_data_dir" 23 hours ago Up 23 hours 22/tcp, 0.0.0.0:8104->8090/tcp, :::8104->8090/tcp, 0.0.0.0:9791->9777/tcp, :::9791->9777/tcp peerplaysqaenvironment_peerplays15_1 15d2b1651e18b431af779e43a6e4f02ea339d420e57656f288ce9b95e881d39e peerplays14 "./witness_node -d ./witness_node_data_dir" 23 hours ago Up 23 hours 22/tcp, 0.0.0.0:8103->8090/tcp, :::8103->8090/tcp, 0.0.0.0:9790->9777/tcp, :::9790->9777/tcp peerplaysqaenvironment_peerplays14_1 e60b5d106322bb826d80227d393cce9c8d459e48ebc944e0835c46e6bddf5022 peerplays02 "./witness_node -d ./witness_node_data_dir" 23 hours ago Exited (139) 17 hours ago peerplaysqaenvironment_peerplays02_1 1a8606c25b4c75c6cc622f8f2b7f5bbc472f4f0d923e4d73f021a20860d9fa0e peerplays13 "./witness_node -d ./witness_node_data_dir" 23 hours ago Exited (139) 12 hours ago peerplaysqaenvironment_peerplays13_1 5706c8586b99e94febc6348bcff2240666bc554a3eea45230248d2bd7581d3f1 peerplays11 "./witness_node -d ./witness_node_data_dir" 23 hours ago Exited (139) 7 hours ago peerplaysqaenvironment_peerplays11_1 62d4b5c75460e40ff7046c7490f926510274632a99fcdb277efa2bfcf9e08dd4 peerplays06 "./witness_node -d ./witness_node_data_dir" 23 hours ago Up 23 hours 22/tcp, 0.0.0.0:8095->8090/tcp, :::8095->8090/tcp, 0.0.0.0:9782->9777/tcp, :::9782->9777/tcp peerplaysqaenvironment_peerplays06_1 522ce75f33340494d97480a0d2e0cfa3c52de36ae43c560fe6831ceee2b03825 peerplays16 "./witness_node -d ./witness_node_data_dir" 23 hours ago Up 23 hours 22/tcp, 0.0.0.0:8105->8090/tcp, :::8105->8090/tcp, 0.0.0.0:9792->9777/tcp, :::9792->9777/tcp peerplaysqaenvironment_peerplays16_1 66d346cd1deb720e04552566fa7757fbfb0d2cd537b687e6888b4df47afaf0bb peerplays08 "./witness_node -d ./witness_node_data_dir" 23 hours ago Up 23 hours 22/tcp, 0.0.0.0:8097->8090/tcp, :::8097->8090/tcp, 0.0.0.0:9784->9777/tcp, :::9784->9777/tcp peerplaysqaenvironment_peerplays08_1 8f3d6add51bf0e6307dc437fa70f28c612fa377543e0a54f8b547130c58ee8fe peerplays05 "./witness_node -d ./witness_node_data_dir" 23 hours ago Exited (139) 21 hours ago peerplaysqaenvironment_peerplays05_1 cb3d23dd97c80206c17a0cf6996e4b89b6b4542f15c0787843550e13b1f71140 peerplays04 "./witness_node -d ./witness_node_data_dir" 23 hours ago Up 23 hours 22/tcp, 0.0.0.0:8093->8090/tcp, :::8093->8090/tcp, 0.0.0.0:9780->9777/tcp, :::9780->9777/tcp peerplaysqaenvironment_peerplays04_1 7b7cc801beb34ba56cff4b4801d20c56aaa429e7f2dc38f92c0f6a608f2a4e40 peerplays-base "/usr/sbin/sshd -D" 23 hours ago Up 23 hours 22/tcp, 8090/tcp, 9777/tcp peerplaysqaenvironment_peerplays-base_1 8300c8e6d8ccb679a85363e52ad9a1b8237fd28ed430a9ed649d032fef817bc7 hive-for-peerplays "./hived -d ./hived_data_dir" 23 hours ago Up 23 hours 22/tcp, 0.0.0.0:28090-28091->28090-28091/tcp, :::28090-28091->28090-28091/tcp peerplaysqaenvironment_hive-for-peerplays_1 2436d50f1a3b24b3b1ce8852a608599c6dc8cc914b5a4574e4528b6f6b0c0e49 bitcoin-for-peerplays "./bitcoind -datadir=./network/" 23 hours ago Up 23 hours 0.0.0.0:8332->8332/tcp, :::8332->8332/tcp, 0.0.0.0:11111->11111/tcp, :::11111->11111/tcp, 22/tcp, 0.0.0.0:18444->18444/tcp, :::18444->18444/tcp peerplaysqaenvironment_bitcoin-for-peerplays_1 03def757e19e952630788bc4cec8a8584ffe461e0d5a7b548650227e579c8309 ubuntu-for-peerplays "/usr/sbin/sshd -D" 23 hours ago Up 23 hours 0.0.0.0:2000->22/tcp, :::2000->22/tcp peerplaysqaenvironment_ubuntu-for-peerplays_1 ubuntu@ip-172-31-35-225:~/peerplays-utils$ ``` container logs: [08oct.tar.gz](/uploads/033e7d7f2acebfc3f1929fb255fb5f86/08oct.tar.gz)

prandnum commented

2021-10-08 05:11:24 +00:00

(Migrated from gitlab.com)

assigned to @serkixenos

prandnum commented

2021-10-08 05:27:00 +00:00

(Migrated from gitlab.com)

changed the description

serkixenos commented

2021-10-08 06:54:26 +00:00

(Migrated from gitlab.com)

https://gitlab.com/PBSA/tools-libs/peerplays-utils/-/tree/master/peerplays-qa-environment#starting-containers

README.md file, section Starting containers explicitly states:

Do not use this!!! Some components are mutually exclusive, and can not run side by side.

docker-compose up

Instead, start containers one by one or in groups

https://gitlab.com/PBSA/tools-libs/peerplays-utils/-/tree/master/peerplays-qa-environment#starting-containers README.md file, section Starting containers explicitly states: Do not use this!!! Some components are mutually exclusive, and can not run side by side. ``` docker-compose up ``` Instead, start containers one by one or in groups

serkixenos commented

2021-10-08 06:58:40 +00:00

(Migrated from gitlab.com)

Also, README.md does not state anywhere that these two containers should be started. Their entry points are disabled.

These two images are helper images, used as a building ground for all other images. There is no such thing as "clean them up after docker-compose".

Follow the instructions from README file at all times!

Also, README.md does not state anywhere that these two containers should be started. Their entry points are disabled. These two images are helper images, used as a building ground for all other images. There is no such thing as "clean them up after docker-compose". Follow the instructions from README file at all times!

serkixenos (Migrated from gitlab.com) closed this issue

2021-10-08 06:59:15 +00:00

prandnum (Migrated from gitlab.com) reopened this issue

2021-10-08 10:07:33 +00:00

prandnum commented

2021-10-08 10:07:43 +00:00

(Migrated from gitlab.com)

I had always run the following commands to bring up the containers(run from /home/ubuntu/peerplays-utils/peerplays-qa-environment diretory.) and not docker-compose up

sudo docker-compose up bitcoin-for-peerplays
sudo docker-compose up hive-for-peerplays
sudo docker-compose up peerplays01 peerplays02 peerplays03 peerplays04 peerplays05 peerplays06 peerplays07 peerplays08 peerplays09 peerplays10 peerplays11 peerplays12 peerplays13 peerplays14 peerplays15 peerplays16

Do you see the same behaviour when the above mentioned commands are run?

I had always run the following commands to bring up the containers(run from /home/ubuntu/peerplays-utils/peerplays-qa-environment diretory.) and not docker-compose up sudo docker-compose up bitcoin-for-peerplays sudo docker-compose up hive-for-peerplays sudo docker-compose up peerplays01 peerplays02 peerplays03 peerplays04 peerplays05 peerplays06 peerplays07 peerplays08 peerplays09 peerplays10 peerplays11 peerplays12 peerplays13 peerplays14 peerplays15 peerplays16 Do you see the same behaviour when the above mentioned commands are run?

serkixenos commented

2021-10-08 12:23:25 +00:00

(Migrated from gitlab.com)

Are you saying that ubuntu-for-peerplays and peerplays-base started on its own, without you giving explicit command to bring them up? Like, they were down, and then you executed these commands

sudo docker-compose up bitcoin-for-peerplays
sudo docker-compose up hive-for-peerplays
sudo docker-compose up peerplays01 peerplays02 peerplays03 peerplays04 peerplays05 peerplays06 peerplays07 peerplays08 peerplays09 peerplays10 peerplays11 peerplays12 peerplays13 peerplays14 peerplays15 peerplays16

and ubuntu-for-peerplays and peerplays-base were up?

Are you saying that ubuntu-for-peerplays and peerplays-base started on its own, without you giving explicit command to bring them up? Like, they were down, and then you executed these commands ``` sudo docker-compose up bitcoin-for-peerplays sudo docker-compose up hive-for-peerplays sudo docker-compose up peerplays01 peerplays02 peerplays03 peerplays04 peerplays05 peerplays06 peerplays07 peerplays08 peerplays09 peerplays10 peerplays11 peerplays12 peerplays13 peerplays14 peerplays15 peerplays16 ``` and ubuntu-for-peerplays and peerplays-base were up?

prandnum commented

2021-10-08 12:25:30 +00:00

(Migrated from gitlab.com)

yes, that is correct.

serkixenos commented

2021-10-08 12:28:27 +00:00

(Migrated from gitlab.com)

Please create a screen cast, and share it here.
https://wiki.ubuntu.com/ScreenCasts

Please create a screen cast, and share it here. https://wiki.ubuntu.com/ScreenCasts

serkixenos commented

2021-10-09 21:13:59 +00:00

(Migrated from gitlab.com)

assigned to @prandnum and unassigned @serkixenos

hbelakon commented

2021-10-13 03:20:12 +00:00

(Migrated from gitlab.com)

added to epic &370

hbelakon commented

2021-10-13 14:14:30 +00:00

(Migrated from gitlab.com)

@serkixenos please estimate! I will put 8h/weight 1 for now

hbelakon commented

2021-10-13 14:14:41 +00:00

(Migrated from gitlab.com)

changed time estimate to 8h

serkixenos commented

2021-10-13 14:20:54 +00:00

(Migrated from gitlab.com)

Your estimation is fine.

prandnum commented

2021-10-14 06:54:29 +00:00

(Migrated from gitlab.com)

please find the scenario captured in the video (available here https://gitlab.com/PBSA/documentation/working-documents/-/blob/develop/exited-containers.mp4)

prandnum commented

2021-10-14 06:57:03 +00:00

(Migrated from gitlab.com)

assigned to @serkixenos

prandnum commented

2021-10-14 06:57:09 +00:00

(Migrated from gitlab.com)

unassigned @prandnum

serkixenos commented

2021-10-14 09:57:50 +00:00

(Migrated from gitlab.com)

These are helper containers, used in a building process, as a base layer for building other containers.
They are not usable in runtime context, and it is not important if they are running or not.
THey cant be removed the way you want, to be invisible to you, and this does not affect qa environment functionality in any way.

These are helper containers, used in a building process, as a base layer for building other containers. They are not usable in runtime context, and it is not important if they are running or not. THey cant be removed the way you want, to be invisible to you, and this does not affect qa environment functionality in any way.

serkixenos (Migrated from gitlab.com) closed this issue

2021-10-14 09:57:50 +00:00

after running the docker-compose up for peerplays witnesses peerplays-base and ubuntu-for-peerplays containers status are shown as stopped #189