Re: [lxc-users] lxc image import: Could not extract image metadata.yaml from tar

2016-07-26 Thread tapczan
On 26 July 2016 at 22:00, Stéphane Graber wrote: > So I wonder if the issue is the prefixing with ./ that your tarball > appears to have. Thanks for hint. Indeed it's a matter of prefix. So the archive tarball has to be created in a way: ~/meta# tar cJf ../meta.tar.xz * ~/meta# tar tf ../meta.t

Re: [lxc-users] Can a container modify the host rtc?

2016-07-26 Thread jjs - mainphrame
Interesting - we've had OVZ containers running as ntp servers, being granted the ability to set the RTC via the CAP_SYS_TIME capability. (never more than one per physical host though) Jake On Tue, Jul 26, 2016 at 9:58 AM, Stewart Brodie wrote: > Paul Giordano wrote: > > > Running LXD 2.0.3 > >

Re: [lxc-users] lxc image import: Could not extract image metadata.yaml from tar

2016-07-26 Thread Stéphane Graber
On Tue, Jul 26, 2016 at 09:18:16PM +0200, tapczan wrote: > Hello > > I'm trying to create custom LXC image. I've create root file system > tarball (rootfs.tar.xz - directly at its root) and meta tar ball: > > # file meta.tar.xz > meta.tar.xz: XZ compressed data > > # tar tf meta.tar.xz > ./ > ./

Re: [lxc-users] Can a container modify the host rtc?

2016-07-26 Thread Stewart Brodie
Paul Giordano wrote: > Running LXD 2.0.3 > > I'm trying to have a container be an ntp server, but the container gets an > EPERM trying to set the hw clock: > > clock_settime(CLOCK_REALTIME, {1469546956, 258938000}) = -1 EPERM (Operation not permitted) > adjtimex(0x7b0d6bf0) = -1 EPERM (Op

[lxc-users] lxc image import: Could not extract image metadata.yaml from tar

2016-07-26 Thread tapczan
Hello I'm trying to create custom LXC image. I've create root file system tarball (rootfs.tar.xz - directly at its root) and meta tar ball: # file meta.tar.xz meta.tar.xz: XZ compressed data # tar tf meta.tar.xz ./ ./metadata.yaml ./templates/ ./templates/upstart-override.tpl ./templates/hostnam

Re: [lxc-users] CirrOS on OpenStack using LXD as a hypervisor

2016-07-26 Thread Muneeb Ahmad
I didn't know that. Thank you very much. It worked! On Tue, Jul 26, 2016 at 6:36 PM, Serge E. Hallyn wrote: > Well, cirros does not in fact have /bin/bash :) Try /bin/sh. > > Quoting Muneeb Ahmad (muneeb.ganda...@gmail.com): > > Thank you for your reply. I tried the way you suggested. ran a lxc

[lxc-users] Can a container modify the host rtc?

2016-07-26 Thread Paul Giordano
Running LXD 2.0.3 I'm trying to have a container be an ntp server, but the container gets an EPERM trying to set the hw clock: clock_settime(CLOCK_REALTIME, {1469546956, 258938000}) = -1 EPERM (Operation not permitted) adjtimex(0x7b0d6bf0) = -1 EPERM (Operation not permitted) settimeofd

Re: [lxc-users] CirrOS on OpenStack using LXD as a hypervisor

2016-07-26 Thread Serge E. Hallyn
Well, cirros does not in fact have /bin/bash :) Try /bin/sh. Quoting Muneeb Ahmad (muneeb.ganda...@gmail.com): > Thank you for your reply. I tried the way you suggested. ran a lxc cirros > container and replaced lxd container's rootfs with lxc container's. > Restarted it and when I try to enter i

[lxc-users] removing cgmanager

2016-07-26 Thread Serge E. Hallyn
Hi everyone, I'm intending to remove cgmanager from Debian. Upstream and distro maintainers all agree this is the right thing to do, but I don't want this to come as a surprise to anyone - so wanted to send out one last email warning and asking if anyone is depending on it. I've said I'll act on

[lxc-users] lxc-create using offline mode

2016-07-26 Thread Ruzsinszky Attila
HI, I found this: https://lists.linuxcontainers.org/pipermail/lxc-devel/2014-July/009784.html I followed the description for Ubuntu Xenial amd64. root@fcubi:~# LANG="C";lxc-create -n lub7 -t ubuntu -- -r xenial -a amd64 Checking cache download in /var/cache/lxc/xenial/rootfs-amd64 ... Copy /var/

Re: [lxc-users] CirrOS on OpenStack using LXD as a hypervisor

2016-07-26 Thread Muneeb Ahmad
Thank you for your reply. I tried the way you suggested. ran a lxc cirros container and replaced lxd container's rootfs with lxc container's. Restarted it and when I try to enter it with 'lxc exec /bin/bash', nothing happens. In lxc.log, i get an error. Any ideas? "ERRORlxc_attach - attach.c:l