Same error setting https_proxy as well as http_proxy.
user@box ~ $ sudo -E lxc launch images:centos/6/amd64 my-centos
Creating my-centos
error: Get https://images.linuxcontainers.org/1.0/images/centos/6/amd64: remote
error: handshake failure
Note: now using lxc 2.0.0.rc6 after last update.
--
You've had some success with live migrations? At any rate, I'm upgrading my
ubuntu 15.10 test box to 16.04 so that I'll have 2 of them. I'll give it a
whirl.
On Sun, Mar 27, 2016 at 9:20 PM, Fajar A. Nugraha wrote:
> On Sun, Mar 27, 2016 at 11:31 PM, jjs - mainphrame
> wrote:
> > The 2nd link y
On Sun, Mar 27, 2016 at 11:31 PM, jjs - mainphrame wrote:
> The 2nd link you sent seems to indicate that
> live migration wants to work, but I haven't been able to find any reports
> from normal users in the field who've actually succeeded with live
> migration. if I've missed something, please le
I was able to find the following in a past lxc-users post:
lxc config device add qt5-development /dev/nvidia0 unix-char
path=/dev/nvidia0
lxc config device add qt5-development /dev/nvidiactl unix-char
path=/dev/nvidiactl
lxc config device add qt5-development /dev/nvidia-uvm unix-char
path=
Thanks for the feedback - I'm glad to see that zfs on ubuntu is a go,
despite the legal naysayers. I've been testing lxc and lxd containers on
ubuntu 16.04 running straight ext4, but I'll redo the partitioning, and/or
add disks, to provide some dedicated zfs storage.
As soon as I can scrounge a su
On Sun, Mar 27, 2016 at 8:11 AM, jjs - mainphrame wrote:
> As a long time fan of openvz, I'm impressed with how far lxc has come in the
> past couple of years, and particularly impressed with how well lxd "just
> works", particularly with the default unprivileged containers.
>
> I'm looking to put
