On Thu, Feb 23, 2017 at 01:33:04AM +0100, Detlef Bracker wrote:
> Every scenerario breaks with other problems - So has somebody a resolution?
>
> Plesk will not work on LCX container about mount problems! A backup and
> restore as an unprivileged server with option ignore restore fails,
> brings n
Installation of diferent things hangs and long log files with this
message comes:
Debian 8 Proxmox LCX-Image - updated to systemd mode - rebooted -
updated - installation of plesk expl.
Feb 23 01:59:34 ct1004 systemd[1]: Looping too fast. Throttling
execution a little.
Feb 23 01:59:35 ct1004
Every scenerario breaks with other problems - So has somebody a resolution?
Plesk will not work on LCX container about mount problems! A backup and
restore as an unprivileged server with option ignore restore fails,
brings new other problems why then the system is no more usable -
possible parts o
I test the new platform with the latest updates
On glusterfs server: no possibility to migrate contenaires :
TASK ERROR: lxc container migration not implemented.
coming soon ?
Thank's.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.pro
>>So I wonder if we can/should simply store the configuration using that
>>simplified format? Any objections?
I agree to have our own format too, something similar than qemu.
- Mail original -
De: "dietmar"
À: "pve-devel"
Envoyé: Samedi 1 Août 2015
Great! i like this. simply is good choice!
> 在 2015年8月1日，下午1:05，Dietmar Maurer 写道：
>
> Hi all,
>
> we currently try to use the original lxc configuration format to
> store our container configuration, because
> I initially thought we need that to use things like 'lxc-snapshot'.
> But it turns o
Hi all,
we currently try to use the original lxc configuration format to
store our container configuration, because
I initially thought we need that to use things like 'lxc-snapshot'.
But it turns out that we make snapshots using our own commands, and we
do not store snapshot config in 'lxc-snapsh
