public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Jonas Theisen <j.theisen@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-mamager v3 2/3] api: apt: move proxy config to pmxcfs and symlink to it
Date: Mon, 12 Oct 2026 16:45:35 +0200	[thread overview]
Message-ID: <20261012144603.288276-3-j.theisen@proxmox.com> (raw)
In-Reply-To: <20261012144603.288276-1-j.theisen@proxmox.com>

The APT proxy config was written to /etc/apt/apt.conf.d/76pveproxy
only if a database update was triggered through the PVE tooling.

Write the config to /etc/pve/apt-proxy.conf instead and replace the
local file with a symlink to it, so that changes are applied
cluster-wide.

The symlink is auto-generated on the next database update and checks
for existance of the target file before creating it.

The config is also only updated if it differs from the current
to avoid unncessarry cluster traffic.

Updateing the database without write access to /etc/pve
still works and only issues a warning.

Note that files in /etc/pve are not readable for users outside the
www-data group, so APT invoked by such users will fail to read the
proxy config.

Signed-off-by: Jonas Theisen <j.theisen@proxmox.com>
---
 PVE/API2/APT.pm | 31 ++++++++++++++++++++++++++++---
 1 file changed, 28 insertions(+), 3 deletions(-)

diff --git a/PVE/API2/APT.pm b/PVE/API2/APT.pm
index 8e16b813..2359a5f5 100644
--- a/PVE/API2/APT.pm
+++ b/PVE/API2/APT.pm
@@ -290,6 +290,24 @@ __PACKAGE__->register_method({
     },
 });
 
+my $apt_proxy_cfn = "/etc/apt/apt.conf.d/76pveproxy";
+my $pve_apt_proxy_cfn = "/etc/pve/apt-proxy.conf";
+
+my $setup_apt_proxy_symlink = sub {
+    my $target = readlink($apt_proxy_cfn);
+    return if defined($target) && $target eq $pve_apt_proxy_cfn;
+
+    my $tmpname = "$apt_proxy_cfn.tmp.$$";
+    unlink($tmpname);
+    symlink($pve_apt_proxy_cfn, $tmpname)
+        || die "unable to create symlink '$tmpname' - $!\n";
+    if (!rename($tmpname, $apt_proxy_cfn)) {
+        my $err = $!;
+        unlink($tmpname);
+        die "unable to replace '$apt_proxy_cfn' - $err\n";
+    }
+};
+
 sub update_apt_proxy_config {
     my ($dcconf) = @_;
 
@@ -299,8 +317,14 @@ sub update_apt_proxy_config {
         my $http_proxy_uri = URI->new($http_proxy);
         $aptconf = "Acquire::http::Proxy \"${http_proxy_uri}\";\n";
     }
-    my $aptcfn = "/etc/apt/apt.conf.d/76pveproxy";
-    PVE::Tools::file_set_contents($aptcfn, $aptconf);
+
+    my $current;
+    $current = PVE::Tools::file_get_contents($pve_apt_proxy_cfn) if -f $pve_apt_proxy_cfn;
+    if (!defined($current) || $current ne $aptconf) {
+        PVE::Tools::file_set_contents($pve_apt_proxy_cfn, $aptconf);
+    }
+
+    $setup_apt_proxy_symlink->();
 }
 
 __PACKAGE__->register_method({
@@ -347,7 +371,8 @@ __PACKAGE__->register_method({
         my $realcmd = sub {
             my $upid = shift;
 
-            update_apt_proxy_config($dcconf);
+            eval { update_apt_proxy_config($dcconf) };
+            warn "unable to update APT proxy config - $@" if $@;
 
             my $cmd = ['apt-get', 'update'];
 
-- 
2.47.3





  parent reply	other threads:[~2026-10-12 14:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12 14:45 [PATCH pve-mamager v3 0/3] fix #8031: Write APT proxy config on http_proxy change Jonas Theisen
2026-10-12 14:45 ` [PATCH pve-mamager v3 1/3] api: apt: factor out writing the APT proxy config Jonas Theisen
2026-10-12 14:45 ` Jonas Theisen [this message]
2026-10-12 14:45 ` [PATCH pve-mamager v3 3/3] fix #8031: api: cluster options: update APT proxy config on change Jonas Theisen
2026-10-12 14:58 ` [PATCH pve-mamager v3 0/3] fix #8031: Write APT proxy config on http_proxy change Jonas Theisen

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=20261012144603.288276-3-j.theisen@proxmox.com \
    --to=j.theisen@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal