error starting userland proxy on ubuntu
Opened this issue · 9 comments
When I try to start azk on my ubuntu 15.04, I get this error:
azk: Please wait, this process may take several minutes
azk: Loading settings and checking dependencies.
azk: Checking version...
azk: azk 0.15.0 detected
azk: Cleaning 0 lost containers
azk: Settings loaded successfully.
azk: Agent is being started...
azk: Trying to connect to docker (unix:///var/run/docker.sock) (timeout: 20s)...
azk: Starting azk dns service...
azk: Error: HTTP code is 500 which indicates error: server error - Cannot start container b17ccc7d4632316a6cebce00c940eeca653164c69d7980c57267c5e35b0f5462: Error starting userland proxy: listen udp 172.17.42.1:53: bind: cannot assign requested address
azk: Agent is being stopped...
azk: Agent has been successfully stopped.
azk: azk agent is required but is not running (try `azk agent status`)
I think that I set something wrong, but I just follow the installation steps for ubuntu 14:04 documentation.
hi @AlvesJonas
the docker is running?
$ docker run hello-world
Hello from Docker.
This message shows that your installation appears to be working correctly.
To generate this message, Docker took the following steps:
1. The Docker client contacted the Docker daemon.
2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
3. The Docker daemon created a new container from that image which runs the
executable that produces the output you are currently reading.
4. The Docker daemon streamed that output to the Docker client, which sent it
to your terminal.
To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash
Share images, automate workflows, and more with a free Docker Hub account:
https://hub.docker.com
Hello from Docker.
This message shows that your installation appears to be working correctly.
To generate this message, Docker took the following steps:
1. The Docker client contacted the Docker daemon.
2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
3. The Docker daemon created a new container from that image which runs the
executable that produces the output you are currently reading.
[...]
I think it's running
you are on a network with proxy?
no
let's talk by gitter to see if we reach a quicker resolution. Can be?
https://gitter.im/azukiapp/azk/pt
As spoken in https://gitter.im/azukiapp/azk/pt, it was identified that the problem was activated dnsmasq. In azk installation documentation in ubuntu there is a step (optional) that instructs how.
http://docs.azk.io/en/installation/linux.html#ubuntu-trusty-1404-lts-64-bit
I suggest that if possible let's add a way to detect this problem and handle the error with instructions or automatic correction.
Hi,
Starting from docker 1.9.0 default docker bridge is 172.17.0.1 instead of 172.17.42.1. Is there any hardcoded configuration to use 172.17.42.1 ?
@teodor-pripoae azk doesn't have hardcoded Docker IP, but when upgrading to 1.9.0 (using a new Docker IP), it's needed to recreate the /etc/resolver/dev.azk.iofile:
$ sudo rm -f /etc/resolver/dev.azk.io
$ azk agent start
We're working on a feature so azk can identify the Docker IP change and auto-update the resolver file. I'll be released in the next few versions.
I installed this today on a friend's computer running Arch Linux. He had docker running but a docker upgrade was pending and azk used older docker config. Then after restart it still used the old docker config.
I fixed this by reverting docker to run on old bridge configuration, --bip 172.17.42.1/24. I didn't know about this resolver config. Thanks!