spaces in container path of mounted shares
When mounting a host folder into a container (using lxc config device add <container> <device> disk source=<source> path=<path>), the path variable doesn't handle spaces upon a container restart. It functions as expected (escaping with a backslash) when first added, (you can use the share and everything) but on container restart, an error is generated. Example:
>lxc stop Container1
>lxc config device add Container1 share disk source=/share path=/home/
Device share added to Container1
>lxc config show Container1
...
devices:
share:
path: /home/test/testing spaces
source: /share
type: disk
...
>lxc start Container1
error: Error calling 'lxd forkstart Container1 /var/lib/
Try `lxc info --show-log Container1` for more info
>lxc info --show-log Container1 | grep -i error
lxc 20160515102447.195 ERROR lxc_conf - conf.c:
lxc 20160515102447.195 ERROR lxc_conf - conf.c:
lxc 20160515102447.195 ERROR lxc_start - start.c:
lxc 20160515102447.195 ERROR lxc_sync - sync.c:
lxc 20160515102447.195 ERROR lxc_start - start.c:
Is there a formatting thing I'm doing wrong? Doubly escaping causes the add command to fail. Manually adding a backslash into the config doesn't change anything - it just adds a backslash at the end of disk.home-
Spaces seem to be handled for the source field just fine, when escaped if added via command-line. They will show in the config without spaces but are interpreted correctly, as far as I can tell.
Question information
- Language:
- English Edit question
- Status:
- Expired
- For:
- Ubuntu lxd Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply: