The container's locale should not be bind-mounted from the host and should be programatically set at container start

After further investigation, chroot container types still need the /usr/lib/locale bind-mount, but that is ok since there is no running container and each operation on the chroot is independent of another running operation or running application.

Fix committed into lp:libertine at revision 365, scheduled for release in libertine, milestone Unknown

This bug was fixed in the package libertine - 1.5.1+17.04.20170118-0ubuntu1

---------------
libertine (1.5.1+17.04.20170118-0ubuntu1) zesty; urgency=medium

  [ Chris Townsend ]
  * Remove the /tmp/.X11-unix umount during LXC container start for operations
    as it seems it's not needed. (LP: #1654650)
  * Remove extra finish_application() in chroot backend.
  * Set container's locale and language based on the host including installing
    necessary language packs. (LP: #1609982)
  * Bump version to 1.5.1.

  [ Larry Price ]
  * Manually execute lxd bind mount script to fix /run/user and remove
    service. (LP: #1654647)
  * Convert results to dicts on operation/application collision in container
    lifecycle managers.
  * Stop bind-mounting /usr/lib/locale and let environment do all the work.
    (LP: #1654648)
  * Mount lxd home directory in $HOME/.local/libertine-container where it
    belongs.
  * Manually wait for lxd container to stop when specified after calling the
    service. (LP: #1655980)
  * Ask for container user password when creating lxd containers. (LP: #1655977)
  * Bind-mount lxd container applications and icons directories into user's
    home directory.

 -- Christopher Townsend <email address hidden> Wed, 18 Jan 2017 14:50:33 +0000