vw-kombi Posted October 8, 2018 Share Posted October 8, 2018 This morning I have about 5 dockers to update. As usual, clicked update, and for each I got TOTAL DATA PULLED: 0 B, yet they showed as updated in unraid. I stopped one, deleted it, and re-installed it fine from CA. A force update from the docker tab has the same issue. Is this due to a parity check running ? This is the output from a forced update test : Pulling image: binhex/arch-lidarr:latest IMAGE ID [latest]: Pulling from binhex/arch-lidarr. Status: Image is up to date for binhex/arch-lidarr:latest TOTAL DATA PULLED: 0 B Stopping container: binhex-lidarr Successfully stopped container 'binhex-lidarr' Removing container: binhex-lidarr Successfully removed container 'binhex-lidarr' Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-lidarr' --net='bridge' -e TZ="Australia/Brisbane" -e HOST_OS="Unraid" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8686:8686/tcp' -v '/mnt/user/Downloads/':'/data':'rw' -v '/mnt/user/Data/Music/':'/media':'rw' -v '/mnt/user/appdata/binhex-lidarr':'/config':'rw' 'binhex/arch-lidarr' ce81101d1c3b03d90849fafefea94a7ef75d589f4780c4c5689759f7c3dd99fc The command finished successfully! Quote Link to comment
vw-kombi Posted October 8, 2018 Author Share Posted October 8, 2018 This problem is no longer there today. Not sure what happened to fix it. I did nothing. Quote Link to comment
Recommended Posts
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.