Hi James! I agree with you that there are many ways to fail in this path. Which instructions are you trying to follow exactly (sorry, there are many options)?
I wrote these instructions https://github.com/apache/fineract-cn-docker-compose/#2-deploy-fineract-manually-using-postman while Courage wrote provisioning with bash scripts (probably we should split them to two separate instructions for clarity). Also a bit depends on your operating system. I have tested my stuff with Mac and I know Courage has Linux. Some parts of Docker work differently - for example in Linux you the IP addresses assigned to individual containers are visible to the host machine from outside Docker. In Mac the internal IP-s are completely hidden. What OS do you use? > Anyway, I get only to the verification part, where I find the verify statements don't work for me. > e.g. http://eureka:8761/ >Should this instead be IP of docker machine on port 8761 ? I now realised that hostname "eureka" was missing from the instructions here: https://github.com/apache/fineract-cn-docker-compose/#use-the-postman-scripts-when-running-locally so I just added it to the first line. Make sure to update your hosts file accordingly. "eureka" is the dns name inside Docker. To make it visible to the host machine (everything outside docker but still in same machine) I have used a trick to edit hosts file of the host machine so that if you try to find "eureka" it resolves to "localhost" and since you have exposed port 8761 from Docker daemon to your host machine it should work. > And, can I use IntelliJ Community version or do I need to have the paid version so that I can follow your instructions literally? Community edition should be perfectly fine. As much I know we are not using any paid features of IntelliJ anywhere in the instructions (so even Eclipse should do) $docker-compose up -d WARNING: Some services (activemq, cassandra, eureka) use the 'deploy' key, which #will be ignored. Compose does not support 'deploy' configuration - use `docker #stack deploy` to deploy to a swarm. ERROR: Couldn't connect to Docker daemon - you might need to run `docker-machine start default`. Try running the command without "-d" flag. This way it starts it in foreground without daemon mode. Kind regards Juhan Kontakt James Dailey (<[email protected]>) kirjutas kuupäeval R, 20. detsember 2019 kell 06:37: > Hi @Juhan, @Courage Angeh <[email protected]> > > I am willing to try to help with this documentation of getting fineractCN > up and running. Once I go through it, it will include all of the possible > ways to badly go about it. :) > > Below is my path through some docker and docker compose issues. But, its > probably too much detail. Could belong in some extra notes below the main > instructions. > > Anyway, I get only to the verification part, where I find the verify > statements don't work for me. > e.g. http://eureka:8761/ > Should this instead be IP of docker machine on port 8761 ? > ? > > and while I have IntelliJ installed and running, and I have a local > provisioner repo, I don't see the screen step that you show for the > provisioner. > > And, can I use IntelliJ Community version or do I need to have the paid > version so that I can follow your instructions literally? > > > --- Docker compose and starting a local docker machine. > > > After following the first part of the directions @Juhan wrote at > > > https://cwiki.apache.org/confluence/display/FINERACT/Bare+minimum+to+run+Fineract-CN+locally > > > > Verify that Docker is working > > $docker > > #returns something intelligent, the list of commands > > > > here is a bit of terminal back and forth - > > > $ pwd > > # returns > > /Users/{username}/code/mifos/fineract-cn-docker-compose/external_tools > > > $Docker-compose up -d > > #returns > > you may need to run > > docker-machine start default > > > $docker-machine create default > > #returns… finally > > Docker is up and running! > > To see how to connect your Docker Client to the Docker Engine running on > this virtual machine, run: docker-machine env default > > > $docker-machine env default > > # this should display, something like: > > export DOCKER_TLS_VERIFY="1" > > export DOCKER_HOST="tcp://192.168.99.102:2376" > > export > DOCKER_CERT_PATH="/Users/{youruser}/.docker/machine/machines/default" > > export DOCKER_MACHINE_NAME="default" > > Run this command to configure your shell: > > eval $(docker-machine env default) > > > $docker-compose up -d > > WARNING: Some services (activemq, cassandra, eureka) use the 'deploy' > key, which #will be ignored. Compose does not support 'deploy' > configuration - use `docker #stack deploy` to deploy to a swarm. > > ERROR: Couldn't connect to Docker daemon - you might need to run > `docker-machine start default`. > > > $ docker-machine ls > > NAME ACTIVE DRIVER STATE URL > SWARM DOCKER ERRORS > > default - virtualbox Running tcp://192.168.99.102:2376 > v19.03.5 > > > $docker info > > #Returns > > Client: > > Debug Mode: false > > > Server: > > ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. > Is the docker daemon running? > > errors pretty printing info > > > > $eval "$(docker-machine env default)" > > # this seems to have resolved the issue with the docker daemon > > note that it was mentioned above > > > $ docker-compose up -d > > # this runs and ends with > > Creating postgres ... done > > Creating activemq ... done > > Creating cassandra ... done > > Creating eureka ... done > > > --- > > > > @jdailey67 > > > > > >
