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

lxc-copy documentation #4406

Open
curable-online opened this issue Mar 3, 2024 · 1 comment
Open

lxc-copy documentation #4406

curable-online opened this issue Mar 3, 2024 · 1 comment
Milestone

Comments

@curable-online
Copy link

Required information

  • Distribution: Arch
  • Distribution version: Current
  • The output of
    • lxc-* --version: 5.0.3

Issue description

As far as I understand from the Manpages, lxc-copy can create
two types of copies: 1. Regular complete copies, 2. Snapshots.

Nevertheless, it is unclear which method of copy it uses for each
type of backing storage, particularly with and without -s and -e flags.

Sounds like the manpage implicitly implies that it does the first type of copy by
default unless -s or -e flags are specified, regardless of the
backing storage type, and will create snapshots otherwise. Is that true?

That would be desireful if it explicitly explains that which type of copy it does for each type of backing storage, by default and also with -s flag. Specially since lxc does not a good job at providing reports by default.

@stgraber stgraber added this to the lxc-6.0.0 milestone Mar 26, 2024
@mihalicyn
Copy link
Member

Hi @curable-online !

First of all, documentation says that:

When the -e flag is specified an ephemeral
snapshot of the original container is created and started.

Thus, -e implies -s.

Sounds like the manpage implicitly implies that it does the first type of copy by
default unless -s or -e flags are specified,

yes, by default a full copy is created.

I agree in general, that it's easy to get lost in this different options. But it would be awesome if you suggest a PR with the documentation changes after clarifications from our side.

What specifically do you think we need to change in the current documentation wordings?

@stgraber stgraber modified the milestones: lxc-6.0, lxc-6.1 Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants