From: Folke Gleumes <f.gleumes@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH container v3] pct: add keep-env option
Date: Fri, 9 Feb 2024 14:17:09 +0100 [thread overview]
Message-ID: <20240209131709.491145-1-f.gleumes@proxmox.com> (raw)
In-Reply-To: <9e65cabe-9251-4b3c-b8ad-c761df5cca0a@proxmox.com>
The keep-env option allows the user to define if the current environment
should be kept when running 'pct enter/exec'. pct will now always set
'--keep-env' or '--clear-env' when calling lxc-attach to anticipate
the upcoming change in default behavior.
Signed-off-by: Folke Gleumes <f.gleumes@proxmox.com>
---
changes in v3:
* fix code style nits
changes in v2:
* add this patch
src/PVE/CLI/pct.pm | 29 +++++++++++++++++++++++++++--
1 file changed, 27 insertions(+), 2 deletions(-)
diff --git a/src/PVE/CLI/pct.pm b/src/PVE/CLI/pct.pm
index 091ac8e..325178f 100755
--- a/src/PVE/CLI/pct.pm
+++ b/src/PVE/CLI/pct.pm
@@ -162,12 +162,22 @@ __PACKAGE__->register_method ({
additionalProperties => 0,
properties => {
vmid => get_standard_option('pve-vmid', { completion => \&PVE::LXC::complete_ctid_running }),
+ # FIXME: passing the environment into the container potentially leaks hosts secrets, or causes
+ # unexpected behavior. Change to opt-in for pve 9
+ 'keep-env' => {
+ type => 'boolean',
+ description => "Keep the current environment. This option will disabled by default with PVE 9."
+ ." If you rely on a preserved environment, please use this option to be future-proof.",
+ optional => 1,
+ default => 1,
+ },
},
},
returns => { type => 'null' },
code => sub {
my ($param) = @_;
+ my $keep_env = $param->{'keep-env'} // 1; # FIXME: switch to default 0 with pve 9, see above
my $vmid = $param->{vmid};
@@ -175,7 +185,10 @@ __PACKAGE__->register_method ({
die "container '$vmid' not running!\n" if !PVE::LXC::check_running($vmid);
clean_environment();
- exec('lxc-attach', '-n', $vmid);
+
+ my @lxc_attach_cmd = ('lxc-attach', '-n', $vmid);
+ push @lxc_attach_cmd, $keep_env ? '--keep-env' : '--clear-env';
+ exec(@lxc_attach_cmd);
}});
__PACKAGE__->register_method ({
@@ -187,12 +200,20 @@ __PACKAGE__->register_method ({
additionalProperties => 0,
properties => {
vmid => get_standard_option('pve-vmid', { completion => \&PVE::LXC::complete_ctid_running }),
+ 'keep-env' => {
+ type => 'boolean',
+ description => "Keep the current environment. This option will disabled by default with PVE 9."
+ ." If you rely on a preserved environment, please use this option to be future-proof.",
+ optional => 1,
+ default => 1, # FIXME: switch to default 0 with pve 9, see enter method
+ },
'extra-args' => get_standard_option('extra-args'),
},
},
returns => { type => 'null' },
code => sub {
my ($param) = @_;
+ my $keep_env = $param->{'keep-env'} // 1; # FIXME: switch to default 0 with pve 9, see enter method
my $vmid = $param->{vmid};
PVE::LXC::Config->load_config($vmid); # test if container exists on this node
@@ -201,7 +222,11 @@ __PACKAGE__->register_method ({
die "missing command" if !@{$param->{'extra-args'}};
clean_environment();
- exec('lxc-attach', '-n', $vmid, '--', @{$param->{'extra-args'}});
+
+ my @lxc_attach_cmd = ('lxc-attach', '-n', $vmid);
+ push @lxc_attach_cmd, $keep_env ? '--keep-env' : '--clear-env';
+ push @lxc_attach_cmd, '--', @{$param->{'extra-args'}};
+ exec(@lxc_attach_cmd);
}});
__PACKAGE__->register_method ({
--
2.39.2
next prev parent reply other threads:[~2024-02-09 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 15:43 [pve-devel] [PATCH container v2 1/2] fix #5194: pct: delete environment variables set by pve Folke Gleumes
2024-01-29 15:43 ` [pve-devel] [PATCH container v2 2/2] pct: add keep-env option Folke Gleumes
2024-02-02 16:53 ` Thomas Lamprecht
2024-02-09 13:17 ` Folke Gleumes [this message]
2024-02-09 19:07 ` [pve-devel] applied: " Thomas Lamprecht
2024-02-02 16:32 ` [pve-devel] applied: [PATCH container v2 1/2] fix #5194: pct: delete environment variables set by pve Thomas Lamprecht
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=20240209131709.491145-1-f.gleumes@proxmox.com \
--to=f.gleumes@proxmox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox