Accenture / adop-docker-compose

Talk to us on Gitter: https://gitter.im/Accenture/ADOP
https://accenture.github.io/adop-docker-compose
Apache License 2.0
764 stars 573 forks source link

Quickstart fails to spin up adop | registry container restarts forever #288

Open vikramkunisetty opened 6 years ago

vikramkunisetty commented 6 years ago

Able to reproduce this after finding the same behavior atleast 3-4times now:

Followed the instructions in the quickstart and performed the steps as follows:

  1. Launched an EC2 - Ubuntu t2.micro to spin up ADOP
  2. Installed Docker, Docker-machine, docker-compose
    
    root@ip-172-31-5-91:~# docker-compose --version
    docker-compose version 1.22.0, build f46880fe
    root@ip-172-31-5-91:~# docker-machine --version
    docker-machine version 0.14.0, build 89b8332
    root@ip-172-31-5-91:~# docker --version
    Docker version 18.06.0-ce, build 0ffa825

git clone https://github.com/Accenture/adop-docker-compose.git

3. Quikcstart Script: 
`./quickstart.sh -t aws -m adop -c vpc-xxxx -r eu-west-1 -z c -a AAA -s SSS -u prd -p xxxx`

    tail of the log: 

Creating sensu-server ... done

  1. Stopped this and connected to the machine: and found that all the services are up and running except the registry container is restarting forever: d3c255fb6e44 registry:2.5.1 "/entrypoint.sh /etc…" 14 minutes ago Restarting (1) 29 seconds ago registry Not sure if this could be an issue but this worked only once when upgraded the image version to 2.6 in compose.yml.
  2. docker logs for jenkins, gerrit etc did not work with the below error:
    
    root@adop:~# docker logs jenkins
    Error response from daemon: configured logging driver does not support reading
    root@adop:~# docker logs jenkins-slave
    Error response from daemon: configured logging driver does not support reading
    root@adop:~# docker logs registry
    Error response from daemon: configured logging driver does not support reading
6. Tried to restart with more options: 
`root@ip-172-31-5-91:~/adop-docker-compose# ./adop compose -m adop init --with-stdout
`
Found out the similar issues reported in #285 

--tail of the log: 

Recreating sensu-uchiwa ... done Recreating sonar ... done


7. performed the logs check of Jenkins and found this extract: 

root@adop:~# docker logs 70a70033eb1ddb93f1e6a5f8e4d4bff6145107cfc3aa99f319977e49e0da036f Genarate JENKINS SSH KEY and add it to gerrit Setting up your default SCM provider - Gerrit... Generate Sonar authentication token Generating Sonar Authentication Token


Detailed logs: [github_adop.log](https://github.com/Accenture/adop-docker-compose/files/2305186/github_adop.log)

> used the latest commit on OS Version "16.04.4 LTS (Xenial Xerus)"