snapcraft not pulling snap from lxd container

[Alan Pope 🍺🐧🐱 🦄]

alan@KinkPad-K450:~/Source/personal/b2$ snapcraft --use-lxd
The LXD provider is offered as a technology preview for early adopters.
The command line interface, container names or lifecycle handling may change in upcoming releases.
Launching a container.
Waiting for cloud-init

status: done
Skipping pull b2 (already ran)
Skipping pull desktop-gtk2 (already ran)
Skipping pull snapcraft-preload (already ran)
Skipping build b2 (already ran)
Skipping build desktop-gtk2 (already ran)
Skipping build snapcraft-preload (already ran)
Skipping stage b2 (already ran)
Skipping stage desktop-gtk2 (already ran)
Skipping stage snapcraft-preload (already ran)
Skipping prime b2 (already ran)
Skipping prime desktop-gtk2 (already ran)
Skipping prime snapcraft-preload (already ran)
The requested action has already been taken. Consider
specifying parts, or clean the steps you want to run again.
Snapping 'b2' -
Snapped b2_9198f33_amd64.snap
alan@KinkPad-K450:~/Source/personal/b2$ ls
snap BBC_owl.svg owl.png

Snap exists in project directory inside the container, but for some reason it never gets pulled to the host.

https://github.com/popey/b2-snap is the project I am using.

This is using snapcraft from candidate, 3.7.1

alan@KinkPad-K450:~$ snapcraft version
snapcraft, version 3.7.1
alan@KinkPad-K450:~$ snap version
snap 2.40
snapd 2.40
series 16
ubuntu 19.04
kernel 5.0.0-23-generic

[Sergio Schvezov (sergiusens)]

For the record, there is no "pulling" as there was with cleanbuild, this is the process:
- the project is mounted into the container
- the lifecycle is ran inside the container from the mounted path
- the generated snap file is created on the mounted path

My only suspicion would be that we have some bad handling of CWD, if so, this behavior should also be seen when running in --destructive-mode.