• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About jkm9000

  • Rank


  • Gender
  1. Came here to ask the same thing.
  2. Reading that, all I could think of is Homer saying "That's how I was raised and I turned out TV." That's a whole lot of TV you've got going there!
  3. You beat me to it, but I was just going to say that something like this seems like it would make sense for a 6.x release (where x >= 1). I gave up on AFP ages ago with unRAID, but I do have a dedicated TimeCapsule so it isn't too critical. I would love to see it improved, but not at the expense of what has already been outlined for a Q3 release. Surely that's reasonable.
  4. That should handle any other lurking edge cases from the CLI output and be a lot more stable moving forward.
  5. Thanks for this One cosmetic issue. I have a custom plex Dockerfile which gets started like so: docker run -d \ --name="plex" \ -v /etc/localtime:/etc/localtime:ro \ -v /mnt/cache/appdata/plex:/config \ -v /mnt/user:/data \ -p 1900:1900/udp \ -p 15353:5353/udp \ -p 32400:32400 \ -p 32410:32410/udp \ -p 32412:32412/udp \ -p 32413:32413/udp \ -p 32414:32414/udp \ -p 32469:32469 \ plex Under the name column I get this: 0:15353->5353/udp,>32400/tcp,>32410/udp,>32412/ud
  6. Gotcha. You could always have other users drop their public key in the build directory. If it's there use it. If not, it just would not enable ssh.
  7. You only need to build the container once though. The real advantage here is that you're using a unique key instead of a public (insecure) one. Or maybe I'm missing something?
  8. boot2docker is great when you are using an OS without support for Linux containers. Since unRAID's kernel has support for this, it's an extra layer that isn't needed.
  9. I think their points apply more to the enterprise than the home user. I'm certainly not going to setup one container for an app itself, another to edit the config of that app, another to view the logs, and another to be able to restart the app. That seems like a lot of complexity for a home media server. For a situation with lots of developers, that approach makes much more sense. I don't think there is one "best way" to use docker because the ways it can be used vary so much.
  10. You can pass along your own public key as outlined here https://github.com/phusion/baseimage-docker#using-your-own-key nsenter might be another option https://github.com/jpetazzo/nsenter
  11. Good points. Valid. To quote the phusion README: "By the time that you've gotten all that right, you've reinvented baseimage-docker. Using baseimage-docker will save you from this effort."
  12. It's worth noting that phusion isn't some random guy, it's the company behind Passenger among other things. As far as distros go, it's great you want to run with the one's you've mentioned. I'm going in a different direction though.