search

internxt / cli

30 stars 6 forks source link

Rclone + Docker support? #113

Open ne0ark opened 2 months ago

ne0ark commented 2 months ago

Hello,

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

jdeus commented 1 week ago

up

sg-gs commented 1 day ago

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

ne0ark commented 1 day ago

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 commented 16 hours ago

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 commented 11 hours ago

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.