d. could be a firewall issue between container and host? do you
<wallyworld_> have any suggestion?
<jam> wallyworld_: so you put an http server on your host machine, and then are unable to access 10.0.3.1:PORT from lxc, is that correct?
<jam> wallyworld_: did you start your HTTP server before starting LXC?
<jam> Is it binding to "*" (0.0.0.0) or is it binding to 127.* or to an explicit IP address?
<wallyworld_> jam: yes, but can access localhost:PORT from host
<jam> wallyworld_: from the *host* can you access 10.0.3.1:PORT
<wallyworld_> yes
<wallyworld_> from my PC
<wallyworld_> oh
<wallyworld_> sec, let me check
<jam> wallyworld_: my first thought is that your service isn't bound to all networks
<wallyworld_> jam: yeah, can't connect to 10.0.3.1 from host. i was just trying to validate the replacing localhost with the bridge address actualy worked
<wallyworld_> maybe there's no need to do that
<jam> wallyworld_: so are you just doing something like python SimpleHTTPServer ?
<wallyworld_> the http proxy, apt proxy etc are all set to <bridge addr> as required
<jam> Are you handing it an address to bind to ?
<jam> Rather than "0.0.0.0" ?
<jam> wallyworld_: it might certainly be a real life issue, as having your HTTP proxy set up may not bind it to the LXC bridge address if it comes up first.
<wallyworld_> jam: ah, i see the issue, the little go prog is binding to localhost
<wallyworld_> http.ListenAndServe("localhost:8000", nil)
<jam> wallyworld_: right, I think you can change that to ":8000' or maybe "0.0.0.0:8000"
<wallyworld_> jam: i assumed that would cover all connections into the physical host
<jam> wallyworld_: nope, specifying localhost restricts it to 127.* as it is how you avoid making something publi
<wallyworld_> oh, i'll try that, ty :-)
<wallyworld_> jam: you are awesome, that worked, ty
<jam> wallyworld_: np
<menn0> davecheney: looking now
<menn0> davecheney: done
<stokachu> anyone notice when doing a juju bootstrap with a maas provider that when it runs its apt-get update/upgrade it returns a non ze