-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please update your installation documentation #89
Comments
Can you provide the exact Docker run command you entered? |
I realized after starting this thread that the code format was not copy-paste ready and I had to remove all of the dashes (\). I'm sure this has thrown off many users who are not used to programming, so I recommend to the author to provide the code without those breaks, or at least to instruct users to remove them. And second, when I re-run the code, I get an error saying the config is incomplete. Here's the output:
And from what I've read, the docker-machine ip command is obsolete. |
It looks like you're missing a \ in your config mapping unless "xxx files" is correct? I'm wondering if the spaces may be causing issues. If I recall, Linux systems don't like spaces in file names or directories. Edit: I did a quick search and you're not alone. There are a number of threads about mapping volumes with spaces and people having problems. I bet if you simplify the path structure it'll work. |
No, the directories are specified correctly; I just replaced my name with 'xxx'. If you have spaces without quotes, such as C:\docker config:/config instead of "C:\docker config":/config, it will of course not run any of the code, but as I posted earlier, it does run the code, only it says the configuration is incomplete. I can also confirm that docker will create your specified directories if they don't exist already-- or at the very least the config directory. Here are the contents of the configuration file that is created:
Perhaps someone can point out what's missing. Then, there's the issue with finding the IP, as "docker-machine ip" is obsolete. I tried inspecting the entire contents of the container settings and there was no IP there. |
Ok, have your pulled up seedsync yet? Can you? To me it looks like the config just needs your seedbox details. |
Yeah, I finally got it to work. All I had to do is go to localhost:8800 and fill out the seedbox details. It's unfortunate that the instructions don't make that clear. They imply that you need to first find the docker/container ip. I would suggest to the author to please clean up the instructions, because if I wasted hours trying to figure out what's wrong, I'm sure that there are plenty of far less experienced users who wouldn't have gotten this far. And, what's worse, for me, is that this application does not do what I thought it would. 😩 Somebody on Reddit suggested it for transferring files between two seedboxes (can't find the link anymore), whereas this is clearly remote-->local transfers only. I use FileZilla for that and get the same speeds. Anyways, thanks for your help @quadcom. |
Hi,
I installed Docker for Windows, confirmed that it's running, and ran your code from this page: https://ipsingh06.github.io/seedsync/install/
But it appears that the code is either incorrect or obsolete. Can you please double check and update?
I get unrecognized command errors in CMD when I type this:
docker run \ -p 8800:8800 \ -v <downloads directory>:/downloads \ -v <config directory>:/config \ ipsingh06/seedsync
(Note: the directories were specified)
And this:
docker-machine ip
thanks
The text was updated successfully, but these errors were encountered: