No masternode found

[Mat001]

Running python vmnet/test_bootstrap.py gives error (@StuartFarmer )

Exception caught on LProcess-1:
(1, 'NotMaster', 'No nodes found, cannot bootstrap yourself because you are not a masternode')

I get similar output when running test_secure_connection.py.

Attaching full log
test_bootstrap.log

[wywfalcon]

Master has been updated recently and tests work on our end. please get the latest version and see if this still occurs.

Note that, this only occurs when after 3 retries on attempting to discover nodes on your machine (in this case, docker containers are trying to discover each other over their own docker bridge network).

If this is still a problem, try this:
Perhaps the images that you are using (specified in "cilantro-bootstrap.yml"), being cached previously, are outdated. You can use lamden/cilantro:ci instead cilantro_base.dev for the image instead and remove the "build" section under the "base" service.

[Mat001]

Thx @wywfalcon
I wiped out all docker images on my machine and updated the repo.
After image is built from scratch, it still throws no masternode found and browser remains empty.
I'll try now the second option you suggested

[Mat001]

Second option also didn't work. Well, there were no errors. But browser was empty. See attached log.
Also, you guys have a private image on docker-hub ---> lamden/cilantro:ci?

Here is my modified cilantro-bootstrap.yml file:

version: "2.3"
networks:
cilantro:
driver: bridge
ipam:
config:
- subnet: 172.29.0.0/16
iprange: 172.29.5.0/24
gateway: 172.29.5.253
services:
base:
image: lamden/cilantro:ci
volumes:
- type: bind
source: /storage/docker/mysql-datadir
target: /var/lib/mysql
mgmt:
ip: 172.29.5.0
stdin_open: true
tty: true
image: lamden/cilantro:ci
volumes:
- type: bind
source: ${LOCAL_PATH}/cilantro
target: /app/
masternode:
ip: 172.29.5.1
stdin_open: true
tty: true
image: lamden/cilantro:ci
volumes:
- type: bind
source: ${LOCAL_PATH}/cilantro
target: /app/
witness:
ip: 172.29.5.x
range:
- 2
- 3
stdin_open: true
tty: true
image: lamden/cilantro:ci
volumes:
- type: bind
source: ${LOCAL_PATH}/cilantro
target: /app/
delegate:
ip: 172.29.5.x
range:
- 4
- 6
stdin_open: true
tty: true
image: lamden/cilantro:ci
volumes:
- type: bind
source: ${LOCAL_PATH}/cilantro
target: /app/

bootstrap_log_ci.txt

So, not sure what is going on. Another person has problems runing bootstrap. He is getting

INFO No need to build
The Compose file './docker-compose.yml' is invalid because:
services.delegate_4.volumes contains an invalid type, it should be a string
services.delegate_5.volumes contains an invalid type, it should be a string

[constfilin]

Greetings all. I indeed have a trouble running cilantro. Here's my environment

1. pulled the latest stuff from https://github.com/Lamden/cilantro.git to /home/cf/Work/Lambden/cilantro
2. Ubuntu
   (venv) cf@cfdell:~/Work/Lambden/cilantro$ uname -a Linux cfdell 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
3. Python version is Python 3.6.5
4. docker version is Docker version 17.12.1-ce, build 7390fc6
5. docker-compose version is 1.17.1, build unknown
6. I set a few environment variables:
   LOCAL_PATH=/home/cf/Work/Lambden/cilantro
PYTHONPATH=/home/cf/Work/Lambden/cilantro:/home/cf/Work/Lambden/cilantro/tests/
7. I did cd tests/vmnet and ran python test_bootstrap.py
8. I've got lots of errors like Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.35/containers/prune: dial unix /var/run/docker.sock: connect: permission denied but I had docket container started anyway:
   cf@cfdell:~/Work/Lambden$ ps aflx | grep docker
0 1001 15463 14433 20 0 15652 1080 pipe_w S+ pts/3 0:00 \_ grep --color=auto docker
4 0 17505 1 20 0 1276804 44660 - Ssl ? 3:07 /usr/bin/dockerd -H fd://
4 0 17539 17505 20 0 1292428 21992 - Ssl ? 3:32 \_ docker-containerd --config /var/run/docker/containerd/containerd.toml
cf@cfdell:~/Work/Lambden$
9. While the docket was running navigating to port :4320 of the host running the container was producing an empty HTML document with lots of JS and CSS but no node status at all.

I hope that the above details will be helpful in diagnosing the problem but if they do not, please do not hesitate to reach out to me in Lamden developer channel.