I am trying to run the docker container for freeswitch from the following URL
https://hub.docker.com/r/bettervoice/freeswitch-container/
When i issue the following command
CID=$(sudo docker run --name freeswitch -p 5060:5060/tcp -p 5060:5060/udp -p 5080:5080/tcp -p 5080:5080/udp -p 8021:8021/tcp -p 7443:7443/tcp -p 60535-65535:60535-65535/udp -v /home/ubuntu/freeswitch/conf:/usr/local/freeswitch/conf bettervoice/freeswitch-container:1.6.6)
After a while the following error is displayed
docker: Error response from daemon: driver failed programming external connectivity on endpoint freeswitch (d805c283f72bc75752a0eb354195e4c7b606b54fed604d238df826261ceeeb43): Error starting userland proxy:.
ERRO[0509] error waiting for container: context canceled
Please help.
Related
I am using windows10, redis-64bit, I started a redis container with command:
docker run --name myredis -d redis redis-server --appendonly yes
when I try to connect to this container using:
redis-cli -h 192.168.99.1 -p 6379
it shows:
Could not connect to Redis at 192.168.99.1:6379: Unknown error
here, 192.168.99.1 is my virtual machine ip address, anyone know how to solve this issue, thanks!
To connect to a redis container from a remote server you should do the following:
Start redis container on host (192.168.99.1):
docker run --name myredis -p 7000:6379 -d redis redis-server
Connect via remote server:
redis-cli -h 192.168.99.1 -p 7000
I use following commands to run my project.
docker run -it -p 8080:80 --rm -v "d:\project1:/var/www/html" myimage....
This was running fine till yesterday. But when I tried the same command, I am getting error
docker: Error response from daemon: failed to create endpoint loving_dubinsky on network nat: hnsCall failed in Win32: The specified port already exists. (0x803b0013).
I checked if 8080 port is being used or not using following command.
netstat -ano | findstr :8080
I could not see this port is being used.
How can I fix this issue?
Thank You.
Run "docker ps" command.
From "docker ps" output, you will come to know if there is any container which is listening to port 8080.
You can kill that container using "docker kill container_id".
Now your port 8080 will be free.
I'm trying to run a postgres docker container on Windows 10.
I've installed postgres using the Linux container as I couldn't do so using the Windows container.
While running the below in powershell
docker run -d --name pg-flowthru --env-file ./database/env.list -p 5432:5432 --rm -v ${PWD}:/docker/volumes/postgres:/var/lib/postgresql/data postgres
(env.list contains database credentials), I'm getting the below error:
C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: invalid mode: /var/lib/postgresql/data.
See 'C:\Program Files\Docker\Docker\Resources\bin\docker.exe run --help'.
C drive is already in the "Shared Drives" in Docker Desktop
I think this may be an issue with path, but I'm new to docker and can't figure it out.
From here
More info here
A volume has to be created first:
docker volume create postgresql-volume
The postgres container can now be run using the previously created volume:
docker run -d --name pg-flowthru --env-file ./database/env.list -p 5432:5432 -v 'postgresql-volume:/var/lib/postgresql/data' postgres
Listing the running containers now shows the above container running.
When there was a configuration problem and docker instance is not coming up, how to do the troubleshooting ..
RajRajen:lb4b-my rajrajen$ docker run -d -t -i -p 80:80 -p 443:443 --name my_nginx_v4 my_nginx_v4
f459a9d666f1596dd77c1095b7256075b183fe8b7997c17e8f7b1640606bb075
RajRajen:lb4b-my rajrajen$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
RajRajen:lb4b-my rajrajen$ docker ps
Results in NO Result. How to identify the reason for the failure. There are many links if there is a running instance.
docker exec -ti /bin/bash
Ref : https://askubuntu.com/questions/505506/how-to-get-bash-or-ssh-into-a-running-container-in-background-mode
Thanks
Just gave a try to find whats in
When there was a configuration problem and docker instance is not coming up, how to do the troubleshooting ..
RajRajen:lb4b-my rajrajen$ docker log
5139b2417a39563a3848cc796b6c572d6508c0b862c4d13dceac9d59b3936420
And this log message is available
RajRajen:lb4b-fe rajrajen$ docker logs 5139b2417a39563a3848cc796b6c572d6508c0b862c4d13dceac9d59b3936420
2015/11/27 01:11:58 [emerg] 1#1: unknown "redir_match" variable
nginx: [emerg] unknown "redir_match" variable
This hint helped to resolve the issue .
Thanks ...
Just gave a try to find whats in it.
When there was a configuration problem and docker instance is not coming up, how to do the troubleshooting ..
A) Identify the instance
RajRajen:lb4b-my rajrajen$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1a03bab01e40 lb4b-my "tail -f /dev/null" 7 minutes ago Excited(1) gc_lb4b-my
And this hidden container id helps to figure out further issue.
B) yet thats not enough to troubleshoot further issues inside the application
So, did the following to keep the docker running and then go inside the docker and execute the command that fails manually.
docker run -d -P --name gc_lb4b-my fe_lb4b-my tail -f /dev/null
I'm trying to set up my own docker registry on a amazon ec2.
If I launch it such as:
docker run -p 5000:5000 registry
it's working without any problem.
However when I try to launch it with s3 using my credential such as:
docker run -p 5000:5000 -e SETTINGS_FLAVOR=s3 -e AWS_REGION=eu-west-1 -e AWS_BUCKET=$BUCKET -e STORAGE_PATH=/registry -e AWS_KEY=$AWS_KEY -e AWS_SECRET=$AWS_SECRET registry
I get
alexis#ubuntu:/home/web$ sudo docker push amazon.ip:5000/web
2014/10/07 00:57:38 Error: Invalid Registry endpoint: Get http://amazon.ip:5000/v1/_ping: dial tcp amazon.ip:5000: connection refused
Thanks for your help