Simon McVittie <s...@debian.org> writes: > I think these are the key facts here. > > Your apt proxy on the host system is probably set to http://127.0.0.1:3142? > > The bug is that a-b-podman auto-detects this, and tries to use the same > proxy inside the container; but the host system's 127.0.0.1 will not be > reachable from inside the container, so it tries to translate it to an > IP address at which the host will be reachable.
Yes, that's the setting on all of my hosts with acng. > Probably the only solution to this is for a-b-podman to refuse to use an > auto-detected proxy if it's 127.0.0.1 (behave as if DIRECT), and instead > log a warning that recommends using the --apt-proxy option. That makes sense to me.
