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

Why not replace the container instead of making a clone? #4

Open
ebertland opened this issue Nov 12, 2024 · 2 comments
Open

Why not replace the container instead of making a clone? #4

ebertland opened this issue Nov 12, 2024 · 2 comments

Comments

@ebertland
Copy link

The way I used this very helpful script is to replace a container that I had originally made unprivileged with a privileged one. In some of the tutorials I found for doing this before finding this script, they recommended destroying the original container in between backup and restore.

What's the reason for keeping the original container? Are you open to a PR that allows the user to choose between replacing and cloning?

@onethree7
Copy link
Owner

Hello,
thanks as well for this suggestion. This one will not come though.

The reasoning behind that is, that an automatic "replacement" could introduce a single point of failure which could actually bring a form of Data Unavailability or even Data Loss into the equasion. We can never anticipate what a user has configured in a way that will break on conversion...

@ebertland
Copy link
Author

Oh, I see. The restore might fail, but the original was already deleted.

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

2 participants