Okay, I realized that `no_proxy="" sudo ...` does not overwrite no_proxy because it gets loaded again from /etc/environment when switching to the su context. If I do `sudo su` and then call `no_proxy="" apt update` then indeed the proxy is no longer by-passed.
> 3) configure Acquire::http::proxy (or http_proxy) and set no_proxy in /etc/environment(.d) This is exactly what I did and it leads to the described inconsistent behavior. Apparently, /etc/environment is not read when apt.daily runs. This means, no_proxy is *not* defined when apt runs as a service - but it *is* defined when running apt from the terminal. So effectively, apt does "suddenly pick different proxies when running as a service". Note that this is not a support request as I did not ask for help or pose any questions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055717 Title: Acquire::http::proxy ignored / used inconsistently? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2055717/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
