Docker Plugin

1. offizieller Beitrag
    • Offizieller Beitrag

    If I reference this thread it might start the ball rolling in particular this post


    Initially I thought I had no issues, but I did notice that that some of the containers had not been updated, so a quick investigation revealed that some should have been. So I checked watchtowers log file, this appeared to working but full of errors relating to watchtower being unable to communicate with the current container list.


    So restarted watchtower and waited for it to refresh still the same errors, cleared the log file (mistake!!) and restarted waited 10 mins refreshed checked the log file empty!


    Delete the container, delete the image and start again -> the container has now been up for 30+ minutes and this is the content of the log file:
    time="2018-11-20T10:20:19Z" level=info msg="First run: 2018-11-20 10:25:19 +0000 GMT" that's it nothing else.


    I then ran service docker restart and checked service docker status ->

    The containers are now showing an up time of 12 minutes and the output from the log file is;


    time="2018-11-20T10:20:19Z" level=info msg="First run: 2018-11-20 10:25:19 +0000 GMT"
    time="2018-11-20T10:58:18Z" level=info msg="Waiting for running update to be finished..."
    time="2018-11-20T10:58:33Z" level=info msg="First run: 2018-11-20 11:03:33 +0000 GMT"


    As you can see "First run" is 11:03 some 9 minutes previous and that is all that's in the log, considering watchtower is supposed to check every 5 mins something is wrong.


    I have also discovered that stopping the container and then modifying errors, in fact the error seems to point to the container being deleted -> odd!


    As it doesn't appear to be able to modify the container I'm going to delete it and set the --debug option in the command setting and see if that reveals anything.

    • Offizieller Beitrag

    There is obviously a problem this is the output from watchtower using the --debug command:


    Looking at Emby this is the information from Emby Docker;



    This is my current Emby version:



    As you can see this should have been updated, if the issue is related to credentials in the /config.json I don't know how to fix it :(

    • Offizieller Beitrag

    Ok after the debug log output I just checked the watchtower log file:


    Code
    time="2018-11-20T12:45:07Z" level=info msg="First run: 2018-11-20 12:50:07 +0000 GMT"
time="2018-11-20T18:10:44Z" level=info msg="Found new linuxserver/heimdall:latest image (sha256:0f3d3ed1dcefff46e646eaf963d20d0ad8ea5629a071f6861b5ef96ae602fe25)"
time="2018-11-20T18:10:51Z" level=info msg="Stopping /Heimdal (c563961b1c049ac67712e399f26f3d3749973ad7682bea374aacc40c3ba9ce09) with SIGTERM"
time="2018-11-20T18:11:41Z" level=info msg="Creating /Heimdal"
time="2018-11-20T18:11:52Z" level=info msg="Removing image sha256:5336ab4f0ab0f264bf86ae403379250000c4213c22d79d26702bfff924338e76"
time="2018-11-20T18:35:17Z" level=info msg="Found new linuxserver/heimdall:latest image (sha256:bfbb97bf8b4db55091e4e6d33fcb2729f62b5a90e509debd0617a95c392d1568)"
time="2018-11-20T18:35:24Z" level=info msg="Stopping /Heimdal (8b447dd2786396e22c9834b2c88c9db440421ad4fe123806e24928a9ccbac480) with SIGTERM"
time="2018-11-20T18:36:53Z" level=info msg="Creating /Heimdal"
time="2018-11-20T18:37:00Z" level=info msg="Removing image sha256:0f3d3ed1dcefff46e646eaf963d20d0ad8ea5629a071f6861b5ef96ae602fe25"

    It appears that Heimdall has updated....so why the errors in the debug log.


    Also by adding --cleanup into Command under Extra Arguments watchtower will remove the old image, but I still don't understand the debug output.

    Sorry to totally intrude in your post but i need to know how did you enable ipv6 on docker? its getting me totally crazy

    nvm found that i missed to add --fixed-cidr-v6...i thought that as im going to give fixed ips to every container from the router i didnt need to set it but apparently i was wrong, now i need to know if you set up anything else, i dont even want ips assigned by the router...im going to test some docker anyway and report back...

    • Offizieller Beitrag

    There does appear to be a problem;


    Code
    time="2018-11-22T04:10:17Z" level=info msg="Unable to update container /Heimdal, err='Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 127.0.0.1:53: read udp 127.0.0.1:56930->127.0.0.1:53: i/o timeout'. Proceeding to next."
time="2018-11-22T04:10:27Z" level=info msg="Unable to update container /watchtower, err='Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 127.0.0.1:53: read udp 127.0.0.1:43048->127.0.0.1:53: i/o timeout'. Proceeding to next."
time="2018-11-22T04:10:37Z" level=info msg="Unable to update container /Cloudcmd, err='Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 127.0.0.1:53: read udp 127.0.0.1:58300->127.0.0.1:53: i/o timeout'. Proceeding to next."
time="2018-11-22T04:10:47Z" level=info msg="Unable to update container /PiHole, err='Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 127.0.0.1:53: read udp 127.0.0.1:37341->127.0.0.1:53: i/o timeout'. Proceeding to next."
time="2018-11-22T04:10:57Z" level=info msg="Unable to update container /Glances, err='Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 127.0.0.1:53: read udp 127.0.0.1:50281->127.0.0.1:53: i/o timeout'. Proceeding to next."
time="2018-11-22T04:11:07Z" level=info msg="Unable to update container /Wetty, err='Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 127.0.0.1:53: read udp 127.0.0.1:49667->127.0.0.1:53: i/o timeout'. Proceeding to next."
time="2018-11-22T04:11:17Z" level=info msg="Unable to update container /EmbyServer, err='Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 127.0.0.1:53: read udp 127.0.0.1:46054->127.0.0.1:53: i/o timeout'. Proceeding to next."

    Whilst you search for the specified error there is either no specific 'do this' as a 'one size fits all' or there is a recommendation to edit x conf file which in omv usually tells you not to do this as the file will be overwritten.
    There seems to be a few choices, remove then reinstall the plugin, remove the plugin and docker -> reinstall docker from the cli and install portianer or cockpit as recommended by @TechnoDadLife reinstall docker and the plugin from the gui.
    As I now have Pi-Hole running on a Pi via DietPi, Emby could go back to the cli, the others I could without and go back to using the cli anyway. What was once working, then appeared to work after the update has obviously gone pear shaped for a reason I am unable to find a conclusive answer.


    EDIT: Investigation, it appears my router decided to reboot during the early hours, hence the above error!!

    • Offizieller Beitrag

    I'm now seeing this in syslog:


    dockerd[28186]: time="2018-11-25T22:10:10.641144209Z" level=info msg="Attempting next endpoint for pull after error: unauthorized: authentication required"
    dockerd[28186]: time="2018-11-25T22:10:10.641320855Z" level=error msg="Handler for POST /v1.24/images/create returned error: unauthorized: authentication required"


    They are also appearing in daemon.log as well and similar in watchtower;


    level=info msg="Unable to update container /watchtower, err='Error response from daemon: unauthorized: authentication required'. Proceeding to next."
    level=info msg="Unable to update container /EmbyServer, err='Error response from daemon: unauthorized: authentication required'. Proceeding to next."
    level=info msg="Unable to update container /Glances, err='Error response from daemon: error parsing HTTP 404 response body: invalid character 'p' after top-level value: "404 page not found\n"'. Proceeding to next."


    If this is a case of pull the plug and start again, I'm fine with that, but at present a search is drawing very little information

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden