Jump to content

Didstopia

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Didstopia

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Any updates on this? Further having the ability to use more complex variables, such as http://[FQDN:IP]:[PORT:12345] would help tremendiously, especially with things like IP changes and CIDR migrations.
  2. Sorry, should've mentioned it doesn't matter which Docker registry you're using. Just replace "your.repo.com" with your registry's URL, and the Docker CLI will attempt to log in to it. If you don't specify any registry, it'll default to logging in to Docker Hub (hub.docker.com). You can also login to multiple registries.
  3. Yes, I have. In case it makes a difference, I'm dedicating a single network interface to Steamcache (eth2), which is statically set to 192.168.1.7 in unRAID's network settings, while the Docker container itself is found to 192.168.1.8.
  4. I've been trying to setup Steamcache (and now SteamCacheBundle) on unRAID for a long, long time, but I've never gotten it to work. The issue I keep seeing is that the container itself doesn't seem to have internet connectivity, no matter what upstream DNS server I use. I've tried both a dedicated NIC and IP for the container, as well as bridged. Everything should be working, but it's not. It almost seems like it's able to resolve Steam-related DNS requests, and everything else is just dropped. Anyone else seeing the same? Any advice on what to try next?
  5. Just to update on this, I just tried to do exactly this on the latest version of unRAID and got it working. First, ssh to the unRAID server as root. Next, run "docker login your.repo.com" (I also logged in to the Docker Hub, just because). Now run "cat ~/.docker/config.json", which should print out a bunch of JSON-formatted text. If it does, good, as this means it's now properly storing your Docker repository credentials for the root user. Finally, all that's left is to deploy a container from the web-interface, remembering to add your private repository url to the beginning of the image path.