JustinAiken Posted July 22, 2017 Share Posted July 22, 2017 (edited) If anyone else is stuck, I found a mirror... $ docker exec -it sickrage /bin/bash $ git clone https://distortion.io/git/mirror/sickrage.git /app/sickrage $ chown -R abc:abc /app /config Wait a few minutes, and the webUI will be up okay Edited July 22, 2017 by JustinAiken 2 Quote Link to comment
etsi Posted July 23, 2017 Share Posted July 23, 2017 (edited) I updated sickrage and it just deleted everything, why make an update to remove all files? It worked with the above commands but still, why someone to make a lame update to just delete the files from the docker? Edited July 23, 2017 by etsi Quote Link to comment
CHBMB Posted July 23, 2017 Share Posted July 23, 2017 Did you read any of the above?!Sent from my LG-H815 using Tapatalk Quote Link to comment
etsi Posted July 23, 2017 Share Posted July 23, 2017 On 7/21/2017 at 7:14 PM, sparklyballs said: for existing users our image is still running, for new users however it won't pull the initial files. in light of this we're beginning to move some of our repos over to having the files pulled at build time rather than runtme, we'd been thinking about it for a while but this situation was the proverbial straw for the camel's back. For existing users it also removed all existing files. Quote Link to comment
sparklyballs Posted July 23, 2017 Share Posted July 23, 2017 45 minutes ago, etsi said: For existing users it also removed all existing files. only if you deleted or updated the container i personally use medusa which is subject to the same DMCA notice and it's still working as i haven't done either of those two things Quote Link to comment
sethrd Posted July 23, 2017 Share Posted July 23, 2017 23 hours ago, JustinAiken said: If anyone else is stuck, I found a mirror... $ docker exec -it sickrage /bin/bash $ git clone https://distortion.io/git/mirror/sickrage.git /app/sickrage $ chown -R abc:abc /app /config Wait a few minutes, and the webUI will be up okay You're doing god's work, son. Quote Link to comment
nordika Posted July 24, 2017 Share Posted July 24, 2017 I made the HUGE mistake of updating the container and now I' lost ... 1) The docker is running but is it working? 2) I cannot access the webui so I can not see what is happening "behind curtains" ... Any help please? Quote Link to comment
nordika Posted July 25, 2017 Share Posted July 25, 2017 I tried that but here's what I get: " [email protected]:~# docker exec -it sickrage /bin/bash Error response from daemon: No such container: sickrage Can you please help? Thanks. Quote Link to comment
CHBMB Posted July 25, 2017 Share Posted July 25, 2017 Well what's your container called then? And is it running?Sent from my LG-H815 using Tapatalk Quote Link to comment
hernandito Posted July 25, 2017 Share Posted July 25, 2017 Stupid Captain Obvious question. In the weekly docker update, is the github check/update been disabled? Quote Link to comment
hernandito Posted July 25, 2017 Share Posted July 25, 2017 (edited) Can't this mess be resolved by adding credits to echel0n in the code? I get that he's being a douche, or a child, but what would be the reason not to do this? And what what is preventing him from incorporating code created by sickrage and medusa into his? I am using Medusa and I would hate having to revert to sickbeard. Is there a way to backup my medusa container code in case something gets corrupted? Would copying the contents of /app/medusa (or /app/sickrage) to the /config folder do the trick? Edited July 25, 2017 by hernandito Quote Link to comment
saarg Posted July 25, 2017 Share Posted July 25, 2017 16 minutes ago, hernandito said: Can't this mess be resolved by adding credits to echel0n in the code? I get that he's being a douche, or a child, but what would be the reason not to do this? And what what is preventing him from incorporating code created by sickrage and medusa into his? I am using Medusa and I would hate having to revert to sickbeard. Is there a way to backup my medusa container code in case something gets corrupted? Would copying the contents of /app/medusa (or /app/sickrage) to the /config folder do the trick? Weekly builds are disabled as far as I know. No point in crediting echel0n when he is not the owner of the code either. I think it's in the Medusa counter DMCA. Quote Link to comment
nordika Posted July 25, 2017 Share Posted July 25, 2017 Problem solved! Container name was not "sickrage" but "SickRage" instead. Thanks for all the help. Hope this is issue with DMCA get's solved soon. Quote Link to comment
mp328 Posted July 25, 2017 Share Posted July 25, 2017 On 22/07/2017 at 5:43 PM, JustinAiken said: If anyone else is stuck, I found a mirror... $ docker exec -it sickrage /bin/bash $ git clone https://distortion.io/git/mirror/sickrage.git /app/sickrage $ chown -R abc:abc /app /config Wait a few minutes, and the webUI will be up okay Tnx dude this worked... now to turn off the autoupdate settings.... Quote Link to comment
botacats Posted July 26, 2017 Share Posted July 26, 2017 9 hours ago, mp328 said: Tnx dude this worked... now to turn off the autoupdate settings.... Hi! Why this doesn't work for me ? ... It's unable to join this address : https://distortion.io/git/mirror/sickrage.git Quote Link to comment
CHBMB Posted July 26, 2017 Share Posted July 26, 2017 2 hours ago, botacats said: Hi! Why this doesn't work for me ? ... It's unable to join this address : https://distortion.io/git/mirror/sickrage.git Dunno. Not like you've posted enough details to help you. Site is still up. Quote Link to comment
botacats Posted July 26, 2017 Share Posted July 26, 2017 Sorry... what I mean is, when I do this : On 22/07/2017 at 11:43 PM, JustinAiken said: $ docker exec -it sickrage /bin/bash $ git clone https://distortion.io/git/mirror/sickrage.git /app/sickrage $ chown -R abc:abc /app /config at the second command, it tells me that it was unabled to contact the address https://distortion.io/git/mirror/sickrage.git And when I tried to access to https://distortion.io with Firefox for example, this doesn't work... Quote Link to comment
JustinAiken Posted July 26, 2017 Share Posted July 26, 2017 3 hours ago, botacats said: at the second command, it tells me that it was unabled to contact the address https://distortion.io/git/mirror/sickrage.git And when I tried to access to https://distortion.io with Firefox for example, this doesn't work... Small server goes down alot... but the sickrage devs set up their own mirror at https://donna.devices.wvvw.me/sickrage/sickrage.git - try that instead. Quote Link to comment
Helmonder Posted July 30, 2017 Share Posted July 30, 2017 This worked ! Lifesavers !! Quote Link to comment
Hennie Posted August 3, 2017 Share Posted August 3, 2017 On 7/22/2017 at 11:43 PM, JustinAiken said: If anyone else is stuck, I found a mirror... $ docker exec -it sickrage /bin/bash $ git clone https://distortion.io/git/mirror/sickrage.git /app/sickrage $ chown -R abc:abc /app /config Wait a few minutes, and the webUI will be up okay Thanks! That helped a lot for a new user like me! It seems to work but I do get random errors like " IOError: [Errno 2] No such file or directory: u'/config/cache/mako/home.mako.py' is the chown command literal or should i replace abc:abc with something else? And how do I find out with what? Quote Link to comment
Hennie Posted August 3, 2017 Share Posted August 3, 2017 4 minutes ago, CHBMB said: Are you using Unraid? Yes I am. Bare metal. Version 6.3.5 Quote Link to comment
CHBMB Posted August 3, 2017 Share Posted August 3, 2017 If it's working fine I'd ignore it. Looks like a Windows path which is why I asked. The chown command is correct. Quote Link to comment
sparklyballs Posted August 5, 2017 Share Posted August 5, 2017 The DMCA notice has been lifted so you don't need to resort to dodgy "fixes" anymore we're also going to move the git pull internal to the image instead of at runtime. 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.