Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About generalz

  • Rank
    Advanced Member


  • Gender
  1. doh the headphones docker broke. After this operation, 22.5 MB of additional disk space will be used. Err http://archive.ubuntu.com/ubuntu/ trusty-updates/main patch amd64 2.7.1-4ubuntu2 404 Not Found [iP: 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/p/patch/patch_2.7.1-4ubuntu2_amd64.deb 404 Not Found [iP: 80] looks like they changed the dir structure on archive
  2. generalz

    New Feature Coming in Beta 15: VM Manager

    do you think we can get a good plugin to go with this for adding drives out of the array for vm storage
  3. has anyone added ffmpeg or lame to the headphones?
  4. generalz

    [DOCKER] ownCloud is here!

    Mine went without issue. What do the logs say?
  5. generalz

    [DOCKER] ownCloud is here!

    whenever you have to update again, can you disable ssl3?
  6. generalz

    [DOCKER] ownCloud is here!

    Does anyone have tips for hosting/uploading files more then 2gigs. mine seems to choke on files bigger then a gig.
  7. generalz

    [CONTAINER] CrashPlan & CrashPlan-Desktop

    nice, now thats some service
  8. generalz

    [CONTAINER] CrashPlan & CrashPlan-Desktop

    correct. freenas guys are having the same problem with the bsd jail (similar to docker) I haven't looked into it. its worse when the program has an internal database for settings or usage because then you get into a situation where the db is newer then the program.
  9. generalz

    [CONTAINER] CrashPlan & CrashPlan-Desktop

    well for one the changes are not saved when you stop and start the container again and it goes through the update process again. the java updates stop the services and since the containers dont start services like a normal *nix box it breaks.
  10. generalz

    [CONTAINER] CrashPlan & CrashPlan-Desktop

    Crashplan is pushing java updates out. will probably break this container in the next few days if it hasn't already.
  11. generalz

    [CONTAINER] CrashPlan & CrashPlan-Desktop

    this is working as intended per crashplans instructions. if you want to use the UI without ssh you need to modifiy my.service.xml in your appdata\crashplan\conf change it from to <serviceUIConfig> <serviceHost></serviceHost> <servicePort>4243</servicePort> <connectCheck>0</connectCheck>
  12. generalz

    [CONTAINER] CrashPlan & CrashPlan-Desktop

    you need to create a crashplan share without cache drive usage and map that in the container setup. then change the default destination on the crashplan server to go to that share for incoming backups
  13. set it back to default, that fixed it! thanks!
  14. oooh i might have changed them. Looks like they are all set to no
  15. those are all dockers I guess they are not excluded from starting up.