Skip to content
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

Rclone + Docker support? #113

Open
ne0ark opened this issue Sep 23, 2024 · 5 comments
Open

Rclone + Docker support? #113

ne0ark opened this issue Sep 23, 2024 · 5 comments

Comments

@ne0ark
Copy link

ne0ark commented Sep 23, 2024

Hello,

Is there any plan to add CLI + Rclone in a docker container that's easy to deploy?

@jdeus
Copy link

jdeus commented Nov 19, 2024

up

@sg-gs
Copy link
Member

sg-gs commented Nov 25, 2024

What do you have in mind @ne0ark? Could you extend on which would be the idea behind it?

@ne0ark
Copy link
Author

ne0ark commented Nov 25, 2024

What do you have in mind @ne0ark? Could you extend on which would be the idea behind it?

Seems like there is an issue with webdav.. I can't seems to touch files into rclone mount. I get the following error:

touch: failed to close 'test': Input/output error

@sg-gs
Copy link
Member

sg-gs commented Nov 26, 2024

So just to be sure which is the proposal and which is the issue:

As a user, I would like to have the Rclone server Dockerized so I can pull/build the image with the proper environment variables (your Internxt credentials, mainly) to have a seamless WebDav server to use Rclone utilities

Is that correct?

The main issue why you propose this feature is, that some of the file system permissions are messed up when using the WebDAV server so you can not use tools like touch to modify files.

Is that also correct? If so, could you please show how (before/after) the permissions are modified when using rclone mount? I assume the issue is on the permissions side as the Input/Output error is frequent when the user executing touch does not have permission to modify the file.

In that line, may I suggest checking if that command is by default configured to implicitly use the --read-only flag in your setup? Maybe changing that behavior could solve your issue @ne0ark

@ne0ark
Copy link
Author

ne0ark commented Nov 26, 2024

So, just to be sure which is the proposal and which is the issue:

As a user, I would like to have the Rclone server Dockerized so I can pull/build the image with the proper environment variables (your Internxt credentials, mainly) to have a seamless WebDav server to use Rclone utilities

Is that correct?

The main issue why you propose this feature is, that some of the file system permissions are messed up when using the WebDAV server so you can not use tools like touch to modify files.

Is that also correct? If so, could you please show how (before/after) the permissions are modified when using rclone mount? I assume the issue is on the permissions side as the Input/Output error is frequent when the user executing touch does not have permission to modify the file.

In that line, may I suggest checking if that command is by default configured to implicitly use the --read-only flag in your setup? Maybe changing that behavior could solve your issue @ne0ark

So just to be sure which is the proposal and which is the issue:

As a user, I would like to have the Rclone server Dockerized so I can pull/build the image with the proper environment variables (your Internxt credentials, mainly) to have a seamless WebDav server to use Rclone utilities

Is that correct?

The main issue why you propose this feature is, that some of the file system permissions are messed up when using the WebDAV server so you can not use tools like touch to modify files.

Is that also correct? If so, could you please show how (before/after) the permissions are modified when using rclone mount? I assume the issue is on the permissions side as the Input/Output error is frequent when the user executing touch does not have permission to modify the file.

In that line, may I suggest checking if that command is by default configured to implicitly use the --read-only flag in your setup? Maybe changing that behavior could solve your issue @ne0ark

I'm still getting an input/output error. My setup is CLI Docker container -> Rclone mount container -> Duplicacy (to schedule a backup). It's not set up with read-only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants