Comment 2 for bug 1607748

Every single available bit of online documentation, merchandise, scripts, ... expect the lxd client to be called "lxc". Folks also expect to install lxd to the get the lxc command.

So yes, we could use another command name, but then everything, including lxd's error messages and built-in documentation will tell you to use a command that you do not have on your system.

An alternative would be to package lxc as a separate snap, but then we'd run into different difficulties as it'd be two completely separate snaps built from the exact same source. Keeping things in sync would be a bit difficult and it would also require the user to install two separate snaps to get the expected user experience.