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

Bugfix: allow backing up of read-only mount /data #39

Merged
merged 1 commit into from Dec 4, 2021

Conversation

Myridium
Copy link
Contributor

@Myridium Myridium commented Dec 4, 2021

This commit allows the user to backup mounts at /data which are mounted
as read-only. There is a slight break to previous behaviour which may
affect some users: symlinks inside /data which point to absolute paths
used to be followed, and their contents included in the backup. This
is no longer the case.

@Myridium
Copy link
Contributor Author

Myridium commented Dec 4, 2021

Clarification: symlinks directly inside /data at the top level.

@Myridium
Copy link
Contributor Author

Myridium commented Dec 4, 2021

Sorry, there is a bug currently. Please allow me to fix this and I will let you know.

@Myridium Myridium force-pushed the ro_patch branch 7 times, most recently from 059564d to 8ebc8a7 Compare December 4, 2021 10:49
This commit allows the user to backup mounts at /data which are mounted
as read-only. There is a slight break to previous behaviour which may
affect some users: symlinks inside /data which point to absolute paths
*used* to be followed, and their contents included in the backup. This
is no longer the case.
@Myridium
Copy link
Contributor Author

Myridium commented Dec 4, 2021

Okay, I've tested it a bit with my data and it seems to be working okay now.

@christophetd christophetd merged commit 53cbc2b into christophetd:master Dec 4, 2021
@christophetd
Copy link
Owner

Thanks! Merged and released as v1.6.0

@Myridium
Copy link
Contributor Author

Myridium commented Dec 5, 2021

Thanks for making the docker container, and for merging. Looks like I can switch over to Duplicacy now :)

@Myridium
Copy link
Contributor Author

@christophetd hi, the pipeline seems to have failed and this hasn't been uploaded to Docker Hub. It looks like the pipeline is just upset that the .duplicacy folder isn't created, but this is intended behaviour now.

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

Successfully merging this pull request may close these issues.

None yet

2 participants