The lxc-instance job ends up starting containers as 'anonymous'. You can see them using
lxc-list -P /var/lib/lxc_anon
The autostart code is currently being reworked but I think this is worth fixing in older releases. It coudl be fixed in one of two ways - or both: the lxc-instance job could detect that linked file is a standard container's config and start it that way (without specifying -f); or lxc-start could detect that the passed-in rcfile is a link to a standard $lxcpath/$name/config, and not start the container anonymously.
Drat my comment got lost.
The lxc-instance job ends up starting containers as 'anonymous'. You can see them using
lxc-list -P /var/lib/lxc_anon
The autostart code is currently being reworked but I think this is worth fixing in older releases. It coudl be fixed in one of two ways - or both: the lxc-instance job could detect that linked file is a standard container's config and start it that way (without specifying -f); or lxc-start could detect that the passed-in rcfile is a link to a standard $lxcpath/ $name/config, and not start the container anonymously.