Code review comment for lp:~alextu/lxc-android-config/lp1575564_include_rules_in_device_tarball

you can only use dpkg -i from a chrooted boot in recovery for such packages. there are plenty of them and usually the bind mount means that there is a file that is either needed inside *and* outside of the container or it is a file we can only ship in the device tarball but need it available in the ubuntu rootfs (the udev rules above fall into that category).

if you would remove these cross device bind mounts you would break the independence of device tarballs from the rootfs ones and have to create one rootfs per device.

this is sadly the nature of using a bind-mount-farm instead of an overlayfs ... dpkg tries to do an atomic unpack of the file which does not work across filesystems (i.e. with bind-mounted files) there is no way to solve this except by changing the system setup altogether (i.e. patch all kernels to support overlayfs (making porting for community people really hard due to requiring giant kernel patches)).
the QA team has several HOWTOs how to deal with these special packages when manually replacing them in the system.