Jump to content

kylemart

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About kylemart

  • Rank
    Newbie
  1. Hmm, that's a fair point. I guess it's more of a feature request than a bug then, especially if the intended use-case is for docker hub to be used. I've noticed that, upon reboot, the /etc/docker/daemon.json file I created (via the command line) to allow insecure connections to my private repository disappeared. Seems as though my intended setup, in its current form, is even less compatible with unRaid than I originally surmised. I guess should private repositories become a supported feature, it would be nice if this configuration option (insecure repositories) were made configurable via the WebGUI and stuck after reboots. That's in addition, of course, to updating the implementation of the "update available" indicator to support private repositories. All-in-all, def exceeds the scope of a bug fix. But anyway, thanks for the insight Squid! In the meantime I think I'll stick with public docker hub repositories. I'm not too worried if the images I'm creating for my NAS are public -- there's nothing sensitive or proprietary in them Cheers!
  2. If this is unexpected behavior I can file a proper bug report through the Unraid WebGUI. Just let me know
  3. Ooh, wasn't aware of that option. Yeah, forced updates work. Although it claims things are up to date (after clicking "Check for Updates"): Running a forced update indicates otherwise:
  4. Hey everyone, I recently set up a private, insecure docker registry to store docker images used by my NAS. The idea being, I can work on private automation-related programs on my home dev box, build docker images for them, deploy the docker images to my private docker registry, and have Unraid detect the updates with a click of the "Check for Updates" button in the WebGUI. There's a slight problem I'm running into, however. I'm able to deploy the images to my private registry, and I'm able to pull down the images and run them as containers on my NAS, but Unraid won't detect available updates. The only way to get the update onto my NAS is to either: a) edit the container's configuration in the WebGUI so that it re-pulls the image and restarts or b) delete the container / image and create a new one. Since this isn't an issue with images hosted in docker hub, I'm currently just deploying my images into public repositories -- which works fine. That said, this isn't the ideal setup that I'm looking for... Anyone know how I can get Unraid to properly detect that new versions are available in my private registry? Thanks!
  5. I think the title pretty much explains what happened. Silly me accidentally set the backup location for the USB to '/boot' and the backup location for the libvirt.img file to '/mnt/user/system/libvirt'. I can't imagine the CA Backup plugin doing more than copying / rsync-ing the files, but just to be sure, are there any negative side-effects to doing what I did? I've since changed the directories by the way.