Docker - Cannot Check for Update or Add Repo's


26 posts in this topic Last Reply

Recommended Posts

Working for me. My folders are not as clean as yours (probably could get rid of some of it) but I don't see anything that should be related.

 

root@unSERVER:~# ls /boot/config/plugins
NerdPack/                    dynamix.plg*                 ntfs-3g-x86_64.plg*
NerdPack.plg*                dynamix.s3.sleep/            powerdown/
XTermTitle.plg*              dynamix.s3.sleep.plg*        powerdown-x86_64.plg*
apache/                      dynamix.system.autofan/      snap/
apcupsd/                     dynamix.system.autofan.plg*  snap-x86_64.plg*
dockerMan/                   dynamix.system.info/         unRAIDServer.plg*
dynamix/                     dynamix.system.info.plg*     virtMan/
dynamix.active.streams/      dynamix.system.stats/        webGui/
dynamix.active.streams.plg*  dynamix.system.stats.plg*    webvirtmgr/
dynamix.cache.dirs/          dynamix.system.temp/         wol/
dynamix.cache.dirs.plg*      dynamix.system.temp.plg*     wol.plg*
dynamix.kvm.manager/         images/
dynamix.kvm.manager.plg*     ntfs-3g/

root@unSERVER:~# ls /boot/config/plugins/dockerman
images/  template-repos*  templates/  templates-user/  webui-images/
root@unSERVER:~#

Link to post

This isn't the first time this has been reported.  Someone else used a VPN connection after getting this error and it resolved the issue.  It seemed to be related to connecting to github.  Not sure why that would be though.  Can you both please share the contents of your network.cfg file?  It's off of the flash device under the config folder.

Link to post

root@:~# cat /boot/config/network.cfg

# Generated settings:
USE_DHCP="yes"
IPADDR="10.0.0.17"
NETMASK="255.255.255.0"
GATEWAY="10.0.0.128"
DHCP_KEEPRESOLV="no"
DNS_SERVER1="10.0.0.128"
DNS_SERVER2=""
DNS_SERVER3=""
BONDING="no"
BONDING_MODE="1"
BRIDGING="yes"
BRNAME="br0"
BRSTP="yes"

 

root@:~# cat /boot/config/docker.cfg

DOCKER_OPTS="--storage-driver=btrfs --dns=10.0.0.128"
DOCKER_IMAGE_FILE="/mnt/cache/AppData/Docker/docker.img"
DOCKER_IMAGE_SIZE="15"
DOCKER_ENABLED="yes"

 

 

I even stopped docker, and started docker, and the UI displays the same. The router [10.0.0.128] has static dhcp entries for the server to dish out the ip of [10.0.0.17].

 

The system most definitely has network connectivity as is evident by seeing my EggDrop bot show up on a different IRC Network.

 

And if it makes any difference, here is the template file used for one of the dockers.

 

root@:~# cat /boot/config/plugins/dockerMan/templates-user/my-NZBGet.xml

<?xml version="1.0" encoding="utf-8"?>
<Container>
  <Name>NZBGet</Name>
  <Description>NZBGet is a cross-platform binary newsgrabber for nzb files, written in C++. It supports client/server mode, automatic par-check/-repair, web-interface, command-line interface, etc. NZBGet requires low system resources and runs great on routers, NAS-devices and media players.[br][br]&#13;
[b][span style=\'color: #E80000;\']Directions:[/span][/b][br]&#13;
[b]/config[/b] : in this path NZBget will store it\'s configuration files.[br]&#13;
[b]/downloads[/b] : in this path, NZBget will store the downloaded files.[br][br]&#13;
[b]Tip:[/b] The default username is nzbget and the default password is tegbzn6789.&#13;
</Description>
  <Registry>https://registry.hub.docker.com/u/devshiny/nzbget</Registry>
  <Repository>devshiny/nzbget</Repository>
  <BindTime>true</BindTime>
  <Privileged>false</Privileged>
  <Environment/>
  <Networking>
    <Mode>bridge</Mode>
    <Publish>
      <Port>
        <HostPort>7070</HostPort>
        <ContainerPort>6789</ContainerPort>
        <Protocol>tcp</Protocol>
      </Port>
      <Port>
        <HostPort>7073</HostPort>
        <ContainerPort>6791</ContainerPort>
        <Protocol>tcp</Protocol>
      </Port>
    </Publish>
  </Networking>
  <Data>
    <Volume>
      <HostDir>/etc/resolv.conf</HostDir>
      <ContainerDir>/etc/resolv.conf</ContainerDir>
      <Mode>ro</Mode>
    </Volume>
    <Volume>
      <HostDir>/mnt/cache/AppData/NzbGet</HostDir>
      <ContainerDir>/config</ContainerDir>
      <Mode>rw</Mode>
    </Volume>
    <Volume>
      <HostDir>/mnt/cache/downloads/</HostDir>
      <ContainerDir>/downloads</ContainerDir>
      <Mode>rw</Mode>
    </Volume>
    <Volume>
      <HostDir>/etc/localtime</HostDir>
      <ContainerDir>/etc/localtime</ContainerDir>
      <Mode>ro</Mode>
    </Volume>
    <Volume>
      <HostDir>/tmp</HostDir>
      <ContainerDir>/tmp</ContainerDir>
      <Mode>rw</Mode>
    </Volume>
  </Data>
  <Version>8fee095fdca2eb77</Version>
  <WebUI>https://[iP]:[PORT:7073]/</WebUI>
  <Banner>http://i.imgur.com/KHZAlJn.png</Banner>
  <Icon>http://i.imgur.com/3zSSB3o.png</Icon>
</Container>

 

Link to post

Here's the result of clicking on update, which indicates that it was already uptodate, after the following it now displays green text of "up-to-date".

 

Preparing to update: devshiny/transmission

Pulling image: devshiny/transmission:latest

IMAGE ID [71087b6ec46f]: Pulling image (latest) from devshiny/transmission. Pulling image (latest) from devshiny/transmission, endpoint: https://registry-1.docker.io/v1/. Pulling dependent layers.
IMAGE ID [511136ea3c5a]: Download complete.
IMAGE ID [53f858aaaf03]: Download complete.
IMAGE ID [837339b91538]: Download complete.
IMAGE ID [615c102e2290]: Download complete.
IMAGE ID [b39b81afc8ca]: Download complete.
IMAGE ID [8254ff58b098]: Download complete.
IMAGE ID [ec5f59360a64]: Download complete.
IMAGE ID [2ce4ac388730]: Download complete.
IMAGE ID [2eccda511755]: Download complete.
IMAGE ID [5a14c1498ff4]: Download complete.
IMAGE ID [0798034de8b6]: Download complete.
IMAGE ID [322a6cb3569e]: Download complete.
IMAGE ID [8def5a94f193]: Download complete.
IMAGE ID [c4d03c7360a5]: Download complete.
IMAGE ID [911fe15c43c5]: Download complete.
IMAGE ID [3a405a8e3a5e]: Download complete.
IMAGE ID [8a0cf677a10d]: Download complete.
IMAGE ID [fcf7a29bbbf1]: Download complete.
IMAGE ID [70931ef84bf6]: Download complete.
IMAGE ID [e8e433486348]: Download complete.
IMAGE ID [cc65c0404ca9]: Download complete.
IMAGE ID [f97925738a63]: Download complete.
IMAGE ID [90c76aa20db8]: Download complete.
IMAGE ID [5ae5acf7a37d]: Download complete.
IMAGE ID [9a2c153686cf]: Download complete.
IMAGE ID [6b70bf6dd8c3]: Download complete.
IMAGE ID [49a80788f942]: Download complete.
IMAGE ID [9fe0c94f0968]: Download complete.
IMAGE ID [71087b6ec46f]: Download complete. Status: Image is up to date for devshiny/transmission:latest.

TOTAL DATA PULLED: 0 MB

Command:root@localhost:# /usr/bin/docker rm -f Transmission

Transmission

The command finished successfully!

Command:root@localhost:# /usr/bin/docker run -d --name="Transmission" --net="bridge" -e USERNAME="admin" -e PASSWORD="password" -e TZ="America/New_York" -p 9091:9091/tcp -p 12290:12290/tcp -v "/etc/resolv.conf":"/etc/resolv.conf":ro -v "/mnt/user/AppData/Transmission":"/config":rw -v "/mnt/cache/downloads/":"/downloads":rw -v "/etc/localtime":"/etc/localtime":ro -v "/tmp":"/tmp":rw devshiny/transmission

604988b0a4950308da1f86cd5d6d970eed9fae836cb984da1e62760e43bcdbe0

The command finished successfully!

 

And tail -f /var/log/syslog produced this at the same time.

Feb 24 17:29:21 avahi-daemon[879]: Withdrawing workstation service for veth6196983.
Feb 24 17:29:21 kernel: docker0: port 3(veth6196983) entered disabled state
Feb 24 17:29:21 kernel: device veth6196983 left promiscuous mode
Feb 24 17:29:21 kernel: docker0: port 3(veth6196983) entered disabled state
Feb 24 17:29:21 kernel: device veth9f466ee entered promiscuous mode
Feb 24 17:29:21 kernel: docker0: port 3(veth9f466ee) entered forwarding state
Feb 24 17:29:21 kernel: docker0: port 3(veth9f466ee) entered forwarding state
Feb 24 17:29:22 avahi-daemon[879]: Withdrawing workstation service for vethe2bda64.
Feb 24 17:29:22 kernel: eth0: renamed from vethe2bda64
Feb 24 17:29:36 kernel: docker0: port 3(veth9f466ee) entered forwarding state

 

TL;DR: Didn't properly detect version is up-to-date. After doing a "nothing to update" update, it detects it as being up-to-date.

Link to post

Here's the result of clicking on update, which indicates that it was already uptodate, after the following it now displays green text of "up-to-date".

 

Preparing to update: devshiny/transmission

Pulling image: devshiny/transmission:latest

IMAGE ID [71087b6ec46f]: Pulling image (latest) from devshiny/transmission. Pulling image (latest) from devshiny/transmission, endpoint: https://registry-1.docker.io/v1/. Pulling dependent layers.
IMAGE ID [511136ea3c5a]: Download complete.
IMAGE ID [53f858aaaf03]: Download complete.
IMAGE ID [837339b91538]: Download complete.
IMAGE ID [615c102e2290]: Download complete.
IMAGE ID [b39b81afc8ca]: Download complete.
IMAGE ID [8254ff58b098]: Download complete.
IMAGE ID [ec5f59360a64]: Download complete.
IMAGE ID [2ce4ac388730]: Download complete.
IMAGE ID [2eccda511755]: Download complete.
IMAGE ID [5a14c1498ff4]: Download complete.
IMAGE ID [0798034de8b6]: Download complete.
IMAGE ID [322a6cb3569e]: Download complete.
IMAGE ID [8def5a94f193]: Download complete.
IMAGE ID [c4d03c7360a5]: Download complete.
IMAGE ID [911fe15c43c5]: Download complete.
IMAGE ID [3a405a8e3a5e]: Download complete.
IMAGE ID [8a0cf677a10d]: Download complete.
IMAGE ID [fcf7a29bbbf1]: Download complete.
IMAGE ID [70931ef84bf6]: Download complete.
IMAGE ID [e8e433486348]: Download complete.
IMAGE ID [cc65c0404ca9]: Download complete.
IMAGE ID [f97925738a63]: Download complete.
IMAGE ID [90c76aa20db8]: Download complete.
IMAGE ID [5ae5acf7a37d]: Download complete.
IMAGE ID [9a2c153686cf]: Download complete.
IMAGE ID [6b70bf6dd8c3]: Download complete.
IMAGE ID [49a80788f942]: Download complete.
IMAGE ID [9fe0c94f0968]: Download complete.
IMAGE ID [71087b6ec46f]: Download complete. Status: Image is up to date for devshiny/transmission:latest.

TOTAL DATA PULLED: 0 MB

Command:root@localhost:# /usr/bin/docker rm -f Transmission

Transmission

The command finished successfully!

Command:root@localhost:# /usr/bin/docker run -d --name="Transmission" --net="bridge" -e USERNAME="admin" -e PASSWORD="password" -e TZ="America/New_York" -p 9091:9091/tcp -p 12290:12290/tcp -v "/etc/resolv.conf":"/etc/resolv.conf":ro -v "/mnt/user/AppData/Transmission":"/config":rw -v "/mnt/cache/downloads/":"/downloads":rw -v "/etc/localtime":"/etc/localtime":ro -v "/tmp":"/tmp":rw devshiny/transmission

604988b0a4950308da1f86cd5d6d970eed9fae836cb984da1e62760e43bcdbe0

The command finished successfully!

 

And tail -f /var/log/syslog produced this at the same time.

Feb 24 17:29:21 avahi-daemon[879]: Withdrawing workstation service for veth6196983.
Feb 24 17:29:21 kernel: docker0: port 3(veth6196983) entered disabled state
Feb 24 17:29:21 kernel: device veth6196983 left promiscuous mode
Feb 24 17:29:21 kernel: docker0: port 3(veth6196983) entered disabled state
Feb 24 17:29:21 kernel: device veth9f466ee entered promiscuous mode
Feb 24 17:29:21 kernel: docker0: port 3(veth9f466ee) entered forwarding state
Feb 24 17:29:21 kernel: docker0: port 3(veth9f466ee) entered forwarding state
Feb 24 17:29:22 avahi-daemon[879]: Withdrawing workstation service for vethe2bda64.
Feb 24 17:29:22 kernel: eth0: renamed from vethe2bda64
Feb 24 17:29:36 kernel: docker0: port 3(veth9f466ee) entered forwarding state

 

TL;DR: Didn't properly detect version is up-to-date. After doing a "nothing to update" update, it detects it as being up-to-date.

Ok, and since reporting "up to date" is everything working ok for you?  Was this just a weird temporary issue?

Link to post

Ok, and since reporting "up to date" is everything working ok for you?  Was this just a weird temporary issue?

 

For me, all is working as expected now.  8)

 

It must have been a very odd temporary issue, especially considering that when I re-added the docker containers the system had to be connected to the internet to be able to even pull them down.

 

Link to post

Ok, and since reporting "up to date" is everything working ok for you?  Was this just a weird temporary issue?

 

For me, all is working as expected now.  8)

 

It must have been a very odd temporary issue, especially considering that when I re-added the docker containers the system had to be connected to the internet to be able to even pull them down.

I know that with beta 13, there was a change gfjardim made to how containers updated that require a one time 0mb update like what you experienced (would have followed beta 14 as well).  Why this would reoccur for you on 14a is beyond me.

Link to post

DCwz09h.png

 

 

seeing this with one of my containers since b14a and checking for updates on the docker page.

 

no i haven't deleted this one, lol.

 

 

aShjJhG.png

 

 

see, it's def there.

 

 

BsKiKIM.png

 

 

the odd entry for update containers in the log corresponds to that image's id #

Link to post

I haven't checked my server as I'm still at work, but I had a look at a backup of my flash that is on my laptop.  I may have found my issue, in network config, DNS 1 & 2 are set to my previous ISP (never noticed) and DNS 3 is set to google DNS.  Will check/test in a few hours

Link to post

I can't update anything. Changing DNS, activating VPN, nothing makes any difference, just no templates and all packages "Not available." I am still getting the error "#012Warning: unlink(/tmp/tmp-2066361256.tar.gz): No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/dockerClient.php on line 157". I have no way to keep my docker images current now.

Link to post

Thank you. That caused my containers to show updated. I still cannot save any template repos. When I try, it flashes that same error message above "#012Warning: unlink(/tmp/tmp-2066361256.tar.gz): No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/dockerClient.php on line 157". It is trying, and failing, to download something, and so the template list can't update itself. I'm trying to use gfjardim's repo.

Link to post

Thank you. That caused my containers to show updated. I still cannot save any template repos. When I try, it flashes that same error message above "#012Warning: unlink(/tmp/tmp-2066361256.tar.gz): No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/dockerClient.php on line 157". It is trying, and failing, to download something, and so the template list can't update itself. I'm trying to use gfjardim's repo.

 

This is a different bug. Run this command from terminal and tell us if it helps:

 

wget -qO /usr/local/emhttp/plugins/dynamix.docker.manager/dockerClient.php https://raw.githubusercontent.com/limetech/dynamix/master/plugins/dynamix.docker.manager/dockerClient.php

Link to post

The command fixed the lack of templates. The error disappears. Then, when I "Check Updates", I'm right back to "Not Available" under versions, and the templates have disappeared. So, I go through the list, Edit each template and hit save, which forces an update. Then I'm back to "Up to Date" again. However, no matter how many times I run the command now, the templates will not update. The error message has remained gone. So to sum:

 

1) The command works once, and templates will update.

2) If you check updates, then the templates are erased.

3) Templates then revert to "Not Available".

4) You have to manually update them one at a time by entering Settings and clicking Save.

5) After this, the CLI command completes, but templates will not refresh.

6) The original error message remains gone.

 

There is nothing of note in the log, other than multiple lines indicating my server has become promiscuous, which I confess, makes me snicker every time. :D

Link to post

The command fixed the lack of templates. The error disappears. Then, when I "Check Updates", I'm right back to "Not Available" under versions, and the templates have disappeared. So, I go through the list, Edit each template and hit save, which forces an update. Then I'm back to "Up to Date" again. However, no matter how many times I run the command now, the templates will not update. The error message has remained gone. So to sum:

 

1) The command works once, and templates will update.

2) If you check updates, then the templates are erased.

3) Templates then revert to "Not Available".

4) You have to manually update them one at a time by entering Settings and clicking Save.

5) After this, the CLI command completes, but templates will not refresh.

6) The original error message remains gone.

 

There is nothing of note in the log, other than multiple lines indicating my server has become promiscuous, which I confess, makes me snicker every time. :D

 

Please try again with this command:

 

wget -qO /usr/local/emhttp/plugins/dynamix.docker.manager/dockerClient.php https://raw.githubusercontent.com/limetech/dynamix/docker-timeout-testing/plugins/dynamix.docker.manager/dockerClient.php

Link to post

That works. It updates the template repo and restores the templates to the list. Then, when I check updates, over several tries, it is consistently updating half of them, the rest remain "Not Available".

 

Did you try to force an update on them? Click on the container's name and hit "Add" without changing anything.

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.