To be able to run docker-compose, I need to have docker desktop running, otherwise I'll get connection refused errors.
Is there a way I can start docker WITHOUT starting the desktop app to be able to then run what needs to be run?
Related
I am a Windows user trying to run "docker-compose up" command but continue to get the error in title. I am writing this code in Ubuntu using WSL 2.
I have tried everything - from this post to this post - and have made sure I have docker installed correctly. When I run "sudo service docker start" I get "docker: unrecognized service". I'm thinking of switching to Podman (though would prefer not to if can avoid it) to get past having to use the docker daemon- though I can't seem to get this to run in wsl.
Any and all guidance would be appreciated!
This typically means that your Docker Service is not running.
Open RUN and type services.msc, then click OK or hit enter
Search for service named as Docker Desktop Service.
Make sure it is running.
You can also set the Docker service to start when you login from Docker Desktop GUI setting panel
I'm using Docker Desktop for Mac to run a Docker container running FileMaker Server 19 on Ubuntu Server. When I start up Docker Engine from scratch, i.e., no daemons running, then start the container, all works as expected. I can open FileMaker's admin console in a browser and I can open the hosted database with FileMaker Pro client app.
But if I stop the container from running and quit Docker Desktop and try to run the container again it starts up but I can't establish connections to it either with the FileMaker Pro client or a browser. The solution I've found is to quit the Docker processes that continue to run in the background and make the Docker engine restart from scratch. This obviously isn't desirable and it indicates to me that something isn't configured correctly in the network connection to the container.
I'm new to Docker, so apologies in advance if I'm missing something very basic. I searched for an solution online but can't find one.
I'm using docker desktop for mac.
I have built a docker image for a Node.js app that connects to an external MongoDB database via URI (the db is running on an AWS instance that I'm connected to over vpn). This works fine - I run the container and the app can connect to the database. Happy days.
Then...
I enable Kubernetes on docker desktop. I apply a deployment.yml to run the container but this deployment fails when trying to connect to the db. From my app's logs (I'm using mongoose):
MongooseServerSelectionError: connect EHOSTUNREACH [MY DB IP] +30005ms
Interestingly...
I can now no longer connect to the db by running my docker container either. I get the same error.
I have to disable kubernetes, restart docker desktop (twice), prune my previous container and network, and re-run my container. Then it will work again.
As soon as I enable kubernetes again, the db becomes unreachable again.
Any ideas why this is and/or how to fix it?
So the issue for us turned out to be an IP range clash. Exactly the same as described in this SO question:
Change Kubernetes docker-for-desktop cluster network ip
Unfortunately, like this user, we haven't been able to find a solution
I run testcafe in a custom docker container and I have the web app running in different docker container (or docker-compose). If I use the app from the web browser I go to the localhost:8080
How can I access the app from testcafe docker container?
> docker run -ti mycustom/testcafe firefox /tests/*
Error details:
Failed to find a DNS-record for the resource at "http://localhost:8080/".
I tried to add --network=network-name but it didn't help.
You don't need to explicitly configure the network with docker-compose. For the solution without docker-compose, refer to this thread.
I'm really new to docker. I have installed docker on my windows 10 laptop.
Then I started docker service. Please refer below screenshots.
However it shows docker running icon of docker shows it is false.
This is out put I got in power shell opened as Admin mode.
Please support me to bring to docker working status.