[lxc-users] Error getting images behind a proxy

[Lago Gonzalez, Diego]

Hello,

I've installed lxc/lxd trought its official PPA (ppa:ubuntu-lxc/lxd-stable) and 
I have version 2.0.0.rc5 in a Ubuntu MATE 15.10 (amd64). When I try to download 
an image (with command `sudo -E lxc launch images:centos/6/amd64 my-centos`) I 
always get the same error:

error: Get https://images.linuxcontainers.org/1.0/images/centos/6/amd64: remote 
error: handshake failure

Full debug output of the command is:

user@host ~ $ sudo -E lxc launch --debug images:centos/6/amd64 my-centos
DBUG[03-23|16:29:16] Raw response: 
{"type":"sync","status":"Success","status_code":200,"metadata":{"api_extensions":[],"api_status":"development","api_version":"1.0","auth":"trusted","config":{"storage.zfs_pool_name":"lxd-pool"},"environment":{"addresses":[],"architectures":["x86_64","i686"],"certificate":"-BEGIN
 
CERTIFICATE-\nMIIFwDCCA6igAwIBAgIRAKHLionIKuqLPMxSzZrE59kwDQYJKoZIhvcNAQELBQAw\nMzEcMBoGA1UEChMTbGludXhjb250YWluZXJzLm9yZzETMBEGA1UEAwwKcm9vdEBk\ndmJveDAeFw0xNjAzMjExMTUwNTBaFw0yNjAzMTkxMTUwNTBaMDMxHDAaBgNVBAoT\nE2xpbnV4Y29udGFpbmVycy5vcmcxEzARBgNVBAMMCnJvb3RAZHZib3gwggIiMA0G\nCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQCnuiQIbMmbQWyLgaokDlcdDX/hzoNJ\nu6xSKlHskMhjoJDgzJZ+s2ooFMlOjinVXQMiTb4thY41z3BaL1JhD83E+YGlMH5c\n1NCzeJT0Zhqrb+kyDKOdLueC3sekLhILdoXBj+t4feyUs5yo3kWqkzKG5ejkpPVo\nhMG9/knXdnz9I2lNk6DuYzxG3OCvGN+8+f7HAJC43lGtsQoee3vUfNr9To/K1CxZ\nFkDBJUyiFcIjIMmPud8O4EAlxaR1hOXSr11Z19b0IE6qYtoKnBGZ2t+Vu76X+s//\nTC5XyVcLnXQCMbbU7GfTmeeNMzQVYpokZclPUO7w4GSHotqv8sUatj+O061KBtCV\nV/tweqrDLvMlkOd40BgKnn8lEuwoxHtSeHquVSYDSXmbHk0xT+X/Jo2bWIzg6jls\nw2s1vS8B71kz78to7GjhcJ4brESjxrClhMZg99O4WO4Bj7mkarvAQwh4CindI0UY\n1TBg0IK6bFm4wm0YhaheJ+2mPn/1PinLu6UrNHD72J9I8O+c92ISK8aC209AWmcH\nuUjHtMdLWMiU/dGcMiiRJSzYIkjNmWKB0VfV9CJFYeAUo7bZUXuxoj28Iw+/JKyc\nDlu0SSfpleHKNaU1JLIsXe/F2cyraxRCQSgzOLsyyJ0oNM+YFvBM6NoiRfcuRzdN\ngttRhnAqMRrcywIDAQABo4HOMIHLMA4GA1UdDwEB/wQEAwIFoDATBgNVHSUEDDAK\nBggrBgEFBQcDATAMBgNVHRMBAf8EAjAAMIGVBgNVHREEgY0wgYqCBWR2Ym94ggwx\nMC4wLjIuMTUvMjSCG2ZlODA6OmEwMDoyN2ZmOmZlZDY6NjI2OC82NIIOMTcyLjE3\nLjQyLjEvMTaCHGZlODA6OjQwYTE6NDlmZjpmZWJhOjhiODYvNjSCCzEwLjAuMy4x\nLzI0ghtmZTgwOjoxNGRkOjdmZjpmZTUwOjE5ZTkvNjQwDQYJKoZIhvcNAQELBQAD\nggIBAE7u9y1fkHPNluuaO4IZNGvl0NkOUpsVVQPL2L+AtAjukdb2c2DYsiOLir+x\nKmTkhu6jgUz87Ht/LSQVH3gXAgMRZhDSAhs9UA+t5O7MDQaRuvWEmzt8iw6/xQ6i\nXqKFUq44frNxyfLlTjJK6sphxcHT8gVxbsUxx2HFU2BrFCxlG6QoKIyD0Z+GHTkR\neZGPW+g8gQsWA0UNN/pNrN/cBe15q6eQBio8g4fjtbp22b/RQFFU+h/FvJifzuVs\nkpVenN2J9ox1EZzXy8/gyStjAbDWQBGJVlDnw10o/CgWbuMCVovwejOxUbXbgyf0\nKGVJyFHtFOXxRpt7d0ZVsyyknNyDeYiNyMDeTiHuh/Mxv0fFEFmvFwgKwhDic6+d\ntFYc3cv/E81n7diMwm2XpCIC2y94ow4ncQvDTkaWvUrSUjTms3nF6L4DL/qUBLgW\npB5PzeIZcZ9FdeUOJzg07OrkdJdwmwV4mSUGvxM+bhBsr7YfwJ+eOUsnYFSb4OPu\nIITkbQhaduUNFO3N2YJRx26gwbrJ+/IJ1rAn5ombVqMsyDjqoTKS4asKmelIpYO1\nisYfBrFNaB+9JtFyFiBg7Zw66Wic5tdPNn3PK/iVVoMp6w3IT+QDFDc1ZCs5Wm7x\nBt/GNd10M7w3N8K1BC7uEH4vAAwk9+iUsLbQHdLmWUW6gYDl\n-END
 
CERTIFICATE-\n","driver":"lxc","driver_version":"2.0.0.rc12","kernel":"Linux","kernel_architecture":"x86_64","kernel_version":"4.2.0-27-generic","server":"lxd","server_pid":6383,"server_version":"2.0.0.rc5","storage":"zfs","storage_version":"5"},"public":false}}
 
DBUG[03-23|16:29:16] Raw response: 
{"type":"sync","status":"Success","status_code":200,"metadata":{"api_extensions":[],"api_status":"development","api_version":"1.0","auth":"trusted","config":{"storage.zfs_pool_name":"lxd-pool"},"environment":{"addresses":[],"architectures":["x86_64","i686"],"certificate":"-BEGIN
 

Re: [lxc-users] Networking LXD containers

[efersept]

After doing some homework on virtualization networking techniques and 
studying the contents of /usr/lib/x86_64-linux-gnu/lxc/lxc-net am I 
correct in deducing that the default lxc/lxd bridge (lxcbr0) is a NATed 
interface? If I wanted to attach containers to a simple bridged 
interface and give them IPs on my network would it be as simple as 
creating the following entry in the container's config after the bridge 
was setup on the host?


devices:
  eth0:
name: eth0
nictype: bridged
parent: br0
type: nic

Or is there some other configuration that would need to be done with 
lxc/lxd to accomplish this?





___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

[lxc-users] lxc-checkpoint failed when restore unprivileged containers

[Ocean Chen]

When restore an unprivilleged container from checkpoint, it failed with error 
"Error (image.c:318): Unable to open netns-9.img: Permission denied".


I run everything in root, and has below lines in lxc config file to have 
unprivilleged container.
  lxc.id_map = u 0 10 65536
  lxc.id_map = g 0 10 65536


The cmd to restore container is:
  lxc-checkpoint -n wily8 -D /var/lib/lxc/wily8/dump -r TRACE -v


Error in dump.log from ciru is:


(00.005616) Wait until namespaces are created
(00.006988) Running setup-namespaces scripts
(00.007010)  1: Calling restore_sid() for init
(00.007017)  1: Restoring 1 to 1 sid
(00.007091)  1: Mount procfs in crtools-proc.goosvl
(00.007154)  1: Restoring namespaces 1 flags 0x7c028000
(00.007196)  1: Error (image.c:318): Unable to open netns-9.img: Permission 
denied
(00.007374) Error (cr-restore.c:1306): 10779 exited, status=1


My env:
ubuntu 15.10 with 4.4.5-040405-generic
lxc 2.0.0~rc13
criu 2.0
checkpoint used to work in my env when I using lxc 2.0.0~rc10 for unprivileged 
containers, but not after I update to rc13.

___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users