I’ve been bashing my head with SNAPCRAFT_CONTAINER_BUILDS=1 attempts and just realised that my copy of snapcraft installed via snappy has magically rolled-down to build 349 where previously I was using 470 from edge channel. It seems that the builds after 349 have all been un-released? whyso? Any time I let snapd update my snapcraft installation automatically it removes my build 470 because it’s been unpublished and lands me back on the current build in edge which is 349. The current build being pushed means that it is currently impossible for anyone using snapcraft via the store to use container builds due to #1483 and #1488
3 Likes
Noticed this also when hoping to use some build-snaps 
Should be back now, sorry, closed it by accident and given we merge code frequently didn’t hurry up to reopen the channels.
snap info snapcraft
name: snapcraft
summary: "easily create snaps"
publisher: canonical
contact: snappy-canonical-storeaccount@canonical.com
description: |
Snapcraft aims to make upstream developers' lives easier and as such is not a
single toolset, but instead is a collection of tools that enable the natural
workflow of an upstream to be extended with a simple release step into Snappy
enabled system.
snap-id: vMTKRaLjnOJQetI78HjntT37VuoyssFE
channels:
stable: –
candidate: 2.33 (349) 53MB classic
beta: ↑
edge: 2.33+git53.69dceb8 (473) 53MB classic
3 Likes