lxc-create doesn't take advantage of the apt proxy

Thanks for reporting this bug.

You can work around this by editing /etc/default/lxc and setting

MIRROR="http://10.0.3.1:3142/archive.ubuntu.com/ubuntu"

(That is assuming you are using the default lxcbr0.)

That's good enough for me, feel free to close the ticket.

I think we could better integrate the host apt proxy data into the template. Ideally the user shouldn't have to make customizations to lxc when the host already knows how to use the proxy. There is a question of whether the host proxy will be valid in the guest (i.e. if using 'http://localhost:3142/', then if we mirror that into the guest then updates will fail in the container although initial container setup will succeed).

I'll leave this open with wishlist priority with the hope we can get better integration.

So to do this properly, do I understand right that we would simply grep for Acquire::http::Proxy in /etc/apt/apt.conf and /etc/apt/apt.conf.d/*?

Assuming /etc/default/lxc is sourced, how about integrating this directly in it:

  # Is there a local apt-proxy/cacher available ?
  eval $(apt-config shell MIRROR Acquire::http::Proxy)

Quoting Simon Déziel (<email address hidden>):
> Assuming /etc/default/lxc is sourced, how about integrating this
> directly in it:
>
> # Is there a local apt-proxy/cacher available ?
> eval $(apt-config shell MIRROR Acquire::http::Proxy)

Thanks, that sounds like a neat trick :)

Fix committed in upstream git.

This bug was fixed in the package lxc - 1.0.0~alpha1-0ubuntu2

---------------
lxc (1.0.0~alpha1-0ubuntu2) saucy; urgency=low

  * Add allow-stderr to autopkgtst restrictions as the Ubuntu template
    uses policy-rc.d to disable some daemons and that causes a message to
    be printed on stderr when the service tries to start.
 -- Stephane Graber <email address hidden> Thu, 12 Sep 2013 13:57:17 -0400