From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Orwa Diraneyya <info@orwa.tech>
Subject: Re: [pve-devel] [PATCH container] Fix bug #6040 in the exclusion pattern of tar
Date: Thu, 13 Feb 2025 11:15:33 +0100 (CET) [thread overview]
Message-ID: <83426160.6545.1739441733078@webmail.proxmox.com> (raw)
In-Reply-To: <mailman.80.1736016466.441.pve-devel@lists.proxmox.com>
> Orwa Diraneyya via pve-devel <pve-devel@lists.proxmox.com> hat am 04.01.2025 19:47 CET geschrieben:
> From: Orwa Diraneyya <diraneyyaorwa@gmail.com>
>
> After this fix, users of Proxmox will be able to
> use the root filesystem tarballs found publicly
> (e.g. at https://cloud-images.ubuntu.com/) as LXC
> container templates.
>
> Currently, this results in a container-creation
> failure due to the root folder `/dev` exclusion
> pattern being ineffective.
>
> The bugfix is also announced on the dev mailing
> list (mailman.74.1735960093.441.pve-devel)
>
> Signed-off-by: Orwa Diraneyya <diraneyyaorwa@gmail.com>
> ---
> src/PVE/LXC/Create.pm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/PVE/LXC/Create.pm b/src/PVE/LXC/Create.pm
> index 8c8cb9a..4d0d11e 100644
> --- a/src/PVE/LXC/Create.pm
> +++ b/src/PVE/LXC/Create.pm
> @@ -75,7 +75,7 @@ my sub restore_tar_archive_command {
> # *sigh*, gnu...
> push @$cmd, '--skip-old-files';
> push @$cmd, '--anchored';
> - push @$cmd, '--exclude' , './dev/*';
> + push @$cmd, '--exclude' , 'dev/*';
Thanks for your patch!
Unfortunately, this is not the correct way to tackle this - because of `--anchored`, `./dev/*` and `dev/*` match different things:
$ mkdir dev; touch dev/test
$ ls dev
test
$ tar cf test.tar ./dev
$ tar tf test.tar
./dev/
./dev/test
$ rm -rf extract; mkdir extract
$ tar -xf test.tar -C extract --anchored --exclude './dev/*' -v
./dev/
$ rm -rf extract; mkdir extract
$ tar -xf test.tar -C extract --anchored --exclude 'dev/*' -v
./dev/
./dev/test
Note how the tarball contains a relative dir ./dev with a file test inside (like our/most container templates), and how extracting it with the original exclusion pattern just extracts the empty dev dir, skipping its contents, while your proposed pattern extracts the contents as well.
The inverse is true for your tarball with the contents the other way round:
$ rm test.tar
$ tar cf test.tar dev
$ tar tf test.tar
dev/
dev/test
$ rm -rf extract; mkdir extract
$ tar -xf test.tar -C extract --anchored --exclude './dev/*' -v
dev/
dev/test
$ rm -rf extract; mkdir extract
$ tar -xf test.tar -C extract --anchored --exclude 'dev/*' -v
dev/
So what we actually want if we want to support both variants is to exclude *both* patterns.
Note that your original use case of just passing an image not intended for container consumption might still fail for other reasons ;) But such a patch would at least allow manually created templates that don't use the ./ prefix to work properly.
> if (defined($bwlimit)) {
> $cmd = [ ['cstream', '-t', $bwlimit*1024], $cmd ];
> --
> 2.46.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-02-13 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 18:47 Orwa Diraneyya via pve-devel
2025-02-13 10:15 ` Fabian Grünbichler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83426160.6545.1739441733078@webmail.proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=info@orwa.tech \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.