I am use wide-dhcpv6-server and wide-dhcpv6-client in two diffrent LXCs
with an iproute2 created bridge and lxc created tun/tap devices and I am
using 3.16.0-4-amd64 #1 SMP and my kernel. I don't have any firewall
that would block ipv6 request and responses that would occur on port 546
and 547,
2016-03-17 10:01 GMT-03:00 Janne Savikko :
>
> $ lxc list web|grep RUNNING|awk '{ print $2 }'|xargs lxc stop
>
>
This is why lxc (not lxd) is BETTER for sysadmins:
# lxc-ls --running | xargs -n1 lxc-stop -n
and docker is even better:
# docker ps -q | docker stop
hi,
I remember, that not very long time ago the 'lxc list' command also
listed snapshots too.
But now it doesn't. How can I do that now?
Thanks,
tamas
ps. Naming lxd client as lxc was a very bad idea from googlers
perspective:/
___
lxc-users
A fix lxcfs has been uploaded and should be available in the various
PPAs over the next few hours.
On Sat, Mar 19, 2016 at 07:53:38AM +0700, Fajar A. Nugraha wrote:
> On Sat, Mar 19, 2016 at 7:07 AM, Stéphane Graber wrote:
> > On Sat, Mar 19, 2016 at 05:47:19AM +0700, Fajar
On 2016-03-16 11:12, Serge Hallyn wrote:
Quoting zzt...@openmailbox.org (zzt...@openmailbox.org):
Will wildcards be supported in lxd commands? For example, I'd like
to do this:
$ lxc info host:*
or
$ lxc info host:web*
and get info on all containers/containers starting with "web" on
On Fri, Mar 18, 2016 at 12:15:35PM -0400, Sean McNamara wrote:
> On Fri, Mar 18, 2016 at 12:09 PM, Sean McNamara wrote:
> > On Fri, Mar 18, 2016 at 11:43 AM, Stéphane Graber
> > wrote:
> >> Our stance hasn't changed. LXD doesn't know nor care about layer-3
On Sat, Mar 19, 2016 at 1:12 AM, B G wrote:
> lxc => 2.0.0rc4
> lxd => 2.0.0rc4
> lxcfs => 2.0.0rc6
>
> After the latest upgrade to lxc/lxd tools existing and new containers fail
> to start, failing on the following stage from the container log:
>
> lxc 20160318161829.810 INFO
On Fri, Mar 18, 2016 at 11:09 PM, Sean McNamara wrote:
> As part of that, I was expecting some way to tell LXD to restrict the
> IP addresses that can be claimed/used by a given container. For
> instance, if I have a public Internet IPv4 /26 allocated to a physical
> host by a