Snapcraft includes files from installed snaps in new snap

[Mark Shuttleworth]

I was very surprised to see these files in a new snap I just made:

squashfs-root/snap
squashfs-root/snap/conjure-up
squashfs-root/snap/conjure-up/108
squashfs-root/snap/conjure-up/108/usr
squashfs-root/snap/conjure-up/108/usr/lib
squashfs-root/snap/conjure-up/108/usr/lib/x86_64-linux-gnu
squashfs-root/snap/conjure-up/108/usr/lib/x86_64-linux-gnu/libdb-5.3.so
squashfs-root/snap/core
squashfs-root/snap/core/current
squashfs-root/snap/core/current/usr
squashfs-root/snap/core/current/usr/lib
squashfs-root/snap/core/current/usr/lib/x86_64-linux-gnu
squashfs-root/snap/core/current/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200

I can't think of any good reason for those files to be there. Conjure-up is not a dependency of this new snap in any way.

[Sergio Schvezov (sergiusens)]

Can I see the snapcraft project that caused this please?

[Sergio Schvezov (sergiusens)]

Just tested some random snaps after installing conjure-up. Would be interested in seeing the project that causes this or some steps to reproduce.

[Sergio Schvezov (sergiusens)]

This happens when creating a snap with classic confinement where the library paths are fixed to a path with `/snap/`. An easy reproducer is to build snapcraft as a snap.

Where this happens is in the code that fetches dependencies (basically running ldd on every binary). My first approach involved disabling this for classic confinement but that is a much more impacting change for people (breakage will happen).

[Sergio Schvezov (sergiusens)]

https://github.com/snapcore/snapcraft/pull/1231