-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
[bitnami/rclone] cannot create temp config file from environment variables #78979
Comments
Hi! Thank you so much for reporting. As a workaround, could you try setting the env var |
Hi yes, forcing To be fair this seems an I don't really understand why they are logging that as an error since it should be at most a warning. I don't really know if this should be considered an image issue. |
FYI also works by setting |
Hi, Thanks for letting us know. Maybe it's worth mentioning this to the rclone devs? |
Yes I already did that |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Name and Version
bitnami/rclone:1.69.1
What architecture are you using?
amd64
What steps will reproduce the bug?
rclone.conf
files, add your rclone configs as environment variables likeRCLONE_CONFIG_<SOURCENAME>_URL
sync
orcopy
rclone command between a source and another destinationWhat is the expected behavior?
The expected behaviour is simply to execute the
copy
orsync
command correctly.What do you see instead?
Additional information
I think that the main issue is that rclone tries to create a temp config file in the user's home directory.
In
bitnami/rclone
, the user uid is 1001, without username where the home directory is/
so rclone tries to write the config temp file in/
.I've tried following rclone docs, setting the
RCLONE_CONFIG_DIR
, settingXDG_CONFIG_HOME
but nothing worked. It seems that rclone tries to write the temp file still in/
and then moving it to its config directory.See https://rclone.org/docs/#config-config-file
This issue does not occur with
rclone/rclone:1.69.1
, since its user is root.The text was updated successfully, but these errors were encountered: