Is there any kind of documentation to set this up with docker other than the README? #134

Closed
opened 2026-01-19 18:29:06 +00:00 by michael · 13 comments
Owner

Originally created by @driftywinds on GitHub.

The readme has very little information and I was wondering if anyone had made a guide to set this up with docker?

Originally created by @driftywinds on GitHub. The readme has very little information and I was wondering if anyone had made a guide to set this up with docker?
Author
Owner

@driftywinds commented on GitHub:

@aspacca My bad, here is the command I use to deploy the container -

sudo docker run --publish 8080:8080 dutchcoders/transfer.sh:latest --provider storj --storj-access <access token> --storj-bucket vaultwarden
@driftywinds commented on GitHub: @aspacca My bad, here is the command I use to deploy the container - ``` sudo docker run --publish 8080:8080 dutchcoders/transfer.sh:latest --provider storj --storj-access <access token> --storj-bucket vaultwarden ```
Author
Owner

@driftywinds commented on GitHub:

@driftywinds do you have any specific issue?

starting from fixing your setup we can come out with better documentation

EDIT: - Forgot to mention I am running Ubuntu 20.04, and I fixed the other issue I had that I had mentioned here. This Storj error is the only issue I still have now.

@aspacca the rclone integration fails to work for me and my bucket is not connected even though I supplied the relevant keys and IDs. The server also does not startup when I use flags to give the Stroj credentials and gives me this error: -

Untitled

@driftywinds commented on GitHub: > @driftywinds do you have any specific issue? > > starting from fixing your setup we can come out with better documentation EDIT: - Forgot to mention I am running Ubuntu 20.04, and I fixed the other issue I had that I had mentioned here. This Storj error is the only issue I still have now. @aspacca the rclone integration fails to work for me and my bucket is not connected even though I supplied the relevant keys and IDs. The server also does not startup when I use flags to give the Stroj credentials and gives me this error: - ![Untitled](https://user-images.githubusercontent.com/63164617/146138928-0d298a2d-58b5-4f06-83f8-c4f9a2be02ef.png)
Author
Owner

@driftywinds commented on GitHub:

@driftywinds this doesnàt seem related to docker

also, could please share the params you use to launch transfer.sh and please, do not attacch screenshot with output, copy the text :)

From my untrained eye it seems like it is not able to connect to Storj servers, is that it?

@driftywinds commented on GitHub: > @driftywinds this doesnàt seem related to docker > > also, could please share the params you use to launch transfer.sh and please, do not attacch screenshot with output, copy the text :) From my untrained eye it seems like it is not able to connect to Storj servers, is that it?
Author
Owner

@paolafrancesca commented on GitHub:

@driftywinds this doesnàt seem related to docker

also, could please share the params you use to launch transfer.sh and please, do not attacch screenshot with output, copy the text :)

@paolafrancesca commented on GitHub: @driftywinds this doesnàt seem related to docker also, could please share the params you use to launch transfer.sh and please, do not attacch screenshot with output, copy the text :)
Author
Owner

@paolafrancesca commented on GitHub:

@driftywinds
do you have any specific issue?

starting from fixing your setup we can come out with better documentation

@paolafrancesca commented on GitHub: @driftywinds do you have any specific issue? starting from fixing your setup we can come out with better documentation
Author
Owner

@stefanbenten commented on GitHub:

It looks like you have some sort of local DNS problem. Also why do you start it with sudo ?

@stefanbenten commented on GitHub: It looks like you have some sort of local DNS problem. Also why do you start it with `sudo` ?
Author
Owner

@stefanbenten commented on GitHub:

Ok it sounds like your user is not part of the docker group then. Its always preferred to run with as few priviliges as possible :)

This however isnt the problem here. The screenshot above clearly indicates a DNS lookup failure.

@stefanbenten commented on GitHub: Ok it sounds like your user is not part of the docker group then. Its always preferred to run with as few priviliges as possible :) This however isnt the problem here. The screenshot above clearly indicates a DNS lookup failure.
Author
Owner

@driftywinds commented on GitHub:

Ok it sounds like your user is not part of the docker group then. Its always preferred to run with as few priviliges as possible :)

This however isnt the problem here. The screenshot above clearly indicates a DNS lookup failure.

I host other things on the same VPS and they seem to connect just fine with whatever they need to, could it be a problem with StorJ servers? I'm sorry I am a novice at this so I do not know what I can do to fix it.

@driftywinds commented on GitHub: > Ok it sounds like your user is not part of the docker group then. Its always preferred to run with as few priviliges as possible :) > > This however isnt the problem here. The screenshot above clearly indicates a DNS lookup failure. I host other things on the same VPS and they seem to connect just fine with whatever they need to, could it be a problem with StorJ servers? I'm sorry I am a novice at this so I do not know what I can do to fix it.
Author
Owner

@driftywinds commented on GitHub:

It looks like you have some sort of local DNS problem. Also why do you start it with sudo ?

Oh I didn't know I was not supposed to use sudo, it has always been a constant. My VPS also gives me permission denied errors when I don't use sudo

@driftywinds commented on GitHub: > It looks like you have some sort of local DNS problem. Also why do you start it with `sudo` ? Oh I didn't know I was not supposed to use `sudo`, it has always been a constant. My VPS also gives me permission denied errors when I don't use `sudo`
Author
Owner

@stefanbenten commented on GitHub:

The Storj Servers are not the problem. Its the DNS lookup of the container that fails. I do not have the time to test the docker image myself in the next few hours, but i also doubt that the image itself is the issue.
Which VPS provider are you using?

@stefanbenten commented on GitHub: The Storj Servers are not the problem. Its the DNS lookup of the container that fails. I do not have the time to test the docker image myself in the next few hours, but i also doubt that the image itself is the issue. Which VPS provider are you using?
Author
Owner

@stefanbenten commented on GitHub:

@driftywinds Glad it works now!
Regarding the deletion token, please see https://github.com/dutchcoders/transfer.sh/issues/419

@stefanbenten commented on GitHub: @driftywinds Glad it works now! Regarding the deletion token, please see https://github.com/dutchcoders/transfer.sh/issues/419
Author
Owner

@driftywinds commented on GitHub:

The Storj Servers are not the problem. Its the DNS lookup of the container that fails. I do not have the time to test the docker image myself in the next few hours, but i also doubt that the image itself is the issue. Which VPS provider are you using?

After looking into it I found out that it was a problem with my docker version. Thank you for your help guys!
One last thing -
when I try to delete a file from the UI after uploading from the command line, what token am I supposed to give to it? Uploading from UI gives a deletion token but the command line does not

@driftywinds commented on GitHub: > The Storj Servers are not the problem. Its the DNS lookup of the container that fails. I do not have the time to test the docker image myself in the next few hours, but i also doubt that the image itself is the issue. Which VPS provider are you using? After looking into it I found out that it was a problem with my docker version. Thank you for your help guys! One last thing - when I try to delete a file from the UI after uploading from the command line, what token am I supposed to give to it? Uploading from UI gives a deletion token but the command line does not
Author
Owner

@driftywinds commented on GitHub:

Thank you!

@driftywinds commented on GitHub: Thank you!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dutchcoders/transfer.sh#134