With the change to BcContainerHelper, sandbox containers became multitenant by default. This means that you have to remember the ?tenant=default in the WebClient and the “tenant” : “default” in launch.json.
The reason for this change was, that sandbox containers needs to feel and act like online tenants and online tenant are… – tenants. I did however miss out on one thing, which I was made aware of over the weekend.
The default tenant is mounted with AllowAppDatabaseWrite. This was done back in the time to ensure that you had a tenant, which worked more or less like on premises. In a few hours, a new generic image will be published, which reverses this for sandbox containers – the default tenant will NOT have AllowAppDatabaseWrite set to true.
You can still add an additionalparameter if you want the “old” behavior:
--env defaultTenantHasAllowAppDatabaseWrite=Y
and of course nothing changes if you are using single tenancy.
Enjoy
Freddy Kristiansen
Technical Evangelist
Freddys blog 
Thanks a lot Freddy! That’s what I’ve been looking for.
LikeLike
I’ve tried some scenario’s. It looks like this new parameter only works if you switch the default database to multi-tenant. If the newdatabase switch is used the value of allowappdatabasewrite is not changed.
I’ve put testresults in the original commit https://github.com/microsoft/nav-docker/commit/2e0343f1d9ec593cb9284c6345955afe5fd6d15f. Or should I create an issue?
LikeLike
Sorry, I didn’t see this. Please create an issue on https://github.com/microsoft/navcontainerhelper/issues and include as much information as possible if this is still an issue
LikeLike