Closed diegolagoglez closed 8 years ago
Yeah, it's unfortunate that the golang error is so cryptic about it...
Yes… Maybe we should add an issue indicating that errors about TLS/SSL issues are so cryptic, specially when it is using a proxy.
That would be an upstream golang issue though. LXD reports all it gets from golang so it doesn't have much more of a clue than you do :)
@diegolagoglez The solution you provide
lxc config set core.http_proxy <proxy server>
results in
error: Bad server config key: 'core.http_proxy'
On https://stgraber.org/2016/03/15/lxd-2-0-installing-and-configuring-lxd-212/, @stgraber has the keys as:
lxc config set core.proxy_http http://squid01.internal:3128
lxc config set core.proxy_https http://squid01.internal:3128
lxc config set core.proxy_ignore_hosts image-server.local
If Stéphane is correct, could you fix the solution you provide above? I am using lxc v2.0.11.
[SOLVED]
The problem was that the proxy server was set into the client side (
lxc
), but it must be set into the server side (lxd
) usinglxc config
command:I've installed lxc/lxd trought its official PPA (
ppa:ubuntu-lxc/lxd-stable
) and I have version 2.0.0.rc6 in a Ubuntu MATE 15.10 (amd64). When I try to download an image (with commandsudo -E lxc launch images:centos/6/amd64 my-centos
) I always get the same error:Full debug output of the command is:
I am behind a proxy server that works well with https addresses but, when I try to download any image, previous error is always shown. I also tested it on a Ubuntu MATE 15.10 (i386) without a proxy and it works perfectly.
Proxy server is configured through the UI (globally) but I also have
http_proxy/https_proxy
shell variables exported.The rest of the commands (like
lxc image list images:
) work well.lxc info
/var/log/lxd/lxd.log: