Stuck On Pulling Docker Image from docker-compose.yml

cyberark / conjur-quickstart

Start securing your secrets and infrastructure by installing Conjur, using Docker and the official Conjur containers on DockerHub.

Apache License 2.0

33 stars 36 forks source link

Stuck On Pulling Docker Image from docker-compose.yml #39

Closed ravics09 closed 3 years ago

ravics09 commented 3 years ago

Summary

Using Docker Desktop on Windows 10, When trying to pull image it stuck and not responding. Tried to run below command $ docker-compose pull

After that it is not responding.

Steps to Reproduce

Steps to reproduce the behavior:

Clone the repo https://github.com/cyberark/conjur-quickstart.git
cd conjur-quickstart
docker-compose pull

Expected Results

It should pulled the docker images defined in docker-compose.yml

Actual Results (including error logs, if applicable)

After running the given command its not responding.

Environment setup

Docker Desktop Community 3.1.0 Also tried on Docker Desktop Community 2.5.0.1

BradleyBoutcher commented 3 years ago

Hi Ravi,

This sounds like it could be an issue with your docker daemon. Let's try a few things to troubleshoot:

Run docker-compose --verbose pull to see verbose output, this may show why its hanging
Can you verify that docker-compose pull is working with other configurations?
Have you tried running ./test_workflow.sh from the conjur-quickstart directory?
If you run docker-compose up bot-app, is there output, or does it hang?

ravics09 commented 3 years ago

Hi Bradley,

I tried to run

docker-compose --verbose pull

and getting below info dockerissue

While running the below command

docker-compose up bot-app

Getting Error: creating network "conjur-quickstart_default" with the default driver ERROR: No such service: bot-app

doodlesbykumbi commented 3 years ago

@ravics09 Restarting your docker daemon might help resolve the docker-compose pull issue. After that you should be able to follow the rest of the quick-start.

re: docker-compose up bot-app

That's failing because of a typo. The service is bot_app, instead of bot-app. You shouldn't need to bring up that service in isolation if you follow the rest of the quick-start once docker-compose pull succeeds.

doodlesbykumbi commented 3 years ago

For what it's worth, I've just successfully run through the flow on a fresh checkout of the repo on Windows.

doodlesbykumbi commented 3 years ago

Closing this now, please reopen and let us know if the issues persists.