Open FDiskas opened 8 years ago
This problem occurs when the firewall fedora is stowed, preventing the correct behavior of the azk dns-resolver.
Workaround:
# stop azk agent
$ azk agent stop
# stop dnsmasq service
$ systemctl stop dnsmasq.service
# stop firewall
$ sudo systemctl stop firewalld
# restart docker service
$ sudo service docker stop
$ sudo service docker start
# start azk agent
$ azk agent start
to test that it works correctly, run:
$ azk shell --image azukiapp/alpine -- ping -c 4 dev.azk.io
PING dev.azk.io (192.168.51.4): 56 data bytes
64 bytes from 192.168.51.4: seq=0 ttl=64 time=0.341 ms
64 bytes from 192.168.51.4: seq=1 ttl=64 time=0.102 ms
64 bytes from 192.168.51.4: seq=2 ttl=64 time=0.106 ms
64 bytes from 192.168.51.4: seq=3 ttl=64 time=0.079 ms
--- dev.azk.io ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 0.079/0.157/0.341 ms
discussion: https://gitter.im/azukiapp/azk?at=565311da06a214f1080b3d07
sudo firewall-cmd --permanent --zone=public --add-port=53/udp
sudo systemctl restart firewalld
good @FDiskas that way continues to work even after the restart, right?
true
nice. Then we can make a small improvement in the installation script.
Please do not delete... Issue in progress... Trying to reproduce.