Quoting Alain St-Denis (al...@zenfolie.org):
> Hi,
>
> I experience the exact same problem. Similar setup (wily host, elementary
> freya container). No user session is created when I login the desktop so
> polkit won't grant elevated privileges.
>
> In the container, /proc/1/cgroup shows:
>
>
On 2016-01-20 02:04, Serge Hallyn wrote:
Quoting Tomasz Chmielewski (man...@wpkg.org):
Can lxc restore a snapshot as a new container?
Let's say I have a container named "container1" and make a snapshot
called "test1":
# lxc snapshot container1 "test1"
How would I restore it as a new
On 2016-01-26 01:46, Stéphane Graber wrote:
So either documentation is outdated, and lxc push/pull is allowed
for containers in any state (or at least RUNNING and STOPPED) or the
functionality will be removed.
Which one is true? Being able to push/pull the files is quite
convenient.
I
According to fine manual[1], lxc file "is only allowed for containers
that are currently running".
I've tried doing both push and pull operations on a container in STOPPED
state, and it worked, i.e.:
lxc file pull stopped-container/etc/services .
lxc file push services
On Tue, Jan 26, 2016 at 01:42:12AM +0900, Tomasz Chmielewski wrote:
> According to fine manual[1], lxc file "is only allowed for
> containers that are currently running".
>
> I've tried doing both push and pull operations on a container in
> STOPPED state, and it worked, i.e.:
>
> lxc file pull
On 2016-01-25 22:19, Tomasz Chmielewski wrote:
Let's say I have a container named "container1" and make a snapshot
called "test1":
# lxc snapshot container1 "test1"
How would I restore it as a new container, called "container1-test"?
lxc copy container1/test1 container1-test1
If using a
Is there a way to protect the containers against accidental termination?
For example:
# lxc list
| container-2016-01-25-17-20-11 | RUNNING | 10.190.0.50 (eth0)
(...)
# lxc delete container-2016-01-25-17-20-11
No longer there!
Some kind of "lxc config set containername
