Are you at HEAD? I don't expect Almanac to be needed during repo creation.

In general, I'd like better error messages for these kinds of situations. Even better would be some prescriptive text like "Go here, add this, click that".

Almanac is a prototype, so if you were exploring it, there may be unintentional bugs. In general we don't recommend using prototypes unless your adventurous. Maybe @epriestley knows a way out of this, my guess would be to use bin/destroy on the Almanac bindings you created.

I definitely get that it's a prototype and I know not to file bugs against prototypes, but this interaction wasn't directly with Almanac but with a core Diffusion feature. Diffusion shouldn't use Almanac unless explicitly set to use it. 

I have just encountered the same error. Simply created a hosted Git repo. Went smooth. But now clicking on the repository in Diffusion opens a page with:

The Almanac service for this repository is not bound to any interfaces.

Almanac was not explicitly used at any time.

In case still interesting to OP:

1. I removed all my almanac devices and services (test ones I made) using delete destroy.
2. Deleted the repositories that were throwing the exception using the same method.
3. Initialized new repositories and it worked.