nzbget | Efficient Usenet Downloader | Download Utils library

Try:

The first command starts with a slash. Not a ./

/ Means look in the root directory. ./ Means local

As you said in the comments to your question, you run your containers with docker start . After you run them all, take a look at docker network ls - this command lists all networks. You should have the same amount of networks as you have containers - because docker start creates a unique (and separated) network and puts your container there. Therefore you can't communicate.

To fix this, you have to put your containers in one network. To do so you could either put your services into docker-compose.yml and run them with docker-compose up. For this read Docker Compose section of the docs.

Or you could put already existing and running containers onto same network manually. For this you could use docker network connect, for example docker network connect .

Generally, to grasp all the aspects, my answer would be incredibly long and therefore I am providing you with those two tips. I hope it's enough for a good nudge in the right direction. I strongly encourage you to read more in the docs.