Re: [lxc-users] LXD Cluster & Ceph storage: "Config key ... may not be used as node-specific key"

2019-05-15 Thread Robert Johnson
On 5/15/19 4:20 PM, Stéphane Graber wrote: On Wed, May 15, 2019 at 03:00:34PM -0700, Robert Johnson wrote: I seem to be stuck in a catch-22 with adding a ceph storage pool to an existing LXD cluster. When attempting to add a ceph storage pool, I am prompted to specify the target node

[lxc-users] LXD Cluster & Ceph storage: "Config key ... may not be used as node-specific key"

2019-05-15 Thread Robert Johnson
I seem to be stuck in a catch-22 with adding a ceph storage pool to an existing LXD cluster. When attempting to add a ceph storage pool, I am prompted to specify the target node, but, when doing so, the config keys are not allowed. Once a ceph pool is created, it's not possible to add config

[lxc-users] Failed to mount rootfs

2018-03-26 Thread Robert Johnson
This is a new LXD host running from the snap system. Initially, this was a working system, but as of this morning, I am unable to start existing containers and am unable to launch new ones. Please advise on any additional information that is needed. robertj@vh3:~$ lxd --version 2.21

Re: [lxc-users] lxc exec - support for wildcards and/or variables?

2017-11-20 Thread Robert Johnson
lxc exec $CONTAINER -- bash -c "rm -rf /tmp/somefile*" On 11/17/2017 08:03 AM, Tomasz Chmielewski wrote: How do I use the variables / wildcards with lxc exec? Say, I want to remove all /tmp/somefile* in the container. ___ lxc-users mailing list

[lxc-users] Manually building an image

2017-04-06 Thread Robert Johnson
I have a particular distribution based on CentOS 7 that I would like to turn into a LXD container. The post from Stephane Graber here below has a section titled Manually building an image, but it gives some pretty generic steps that I'm not entirely familiar with. I'm hoping someone could

Re: [lxc-users] lxd api return of /1.0/containers//exec

2016-12-23 Thread Robert Johnson
I've been working on obtaining two way communications with the /exec URI, but your needs may more simple then mine. When you POST to /exec, you probably want to include the 'record-output' key with a (boolean) value of true. ie '{"command": ["df -f /"], "record-output": true}' The doc's