[lxc-devel] making lxcpath a real path?

[Harald Dunkel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Mike,

Of course I understand that the lxc container search path might
lead to confusion in case of ambiguous container names. However,
similar problems exist for $PATH and $LD_LIBRARY_PATH and others.
How about "first match wins"?

If lxcpath is a search path, then I see no other way than to
distinguish between the lxc-commands working on existing
containers, and the lxc-commands requiring a destination
directory (to create, move or migrate a container). Do you
think it would be possible to use

	lxc-create -n /some/absolute/path/to/my_container
or
	lxc-create -n ../local/path/to/my_container

(ignoring the lxcpath)?

Do we need commands like "lxc-edit-config -n my_container" to
make sure that "my_container" is just a container identifier
without revealing it as a Posix directory name?


Regards
Harri

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)

iQEcBAEBCAAGBQJSniyXAAoJEAqeKp5m04HL+IEIAIYVojPMHJlUgTDIm2E1BW4F
zO6/A1sqxq4nN5VSyUtmL1iVVulLnWCJOlnhy6Sli4aCZebT5fi7LbNMPrYuE7K1
p5py3QgzRvcka7vIVx18/DPj6XLIjUA4HiogDHfd0wgn6JXASGzB2fztJfT8B0RB
JZ4gzBigQtJ9k3NuVpYE5Yh+ZLoQVaJQUCI6atJw9lDnSdcqV+ff4G0xD/ReueWV
mopTQc/Ek/aAihq0mquPmndzVlWB8uPVEJUWD8SWy8fymeK6+24mS4dhggfFSBZ5
NGNoaEDxjkzD6zL8bI+/WaIyr1OBd4g8inEdn9uAY1atrClTNDbS2N8BzAOJsTQ=
=WtrK
-----END PGP SIGNATURE-----