lxc network list
+-+--+-+-+-+
| NAME | TYPE | MANAGED | DESCRIPTION | USED BY |
+-+--+-+-+-+
+-+--+-+-+-+
| lxdbr0 |
On Mon, May 7, 2018 at 2:10 AM, Gaétan QUENTIN wrote:
>
> lxc network list
> +-+--+-+-+-+
> | NAME | TYPE | MANAGED | DESCRIPTION | USED BY |
>
On 2018-05-06 17:27, Tomasz Chmielewski wrote:
On 2018-05-06 17:16, Tomasz Chmielewski wrote:
On 2018-05-06 17:07, Tomasz Chmielewski wrote:
I have a Ubuntu 16.04 server with LXD 3.0 installed from snap.
I've filled the disk to 100% to get "No space left on device".
(...)
The same error
Hello,
Tomasz Chmielewski writes:
> I have a Ubuntu 16.04 server with LXD 3.0 installed from snap.
>
> I've filled the disk to 100% to get "No space left on device".
>
> A while later, it was not possible to use "lxc shell container" or "lxc
> list", because of:
>
> Error: Get
On 2018-05-06 17:55, Free Ekanayaka wrote:
Perhaps it's related to the disk full issue? Maybe Stephane has more
insight bout this.
About the panic, I assume it's still the case that you can't start the
LXD daemon because it panics at startup all the times?
Correct.
Please would send us tar
On 2018-05-06 17:07, Tomasz Chmielewski wrote:
I have a Ubuntu 16.04 server with LXD 3.0 installed from snap.
I've filled the disk to 100% to get "No space left on device".
(...)
The same error shows up after freeing space and restarting the server.
How to debug this?
Also found this
On 2018-05-06 17:16, Tomasz Chmielewski wrote:
On 2018-05-06 17:07, Tomasz Chmielewski wrote:
I have a Ubuntu 16.04 server with LXD 3.0 installed from snap.
I've filled the disk to 100% to get "No space left on device".
(...)
The same error shows up after freeing space and restarting the