This is what the log is saying since its started up again, I dont know if it has anythign to do with it…
2129 25c3f95 2017-04-06 14:54 CONSOLE GET ALERT / Layout has empty region
2128 898fd09 2017-04-06 14:53 CONSOLE GET ERROR /1 Unable to Process Queue of Player actions due to 2 of 2 player actions failed
2127 898fd09 2017-04-06 14:53 CONSOLE GET ERROR /1 Player action connection failed. E = XMR connection failed. Error = Failed to connect the ZMQ: Protocol not supported
2126 898fd09 2017-04-06 14:53 CONSOLE GET ERROR /1 Player action connection failed. E = XMR connection failed. Error = Failed to connect the ZMQ: Protocol not supported
I’m pretty sure its still a dns issue, I can ping bbc.co.uk for a normal terminal, I can ping 212.58.246.92 from within the container using
$ docker run busybox ping -c 1 212.58.246.92
If I try to start or restart the docker service with the daemon.json file there I get this as a result
Job for docker.service failed because the control process exited with error code. See “systemctl status docker.service” and “journalctl -xe” for details.
The systemctl says
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: e
Active: failed (Result: exit-code) since Fri 2017-04-07 09:05:16 BST; 18s ago
Docs: https://docs.docker.com
Process: 8047 ExecStart=/usr/bin/dockerd -H fd:// $DOCKER_OPTS (code=exited, s
Main PID: 8047 (code=exited, status=1/FAILURE)
Apr 07 09:05:16 signage systemd[1]: Starting Docker Application Container Engine
Apr 07 09:05:16 signage dockerd[8047]: time=“2017-04-07T09:05:16+01:00” level=fa
Apr 07 09:05:16 signage systemd[1]: docker.service: Main process exited, code=ex
Apr 07 09:05:16 signage systemd[1]: Failed to start Docker Application Container
Apr 07 09:05:16 signage systemd[1]: docker.service: Unit entered failed state.
Apr 07 09:05:16 signage systemd[1]: docker.service: Failed with result 'exit-cod
What I can’t work out is why the steps in that article aren’t working for you. The fact Docker won’t restart suggests that there’s an error in that file.
What is the exact content you’ve put in there?
Here, I’ve done the following:
sudo nano /etc/docker/daemon.json
In that file, I’ve put exactly
{
"dns": ["192.168.0.1", "8.8.8.8"]
}
Then I restarted the Docker daemon
sudo service docker restart
Then I get the DNS server configured correctly:
docker run busybox nslookup google.com
alex@alex-desktop:~$ docker run busybox nslookup google.com
Unable to find image 'busybox:latest' locally
latest: Pulling from library/busybox
7520415ce762: Pull complete
Digest: sha256:32f093055929dbc23dec4d03e09dfe971f5973a9ca5cf059cbfb644c206aa83f
Status: Downloaded newer image for busybox:latest
Server: 192.168.0.1
Address 1: 192.168.0.1
Name: google.com
Address 1: 2a00:1450:4009:811::200e lhr25s15-in-x0e.1e100.net
Address 2: 172.217.23.14 lhr35s01-in-f14.1e100.net
Well I’ve done it your way and its worked a charm, dns pinging, ticker data being populated.
Must of not liked the way I did it, I created the file by browsing to the location and right clicking and creating a new empty document then editing with gedit.
Thank you so much for your on going help with getting me up and running on docker and all the other issues, I guess your patience is wearing a bit thin with me but i really appreciate it.