You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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...
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?
The text was updated successfully, but these errors were encountered: